On Mon, Jan 24, 2005 at 05:56:48AM -0500, Jeff Roberson wrote: > That's all of it. If you wait for your cvsup mirror to catch up, you can > try running with a smpsafe vfs by setting the debug.mpsafevfs tunable. > This option requires mpsafevm as well. I have two known bugs that have > only been triggered by peter holm's excellent stress suite, but none are > known to cause problems if mpsafevfs is disabled, and none of them have > been seen on normal systems to my knowledge. This happened on a machine with mpsafevfs=1 and DEBUG_LOCKS panic: vm_fault: fault on nofault entry, addr: deadc000 cpuid = 1 KDB: enter: panic [thread pid 13312 tid 100135 ] Stopped at kdb_enter+0x30: leave db> tr Tracing pid 13312 tid 100135 td 0xc383e730 kdb_enter(c06f4e4a,1,c0709378,bb6,c383e730) at kdb_enter+0x30 panic(c0708e4f,deadc000,1,edfe9a30,edfe9a20) at panic+0x13e vm_fault(c1059000,deadc000,1,0,c383e730) at vm_fault+0x23a trap_pfault(edfe9af8,0,deadc0de,35,deadc0de) at trap_pfault+0x166 trap(ffff0018,7fff0010,10,c06f42be,deadc0de) at trap+0x34c calltrap() at calltrap+0x5 --- trap 0xc, eip = 0xc05900e8, esp = 0xedfe9b38, ebp = 0xedfe9b38 --- strlen(deadc0de,edfe9c24,edfe9b78,0,a) at strlen+0x8 kvprintf(c06f42a3,c053d716,edfe9c24,a,edfe9c68) at kvprintf+0x693 vsnprintf(c0754a60,100,c06f42a3,edfe9c64,c383e730) at vsnprintf+0x3c panic(c06f42a3,deadc0de,c06fd180,390,c0516286) at panic+0xb8 _mtx_lock_flags(c3766860,0,c06fd180,390,c0754820) at _mtx_lock_flags+0x6b dounmount(c3766800,8080000,c383e730,37b,508ff10) at dounmount+0x59 unmount(c383e730,edfe9d14,8,28149000,2) at unmount+0x271 syscall(2f,2f,2f,804a458,804f421) at syscall+0x271 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (22, FreeBSD ELF32, unmount), eip = 0x280b8af7, esp = 0xbfbfe4ec, ebp = 0xbfbfe598 --- Kris
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:26 UTC