Date: Thu, 07 Jul 2011 14:52:56 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Jeremy Chadwick <freebsd@jdc.parodius.com> Cc: Kostik Belousov <kostikbel@gmail.com>, FreeBSD-STABLE Mailing List <freebsd-stable@FreeBSD.org> Subject: Re: panic: spin lock held too long (RELENG_8 from today) Message-ID: <4E159E18.7070903@FreeBSD.org> In-Reply-To: <20110707114122.GA8459@icarus.home.lan> References: <4E154A63.90600@sentex.net> <4E15620A.9030608@FreeBSD.org> <20110707082027.GX48734@deviant.kiev.zoral.com.ua> <4E159959.2070401@sentex.net> <20110707114122.GA8459@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
on 07/07/2011 14:41 Jeremy Chadwick said the following:
> 1. info threads
> 2. Find the index value that matches the tid in question (in the above
> spin lock panic, that'd be tid 100109). The index value will be
> the first number shown on the left
> 3. thread {index}
Just in case, in kgdb there is a command 'tid' that does all of the above steps in
one go.
> 4. bt
>
> If this doesn't work, alternatively you can try (from the beginning)
> "thread apply all bt" and provide the output from that. (It will be
> quite lengthy, and at this point I think tid 100109 is the one of
> interest in this crash, based on what Andriy said earlier)
--
Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E159E18.7070903>