From owner-freebsd-current@FreeBSD.ORG Mon Jul 9 16:05:19 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CC37D106566B for ; Mon, 9 Jul 2012 16:05:19 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id A201E8FC19 for ; Mon, 9 Jul 2012 16:05:19 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id F414EB943; Mon, 9 Jul 2012 12:05:18 -0400 (EDT) From: John Baldwin To: Michael Butler Date: Mon, 9 Jul 2012 11:54:25 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <4FF98128.6050607@protected-networks.net> <201207091122.38865.jhb@freebsd.org> <4FFAFBB2.6070909@protected-networks.net> In-Reply-To: <4FFAFBB2.6070909@protected-networks.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201207091154.25414.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 09 Jul 2012 12:05:19 -0400 (EDT) Cc: Konstantin Belousov , current@freebsd.org Subject: Re: sleeping thread panic? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2012 16:05:19 -0000 On Monday, July 09, 2012 11:41:38 am Michael Butler wrote: > On 07/09/12 11:22, John Baldwin wrote: > > On Sunday, July 08, 2012 9:46:09 am Michael Butler wrote: > > [ .. snip .. ] > > >> > >> Sorry, that is the entire info file - nothing more than I've posted is > >> logged, > > > For future reference, you can look at the core.txt.0 file generated > > by crashinfo. It should contain the dmesg near the bottom and you could > > have gotten the stack trace of the broken thread from that. > > While that's usually the case in my experience, none was written with > this :-( Humm, you can also get to it in kgdb via this: printf "%s", msgbufp->msg_ptr -- John Baldwin