From owner-freebsd-current@FreeBSD.ORG  Mon Jul  9 16:08:30 2012
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 738C5106566B;
	Mon,  9 Jul 2012 16:08:30 +0000 (UTC)
	(envelope-from imb@protected-networks.net)
Received: from sarah.protected-networks.net (sarah.protected-networks.net
	[202.12.127.65])
	by mx1.freebsd.org (Postfix) with ESMTP id 375B28FC16;
	Mon,  9 Jul 2012 16:08:30 +0000 (UTC)
Received: from toshi.auburn.protected-networks.net
	(toshi.auburn.protected-networks.net [202.12.127.84])
	(using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
	(Client CN "Iain Butler",
	Issuer "RSA Class 2 Personal CA" (not verified))
	(Authenticated sender: imb@protected-networks.net)
	by sarah.protected-networks.net (Postfix) with ESMTPSA id C9A7E617C;
	Mon,  9 Jul 2012 12:08:23 -0400 (EDT)
DomainKey-Signature: a=rsa-sha1; s=200509; d=protected-networks.net; c=nofws;
	q=dns; 
	h=message-id:date:from:user-agent:mime-version:to:cc:subject:
	references:in-reply-to:x-enigmail-version:openpgp:content-type:content-transfer-encoding;
	b=gupo9ooYzCGDFD/iFhmaPSmAyTKJqHKuU6eG0BWjOlNyFP+5n6w+rkVNNZWeWJdC/
	CoA8j299d/v9vXrNZIBpwKVzJ9F7UurMpq5wLfZksS+Dtsu0ClqQN8uHlADOsRo
Message-ID: <4FFB01F5.80803@protected-networks.net>
Date: Mon, 09 Jul 2012 12:08:21 -0400
From: Michael Butler <imb@protected-networks.net>
User-Agent: Mozilla/5.0 (X11; FreeBSD i386;
	rv:13.0) Gecko/20120619 Thunderbird/13.0.1
MIME-Version: 1.0
To: John Baldwin <jhb@freebsd.org>
References: <4FF98128.6050607@protected-networks.net>
	<201207091122.38865.jhb@freebsd.org>
	<4FFAFBB2.6070909@protected-networks.net>
	<201207091154.25414.jhb@freebsd.org>
In-Reply-To: <201207091154.25414.jhb@freebsd.org>
X-Enigmail-Version: 1.4.2
OpenPGP: id=0442D492
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Konstantin Belousov <kostikbel@gmail.com>, 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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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: Mon, 09 Jul 2012 16:08:30 -0000

On 07/09/12 11:54, John Baldwin wrote:
> 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
> 

Thanks! Archived for future reference :-)

	imb