From owner-freebsd-net@FreeBSD.ORG  Sat Jan 15 16:28:52 2011
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 6DD05106566C
	for <freebsd-net@freebsd.org>; Sat, 15 Jan 2011 16:28:52 +0000 (UTC)
	(envelope-from egrosbein@rdtc.ru)
Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [62.231.161.221])
	by mx1.freebsd.org (Postfix) with ESMTP id CB6D98FC15
	for <freebsd-net@freebsd.org>; Sat, 15 Jan 2011 16:28:51 +0000 (UTC)
Received: from eg.sd.rdtc.ru (localhost [127.0.0.1])
	by eg.sd.rdtc.ru (8.14.4/8.14.4) with ESMTP id p0FGSiYk009961;
	Sat, 15 Jan 2011 22:28:44 +0600 (NOVT)
	(envelope-from egrosbein@rdtc.ru)
Message-ID: <4D31CB37.9090003@rdtc.ru>
Date: Sat, 15 Jan 2011 22:28:39 +0600
From: Eugene Grosbein <egrosbein@rdtc.ru>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; ru-RU;
	rv:1.9.2.13) Gecko/20110112 Thunderbird/3.1.7
MIME-Version: 1.0
To: John Baldwin <jhb@freebsd.org>
References: <4D3011DB.9050900@frasunek.com>
	<4D30458D.30007@sentex.net>	<4D309983.70709@rdtc.ru>
	<201101141437.55421.jhb@freebsd.org>
In-Reply-To: <201101141437.55421.jhb@freebsd.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: freebsd-net@freebsd.org, Przemyslaw Frasunek <przemyslaw@frasunek.com>,
	Mike Tancsa <mike@sentex.net>
Subject: Re: panic: bufwrite: buffer is not busy???
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Jan 2011 16:28:52 -0000


> Assuming your kernel is built with debug symbols (which is the default), one
> thing you can do to aid in debugging is this:
> 
> gdb /boot/kernel/kernel
> (gdb) l *0xffffffff803cc979
> 
> Where the 0xfff<blah> bit is the part of the 'instruction pointer' value
> above after the colon (:) and then send the output of that in your e-mail to
> the list.  This allows us to the source line at which the fault occurred.

I'd glad to, but just found that HDD crash on my buildbox took away obj directory
for this NanoBSD... I'll rebuild it again do this next time (it won't take much time, sigh).

Btw, I did not know of this way to debug, thanks.