Date: Mon, 11 Dec 2006 17:40:22 -0500 From: John Baldwin <jhb@freebsd.org> To: "Marc G. Fournier" <scrappy@hub.org> Cc: freebsd-stable@freebsd.org Subject: Re: panic: sleeping thread Message-ID: <200612111740.23259.jhb@freebsd.org> In-Reply-To: <881CD0E71B5FAD4AF6E86200@ganymede.hub.org> References: <624054998B7DEF7D446796E1@ganymede.hub.org> <200612111627.23547.jhb@freebsd.org> <881CD0E71B5FAD4AF6E86200@ganymede.hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 11 December 2006 17:21, Marc G. Fournier wrote: > > --On Monday, December 11, 2006 16:27:23 -0500 John Baldwin <jhb@freebsd.org> > wrote: > > > On Saturday 09 December 2006 03:30, Marc G. Fournier wrote: > >> > >> Without a core dump, does this mean anything to anyone? > >> > >> Sleeping thread (tid 101251, pid 38200) owns a non-sleepable lock > >> panic: sleeping thread > >> cpuid = 1 > >> > >> The kernel was last upgraded: > >> > >> FreeBSD 6.2-PRERELEASE #1: Fri Nov 17 23:31:41 AST 2006 > >> > >> I'm going to build in DDB stuff right now, as I know I've seen that one > > before > >> ... but figured I'd ask and see if someone had an idea with so very little > >> information :( > > > > ddb will give a lot more useful information, can't really debug it further > > w/o that, sorry. :( > > NP, I've added DDB to my kernel, but I'm having a hard time finding out how to > break into DDB over an SSH connection ... telnet is easy, but all my HP remote > consoles use SSH ... Maybe use ssh -e none? You don't need to break into ddb though, when it panics it will print out more useful info on its own. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200612111740.23259.jhb>