Date: Fri, 12 Dec 2008 15:42:31 +0000 (GMT) From: Robert Watson <rwatson@FreeBSD.org> To: Roman Divacky <rdivacky@FreeBSD.org> Cc: Kostik Belousov <kostikbel@gmail.com>, Randy Bush <randy@psg.com>, Bartosz Stec <admin@kkip.pl>, FreeBSD Current <current@FreeBSD.org> Subject: Re: panic: sleeping thread & bufwrite: buffer is not busy??? Message-ID: <alpine.BSF.1.10.0812121541490.59182@fledge.watson.org> In-Reply-To: <20081212112030.GA74265@freebsd.org> References: <4940A685.7040608@psg.com> <494216C2.7080606@kkip.pl> <20081212095238.GY2038@deviant.kiev.zoral.com.ua> <alpine.BSF.1.10.0812121037360.41885@fledge.watson.org> <20081212112030.GA74265@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 12 Dec 2008, Roman Divacky wrote: >>> You are mixing the issues without a reason. To claim that you problem is >>> similar, you need to show the similar backtrace. The panic shown is the >>> late manifestation of a problem, it is kind a catch-all for some sort of >>> locking issues. >> >> This is the second report of weird rwlock-related panics in a week. We >> should read the code on this one closely, but I can't help but notice that >> it's similar to Roman's report of an rwlock-related panic. Was there a >> locking/scheduling change in the last week or two in -current that could >> explain these symptoms? > > I still have the vmcore from the crash... can it help? I think the most important thing is to see the contents of *inp and *inp->inp_lock.lock_object. Robert N M Watson Computer Laboratory University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.1.10.0812121541490.59182>