From owner-freebsd-bugs@FreeBSD.ORG  Tue Nov 11 00:15:10 2014
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 3B3BF9A3
 for <freebsd-bugs@FreeBSD.org>; Tue, 11 Nov 2014 00:15:10 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 2290D156
 for <freebsd-bugs@FreeBSD.org>; Tue, 11 Nov 2014 00:15:10 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sAB0FABi071515
 for <freebsd-bugs@FreeBSD.org>; Tue, 11 Nov 2014 00:15:10 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 194938] [10.1-RC4-p1][panic] panic by setting sysctl
 vfs.zfs.vdev.aggregation_limit (with backtrace)
Date: Tue, 11 Nov 2014 00:15:10 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.1-RC2
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: code.jpe@gmail.com
X-Bugzilla-Status: Needs Triage
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-194938-8-P9d7JgGTnH@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-194938-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-194938-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Nov 2014 00:15:10 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D194938

--- Comment #1 from J. Pernfu=C3=9F <code.jpe@gmail.com> ---
Correction: the 10.1-RC3 r273607 just panic'ed as well. It just took a lot
longer. The panic message was, as far as I could see from the corner of my =
eye,
the same call sequence.

This will make it easier if any of you require something from me, since the
10.3 is under my desk. I'll try to get a core from that one tomorrow as wel=
l if
required.


Regards,
  Joerg

--=20
You are receiving this mail because:
You are the assignee for the bug.=