On a very current -current, I get this reproducable panic when
I try to revive a vinum plex:
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
cpuid = 0; lapic.id = 01000000
fault virtual address = 0x1a0
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc015f01d
stack pointer = 0x10:0xdfad6ca0
frame pointer = 0x10:0xdfad6cac
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = resume, IOPL = 0
current process = 612 (vinum)
kernel: type 12 trap, code=0
CPU0 stopping CPUs: 0x00000002... stopped.
Stopped at mtx_enter_hard+0x125: movl 0x1a0(%edx),%eax
db> trace
mtx_enter_hard(c28e3930,0,0,0,c28e3900) at mtx_enter_hard+0x125
_mtx_enter(c28e3930,0,c2830240,87,0) at _mtx_enter+0x132
lockrange(0,cec3f330,c28e3900,c25f6000,2) at lockrange+0x31
revive_block(2,c25f6000,c2816d00,dfa90a80,0) at revive_block+0x2f6
start_object(c25f6000,0,c2816d00,dfa90a80,d9d4ac30) at start_object+0x10d
setstate(c25f6000,dfad6e08,c2816d00,c25f6000,dfad6dd8) at setstate+0x1fd
vinumioctl(c2816d00,c400464c,c25f6000,3,dfa90a80) at vinumioctl+0x4c1
spec_ioctl(dfad6e08,dfad6df0,c020e5f1,dfad6e08,dfad6e98) at spec_ioctl+0x2c
spec_vnoperate(dfad6e08,dfad6e98,c019e8ac,dfad6e08,c292ddc0) at spec_vnoperate+0x15
ufs_vnoperatespec(dfad6e08,c292ddc0,0,400,c0283780) at ufs_vnoperatespec+0x15
vn_ioctl(c292ddc0,c400464c,c25f6000,dfa90a80,dfa90a80) at vn_ioctl+0x110
ioctl(dfa90a80,dfad6f80,bfbff64c,bfbff1cc,2) at ioctl+0x20a
syscall2(2f,2f,2f,2,bfbff1cc) at syscall2+0x2a0
Xint0x80_syscall() at Xint0x80_syscall+0x23
--- syscall 0x36, eip = 0x8072ecc, esp = 0xbfbff1a0, ebp = 0xbfbff68c ---
db>
Dunno if this is actually vinum, or it is caused by the mere fact
that I'm trying to run -current.
Anyway, it happens in UP as well as SMP, and I am not using DEVFS.
Oh, one more thing: the vinum volume (raid01) apparantly runs without
any problems - as long as I don't try to revive a faulty plex within
the volume.
/Niels Chr.
--
Niels Christian Bank-Pedersen, NCB1-RIPE.
"Hey, are any of you guys out there actually *using* RFC 2549?"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
