panic: spin lock held too long (RELENG_8 from today)

[Andriy Gapon]

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