From owner-freebsd-current@FreeBSD.ORG Tue Dec 16 07:56:15 2008 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 392AB106564A for ; Tue, 16 Dec 2008 07:56:15 +0000 (UTC) (envelope-from admin@kkip.pl) Received: from mainframe.kkip.pl (kkip.pl [87.105.164.78]) by mx1.freebsd.org (Postfix) with ESMTP id D46D38FC13 for ; Tue, 16 Dec 2008 07:56:14 +0000 (UTC) (envelope-from admin@kkip.pl) Received: from admin.admin.lan.kkip.pl ([10.66.3.254]) by mainframe.kkip.pl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LCUmp-000DTU-AL; Tue, 16 Dec 2008 08:56:13 +0100 Message-ID: <49475F1D.3030902@kkip.pl> Date: Tue, 16 Dec 2008 08:56:13 +0100 From: Bartosz Stec User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: Robert Watson References: <4940A685.7040608@psg.com> <494216C2.7080606@kkip.pl> <20081212095238.GY2038@deviant.kiev.zoral.com.ua> <49423E5A.10900@kkip.pl> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-User: admin@kkip.pl X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Spam-Score: -8.6 X-Spam-Score-Int: -85 X-Exim-Version: 4.69 (build at 13-Dec-2008 11:39:14) X-Date: 2008-12-16 08:56:13 X-Connected-IP: 10.66.3.254:4674 X-Message-Linecount: 54 X-Body-Linecount: 39 X-Message-Size: 2214 X-Body-Size: 1394 X-Received-Count: 1 X-Recipient-Count: 4 X-Local-Recipient-Count: 4 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 Cc: Kostik Belousov , Randy Bush , FreeBSD Current Subject: Re: panic: sleeping thread & bufwrite: buffer is not busy??? 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: Tue, 16 Dec 2008 07:56:15 -0000 Robert Watson pisze: > > On Fri, 12 Dec 2008, Bartosz Stec wrote: > >> OK. I'll try to build debug kernel today and I will provide >> backtrace. I forgot to mention in my last post that I saw very >> similiar (if not identical) lines to: >> >> Sleeping thread (tid 100054, pid 646) owns a non-sleepable lock >> panic: sleeping thread >> panic: bufwrite: buffer is not busy??? >> >> while checking dmesg buffer after one of the panics earlier. That's >> why I assumed it's probably the same issue. Sorry for confusion, >> they're my first steps with CURRENT and very first experience with >> kernel panic :). > > Yeah, secondary panics can significantly complicate the debugging > process, unfortunately. Another similar class of confusing cases > exist when panics occur and are then preempted during the panic by > another thread that promptly trips over state left behind by the first > thread, and panics. :-) > > Robert N M Watson > Computer Laboratory > University of Cambridge > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" Whatever it was it's gone by now. Kernel builded yesterday doesn't panic until now. I still could provide some debug information if needed. -- Bartosz Stec