Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 23 Nov 2004 11:36:49 -0500
From:      John Baldwin <jhb@FreeBSD.org>
To:        freebsd-current@FreeBSD.org
Cc:        phk@FreeBSD.org
Subject:   Re: panic: sleeping thread owns a non-sleepable lock
Message-ID:  <200411231136.49362.jhb@FreeBSD.org>
In-Reply-To: <20041123011307.GA38559@peter.osted.lan>
References:  <20041122143804.GA36649@peter.osted.lan> <200411221657.36659.jhb@FreeBSD.org> <20041123011307.GA38559@peter.osted.lan>

next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 22 November 2004 08:13 pm, Peter Holm wrote:
> On Mon, Nov 22, 2004 at 04:57:36PM -0500, John Baldwin wrote:
> > On Monday 22 November 2004 09:38 am, Peter Holm wrote:
> > > During stress test with GENERIC HEAD from Nov 20 08:40 UTC I got:
> > > Sleeping on "fdesc" with the following non-sleepable locks held:
> > > exclusive sleep mutex fdesc r = 0 (0xc08d15a0) locked @
> > > kern/kern_descrip.c:2425 and then
> > > panic: sleeping thread (pid 92279) owns a non-sleepable lock
> > >
> > > http://www.holm.cc/stress/log/cons89.html
> >
> > Yes, the panic is a result of the earlier warning.  Poul-Henning touched
> > this code last, so it is probably something for him to look at.  I'm
> > unsure how msleep() is getting called, however.  The turnstile panic is
> > not important, can you find the thread that went to sleep (should be pid
> > 92279) and get stack trace for that?
>
> The ddb trace is in the log, just before call doadump. Let me know if you
> need any gdb output.

Ok, can you use gdb to get the source/file of 'sysctl_kern_file+0x1ae'?

-- 
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?200411231136.49362.jhb>