Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Mutex error



And this can be triggered by adding one of the following in /etc/rc.conf:

fsck_flags="-y -P"
fsck_flags="-y"
fsck_flags="-P"

In case of -P (and if the filesystem is dirty), a nice progress bar is show but if I type y to fix errors I get this mutex error. In case of "-y -P" and "-y" I get this mutex error. Not defining fsck_flags in rc.conf makes the boot successful. It seems this "assume yes as the answer to all operator questions" does something bad.


Another thing, running "halt -p" still causes this panic:

May 26 09:47:12 n38 halt: halted by martti
panic: kernel diagnostic assertion "!fd_isused(fdp, fd)" failed: file "/home/src/sys/kern/kern_descrip.c", line 175
Begin traceback...
uvm_fault(0xc9e1a350, 0, 1) -> 0xe
fatal page fault in supervisor mode
trap type 6 code 0 eip c0136121 cs 9 eflags 10246 cr2 6 ilevel 0
panic: trap
Faulted in mid-traceback; aborting...
dumping to dev 142,1 offset 534615
dump device bad



# zcat netbsd-XEN3PAE_DOMU.gz | strings | grep kern_descrip.c
$NetBSD: kern_descrip.c,v 1.193 2009/05/26 00:42:33 ad Exp $

Martti


Home | Main Index | Thread Index | Old Index