From owner-freebsd-current@FreeBSD.ORG  Tue Jan  8 00:21:06 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id E2209C42
 for <freebsd-current@freebsd.org>; Tue,  8 Jan 2013 00:21:06 +0000 (UTC)
 (envelope-from rysto32@gmail.com)
Received: from mail-ob0-f175.google.com (mail-ob0-f175.google.com
 [209.85.214.175]) by mx1.freebsd.org (Postfix) with ESMTP id B3843F28
 for <freebsd-current@freebsd.org>; Tue,  8 Jan 2013 00:21:06 +0000 (UTC)
Received: by mail-ob0-f175.google.com with SMTP id vb8so17989086obc.20
 for <freebsd-current@freebsd.org>; Mon, 07 Jan 2013 16:21:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=iWTvawaH6/3G+Dr1QTiqG7WbyF4MphqskQvT9biMmrI=;
 b=Ld8wqbOis3ASPae79VELqj4XfhsnA/eF4aT0ybgC95hoUjbKYj4vqHAvbPGETCJLEc
 SpRM6mTN4endy0XOUATtCgZ9rw6xXC9LzPE4AoaGUELpwD3uFLjGfHbZGwsRU/MtaZHf
 wNjG8IfSWhU6PCy6mqMqoDiojX8vC9MCtzcEUaa+Bpz3R67Cl9kaSXN2rZri8QL4RrsD
 6vumDOAKWwHC99bZf4uyZeF9381+t7WBLbydkPstujfuqz8PxaevUAT+58IniRWvjr89
 kYgAHGKarAgcRYSJ2NGaUT9qQdxfWac+9OJpaZqNxtBfIpGMPx69kdxAesVkt/+M/3em
 pPRA==
MIME-Version: 1.0
Received: by 10.60.171.175 with SMTP id av15mr34089243oec.75.1357604460782;
 Mon, 07 Jan 2013 16:21:00 -0800 (PST)
Received: by 10.76.128.68 with HTTP; Mon, 7 Jan 2013 16:21:00 -0800 (PST)
In-Reply-To: <50EB63A9.50903@delphij.net>
References: <50EB602F.9050300@delphij.net> <20130108000233.GZ82219@kib.kiev.ua>
 <50EB63A9.50903@delphij.net>
Date: Mon, 7 Jan 2013 19:21:00 -0500
Message-ID: <CAFMmRNwv8pDsy0ZRLXzUft7A1OGxEt9DSmYN1Hun7FxrbHYvnA@mail.gmail.com>
Subject: Re: sysctl -a causes kernel trap 12
From: Ryan Stone <rysto32@gmail.com>
To: Xin LI <d@delphij.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
Cc: Konstantin Belousov <kostikbel@gmail.com>,
 FreeBSD Current <freebsd-current@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 00:21:06 -0000

Have you tried dropping into the debugger by setting
debug.debugger_on_panic=1 instead of trying to generate a core?  You might
have some success generating at least a backtrace.

Also it would be worth setting kern.stop_scheduler_on_panic=0 to see if
that lets you generate a core.