Date: Fri, 30 Jun 2006 15:00:40 GMT From: =?ISO-8859-1?Q?Eirik_=D8verby?= <ltning@anduin.net> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/99094: panic: sleeping thread (Sleeping thread ... owns a non-sleepable lock) Message-ID: <200606301500.k5UF0ePp066518@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/99094; it has been noted by GNATS. From: =?ISO-8859-1?Q?Eirik_=D8verby?= <ltning@anduin.net> To: John Baldwin <john@baldwin.cx> Cc: bug-followup@freebsd.org Subject: Re: kern/99094: panic: sleeping thread (Sleeping thread ... owns a non-sleepable lock) Date: Fri, 30 Jun 2006 16:56:14 +0200 Hm, I thought I had that in my report? I have to find a way to automate this. I've just moved the installation to a newly partitioned array, to make sure I have room for crash dumps, and I have the following in rc.conf: dumpdev="AUTO" dumpdir="/usr/crash" from my reading, that should be enough. In addition I added KDB_UNATTENDED to the kernel config, as I cannot risk that the box is down for hours before I have a chance to get to the debugger console every time. The question is: Will it actually do an automatic dump before rebooting, or will a dump *always* require manual intervention? And will a dump contain all necessary information? Thanks, /Eirik On Jun 29, 2006, at 1:26 PM, John Baldwin wrote: > You need to get a stack trace of the thread mentioned in the message > that actually misbehaved. It actually should have been printed on > the console when it panic'd since you have DDB in the kernel. > > -- > John Baldwin > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200606301500.k5UF0ePp066518>