From owner-freebsd-current@FreeBSD.ORG Tue Jan 8 02:30:54 2013 Return-Path: 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 C5BF95FC for ; Tue, 8 Jan 2013 02:30:54 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from anubis.delphij.net (anubis.delphij.net [64.62.153.212]) by mx1.freebsd.org (Postfix) with ESMTP id 92FA837E for ; Tue, 8 Jan 2013 02:30:54 +0000 (UTC) Received: from Xins-MacBook-Pro-2.local (c-67-188-85-47.hsd1.ca.comcast.net [67.188.85.47]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by anubis.delphij.net (Postfix) with ESMTPSA id D6C5F1F51A; Mon, 7 Jan 2013 18:30:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=delphij.net; s=anubis; t=1357612253; bh=bNZ3DD5K1Odc3N2MlmylKVCEbP3gMxofcR5UXPKmBCQ=; h=Date:From:Reply-To:To:Subject:References:In-Reply-To; b=o+hPT9zZylIecuZNU08j6dyTvqjn7HDXeMLI+DL3eoGyqyW1RduKJtiowjc2rMMrd VtsVFVTJAo34LUzpnCN7uGlxBO5Pi0MnVCBgWurKBeeuaksJHENayx4xWNl96uX8Fw SHSEHriBVPputzzKL06MCq1zSShcG3NctnrRss3s= Message-ID: <50EB84DC.2010805@delphij.net> Date: Mon, 07 Jan 2013 18:30:52 -0800 From: Xin Li Organization: The FreeBSD Project MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: sysctl -a causes kernel trap 12 References: <50EB602F.9050300@delphij.net> <20130108000233.GZ82219@kib.kiev.ua> <50EB63A9.50903@delphij.net> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: d@delphij.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jan 2013 02:30:54 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 1/7/13 4:21 PM, Ryan Stone wrote: > 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. My setting was debugger on panic but that's a good point, will try unattended tomorrow to find out (I don't have high expectation here though). > Also it would be worth setting kern.stop_scheduler_on_panic=0 to > see if that lets you generate a core. Hmm... I don't know how will this help but will try. Cheers, -----BEGIN PGP SIGNATURE----- iQEcBAEBCAAGBQJQ64TcAAoJEG80Jeu8UPuzhLoH/RVSZKhc4TkhWM3GF9FgiZY0 s5TH738pyh0+fe+FsGItr4uw83MvLLkjVZTlvstwXjEZhrXH6ehnXibcAQnNKACo 0mJKUOQq5xbWVVDSkLeJwthavrAXEBwUPVTVjx6ZhRLJmikkQNbtOkvOypvJ5Jjh i/1/HSFgFrI3x71OpPJOdKMru18VvN5K74A8v34HlaYMgEpnPGmuTJ6hPvkgC8a+ 1w0vGBInmLQWQZ4UEGUhPyoVly2zp81zFpCUfIzf6jd+FPMOcN+gj2JPSYLVUHS2 Rv7ReaT5U6gWvTxTm+lc2zkaUnSkXb8oAwQafWWD/NopnUZHvlQsIdZgSjGhG1k= =Nf0J -----END PGP SIGNATURE-----