On 08-Jun-2002 Bernd Walter wrote: > Anyone knows what to do with this? > It happened on an alpha with yesterdays -current. > > panic: blockable sleep lock (sleep mutex) vnode_free_list @ >../../../kern/vfs_subr.c:2723 > panic > Stopped at Debugger+0x34: zapnot v0,#0xf,v0 <v0=0x7>
Oh, this is ugly. > db> trace > Debugger() at Debugger+0x34 > panic() at panic+0xe4 > witness_lock() at witness_lock+0xb4 > _mtx_lock_flags() at _mtx_lock_flags+0xa8 > vfree() at vfree+0x30 > vm_page_free_toq() at vm_page_free_toq+0x18c > vm_page_free() at vm_page_free+0x2c > vm_page_alloc() at vm_page_alloc+0x158 > pmap_growkernel() at pmap_growkernel+0x398 This runs in a critical section (which may not really be correct, quite possibly it should be turned off, but someone more familiar with the alpha pmap than I (dfr?) would better be able to comment) and that is why it complains when it tries to acquire a sleep mutex in vfree(). -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
