Date: Tue, 2 Mar 2004 17:08:43 -0500 From: John Baldwin <jhb@FreeBSD.org> To: des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern subr_sleepqueue.c Message-ID: <200403021708.43422.jhb@FreeBSD.org> In-Reply-To: <xzpwu63udyx.fsf@dwp.des.no> References: <200403021502.i22F28vF032585@repoman.freebsd.org> <xzpwu63udyx.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 02 March 2004 04:38 pm, Dag-Erling Smørgrav wrote:
> John Baldwin <jhb@FreeBSD.org> writes:
> > Log:
> > Always assert that the passed in lock is the same as the saved lock in
> > the sleep queue now that the one abnormal case has been fixed.
>
> I believe you've missed at least one other abnormal case: either
> linux_rt_sigsuspend used to trigger the "mismatched locks" warning,
> and now just gives me a panic. To top it all off, the box freezes
> right after the Debugger("panic") line, without dropping to ddb.
I never saw that case and this is the first I've heard of it. ddb tends to
freeze when you enter it holding a spin lock. Do you have any log messages
from the mis-matched locks for msleep?
--
John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200403021708.43422.jhb>