Re: Another "impossible" mutex panic (Re: Panic in wait4())

From: John Baldwin <jhb_at_FreeBSD.org>
Date: Tue, 15 Apr 2003 16:07:09 -0400 (EDT)
On 15-Apr-2003 Kris Kennaway wrote:
> On Tue, Apr 15, 2003 at 10:29:29AM -0700, Kris Kennaway wrote:
>> On Tue, Mar 25, 2003 at 02:22:04PM -0800, Kris Kennaway wrote:
>> > I just got this on bento (running a kernel from Mar 17).  It was under
>> > heavy disk load at the time, which may or may not be relevant.
>> > 
>> > Kris
>> > 
>> > panic: mtx_lock() of spin mutex %s _at_ %s:%d
>> > panic messages:
>> 
>> I just got another one of these "impossible" panics on one of the
>> gohans (impossible because according to gdb the mutex is not a spin
>> mutex, so the assertion should not have fired).
> 
> I got this a third and fourth time on another two gohans (same
> backtrace).

Best guess is that someone is doing a lock on a mutex that has
been destroyed.  Possibly the memory has been overwritten by
something else.  What does gdb show for the contents of the
actual mutex?

-- 

John Baldwin <jhb_at_FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/
Received on Tue Apr 15 2003 - 11:07:11 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:03 UTC