Date: Tue, 02 Feb 2010 19:42:53 +0200 From: Andriy Gapon <avg@icyb.net.ua> To: Julian Elischer <julian@elischer.org> Cc: freebsd-fs@freebsd.org, Stephane LAPIE <stephane.lapie@darkbsd.org>, freebsd-hardware@freebsd.org Subject: Re: [zfs][hardware] Reproducible kernel panic in 8.0-STABLE Message-ID: <4B68641D.9000201@icyb.net.ua> In-Reply-To: <4B686324.2090308@elischer.org> References: <4B682972.6030604@darkbsd.org> <4B682F29.90505@icyb.net.ua> <4B686324.2090308@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
on 02/02/2010 19:38 Julian Elischer said the following: > Andriy Gapon wrote: >> on 02/02/2010 15:32 Stephane LAPIE said the following: >>> I have a case of kernel panic that can be consistently reproduced, and >>> which I guess is related to the hardware I'm using (Marvell controllers, >>> check my pciconf -lv output below). >>> >>> The kernel panic message is always, consistently, the following : >>> >>> Sleeping thread (tid 100021, pid 0) owns a non-sleepable lock >> >> I probably won't be able to help you, but to kickstart debugging could >> you please >> run 'procstat -t 0' and determine what kernel thread has tid 100021 on >> your system? > > or in the kernel debugger after the panic, do: bt I think that in this case it may not help. I mean the stack trace. Because, I think that this panic happens after the taskqueue thread is done with its tasks and is parked waiting. > you DO have options kdb and ddb right? (I never leave home without them) > -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B68641D.9000201>