Date: Wed, 20 Nov 2002 12:01:41 -0500 (EST) From: Robert Watson <rwatson@freebsd.org> To: "Joel M. Baldwin" <qumqats@outel.org> Cc: current@freebsd.org Subject: Re: panic: sleeping thread owns a mutex - with debug traceback Message-ID: <Pine.NEB.3.96L.1021120120103.40737Z-100000@fledge.watson.org> In-Reply-To: <Pine.NEB.3.96L.1021120115452.40737Y-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 20 Nov 2002, Robert Watson wrote: > Hmm. Another thread has decided to sleep while holding an inpcb mutex. > Any chance this can be reproduced while running WITNESS? If so, you > should get a panic earlier when the other thread sleeps in the first > place. The easiest way to do that is if you can reproduce the panic with > WITNESS. If you can't reproduce the panic, you may be able to extract > this from your system core using gdb -- you want to figure out what the > thread owner of the mutex is doing -- in the context of the kassert() > below, td is the pointer to the thread that owns the mutex. I'm not sure > how to extract a stack trace from that information, unfortunately, perhaps > someone can give us pointers. (note: td from the priority_propagate() > argument is shadowed, which is annoying). Ack. I mis-read. You want the stack from thread td1 (the mutex owner), not thread td. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1021120120103.40737Z-100000>