Home » Mailing list archives » openbsd-misc » 2010 » July » 19

i386 panic - mtx_enter: locking against myself

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
[view in full thread]
From: Martin Pelikán
Subject: i386 panic - mtx_enter: locking against myself
Date: Monday, July 19, 2010 - 5:34 am

Hello everyone.
Yesterday I compiled some stuff from ports, when my i386 -current (about
two days old) paniced (onproc was one of those cc(1)):
Debugger(), panic(),
mtx_enter+0x5a(d0a2fc20, d2bae000, d2baf000, 0, 0)
uvm_pseg_release+0x6b
uvm_swap_allocpages+0x8d9
uvm_swap_get+0x38
uvm_fault_anonget+0x169
uvm_fault+0x4bd(d2e83ec4, 88388000, 0, 1, cfbecb58)

"show panic" showed "mtx_enter: locking against myself". I probably
went out of memory (just 128M ram + 300M swap). Lastly, I unfortunately
mistyped "boot sync" instead of "boot crash", so I don't have any other
information except from this small piece of paper :-(
I found the place in the code, but don't really understand the meaning
of the #ifdef DIAGNOSTIC blocks inside mutex.S in mtx_enter(). Can
anyone explain me what is this check for?
Thanks in advance, will post more details after I reproduce this.

-- 
Martin Pelikan
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
Messages in current thread:
i386 panic - mtx_enter: locking against myself, Martin Pelikán, (Mon Jul 19, 5:34 am)
Re: i386 panic - mtx_enter: locking against myself, Owain Ainsworth, (Mon Jul 19, 10:06 am)