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. Another one with your latest sources and mpsafevfs=1: panic(c06f077a,0,c06f0690,ee,c977bb80) at panic+0xd6 lockmgr(de75eed8,90022,ca369450,c977bb80,12b) at lockmgr+0x3cd getdirtybuf(de75ee78,ca369450,1,1298,2) at getdirtybuf+0xf0 softdep_sync_metadata(f1546800,0,c07044ab,10d,1) at softdep_sync_metadata+0x11e ffs_fsync(f1546800,ca53d834,10880,f154695c,c062bd0b) at ffs_fsync+0x397 VOP_FSYNC_AP(f1546800,1ff,0,200,c675ec80) at VOP_FSYNC_AP+0x76 ffs_truncate(ca369450,200,0,880,c675ec80) at ffs_truncate+0xa67 ufs_direnter(ca369450,0,f1546a84,f1546c48,0) at ufs_direnter+0x91b ufs_rename(f1546be0,ca06d8a0,c977bb80,f1546ccc,c058cfe4) at ufs_rename+0x72c VOP_RENAME_AP(f1546be0,f1546bdc,101,1,0) at VOP_RENAME_AP+0x76 kern_rename(c977bb80,808c060,bfbfb2a0,0,f1546d40) at kern_rename+0x2fe rename(c977bb80,f1546d14,8,3ff,2) at rename+0x29 syscall(809002f,bfbf002f,bfbe002f,808c060,bfbfb2a0) at syscall+0x271 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (128, FreeBSD ELF32, rename), eip = 0x281f72d7, esp = 0xbfbea62c, ebp = 0xbfbfbab8 --- The panic string was lost (cascading panics as usual), but: db> x/s 0xc06f24de 0xc06f24de: panic: %s\012 db> x/s 0xc06f0690 0xc06f0690: ../../../kern/kern_lock.c kern_lock.c:238 is the following in lockmgr(): 1.45 (alfred 20-Apr-01): if (flags & LK_INTERLOCK) { 1.46 (alfred 28-Apr-01): mtx_assert(interlkp, MA_OWNED | MA_NOTRECURSED); 1.41 (bmilekic 09-Feb-01): mtx_unlock(interlkp); Unfortunately: db> show lockedvnods Locked vnodes panic: Assertion td->td_turnstile != NULL failed at ../../../kern/subr_turnstile.c:544 cpuid = 0 panic: sched_bind: cannot bind non-running thread cpuid = 0 panic: sched_bind: cannot bind non-running thread cpuid = 0 [...] Kris
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:26 UTC