Date: Tue, 16 Dec 2008 08:56:13 +0100 From: Bartosz Stec <admin@kkip.pl> To: Robert Watson <rwatson@FreeBSD.org> Cc: Kostik Belousov <kostikbel@gmail.com>, Randy Bush <randy@psg.com>, FreeBSD Current <current@freebsd.org> Subject: Re: panic: sleeping thread & bufwrite: buffer is not busy??? Message-ID: <49475F1D.3030902@kkip.pl> In-Reply-To: <alpine.BSF.1.10.0812121039180.41885@fledge.watson.org> References: <4940A685.7040608@psg.com> <494216C2.7080606@kkip.pl> <20081212095238.GY2038@deviant.kiev.zoral.com.ua> <49423E5A.10900@kkip.pl> <alpine.BSF.1.10.0812121039180.41885@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49475F1D.3030902>