Date: Sat, 17 Dec 2011 19:41:15 -0800 From: mdf@FreeBSD.org To: Alexander Kabaev <kabaev@gmail.com> Cc: Current FreeBSD <freebsd-current@freebsd.org>, "O. Hartmann" <ohartman@zedat.fu-berlin.de> Subject: Re: Sleeping thread (tid 100033, pid 16): panic in FreeBSD 10.0-CURRENT/amd64 r228662 Message-ID: <CAMBSHm_MHAhTMafuHkMh_CAdOcU4zgJUgbzTNhLvajDFSp45UA@mail.gmail.com> In-Reply-To: <20111217204514.2fa77ea2@kan.dyndns.org> References: <4EED2F1C.2060409@zedat.fu-berlin.de> <20111217204514.2fa77ea2@kan.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Dec 17, 2011 at 5:45 PM, Alexander Kabaev <kabaev@gmail.com> wrote: > On Sun, 18 Dec 2011 01:09:00 +0100 > "O. Hartmann" <ohartman@zedat.fu-berlin.de> wrote: > >> Sleeping thread (tid 100033, pid 16) owns a non sleepable lock >> panic: sleeping thread >> cpuid = 0 >> >> PID 16 is always USB on my box. > > You really need to give us a backtrace when you quote panics. It is > impossible to make any sense of the above panic message without more > context. In the case of this panic, the stack of the thread which panics is useless; it's someone trying to propagate priority that discovered it. A backtrace on tid 100033 would be useful. With WITNESS enabled, it's possible to have this panic display the stack of the incorrectly sleeping thread at the time it acquired the lock, as well, but this code isn't in CURRENT or any release. I have a patch at $WORK I can dig up on Monday. Cheers, matthew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMBSHm_MHAhTMafuHkMh_CAdOcU4zgJUgbzTNhLvajDFSp45UA>