kern/40616: panic on reboot (perhaps due to raidframe)

[dogcow%babymeat.com@localhost]

>Number:         40616
>Category:       kern
>Synopsis:       panic on reboot (perhaps due to raidframe)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Feb 11 16:45:00 +0000 2009
>Originator:     moof
>Release:        NetBSD 5.0_RC2
>Organization:
        
>Environment:
        
        
System: NetBSD burai.babymeat.com 5.0_RC2 NetBSD 5.0_RC2 (BRAID) #1: Tue Feb 10 
20:40:17 JST 2009 
dogcow%burai.babymeat.com@localhost:/crap/obj/obj/usr/src/sys/arch/i386/compile/BRAID
 i386
Architecture: i386
Machine: i386
>Description:
        
It seems that raidframe w/ a failed component might induce strange and bad
behavior upon attempting to unmount. In some cases, it hangs; in others,
it panics. Here's the kernel backtrace:
925                     dumpsys();
(gdb) bt
#0  0xc03479b2 in cpu_reboot (howto=260, bootstr=0x0) at 
/usr/src/sys/arch/i386/i386/machdep.c:925
#1  0xc02aa5a0 in panic (fmt=0xc04ab0cc "kernel %sassertion \"%s\" failed: file 
\"%s\", line %d")
    at /usr/src/sys/kern/subr_prf.c:253
#2  0xc0403899 in __kernassert (t=0xc044ad48 "diagnostic ", f=0xc046ea2f 
"/usr/src/sys/kern/vfs_subr.c", l=872, 
    e=0xc046ebb2 "LIST_EMPTY(&vp->v_dirtyblkhd)") at 
/usr/src/sys/lib/libkern/__assert.c:50
#3  0xc02ecd61 in vinvalbuf (vp=0xcdbbea20, flags=<value optimized out>, 
cred=0xffffffff, l=0xcdbb7ae0, catch=false, slptimeo=0)
    at /usr/src/sys/kern/vfs_subr.c:872
872                     KASSERT(LIST_EMPTY(&vp->v_dirtyblkhd));
#4  0xc0305c9d in spec_close (v=0xcdc82b28) at 
/usr/src/sys/miscfs/specfs/spec_vnops.c:935
935                     error = vinvalbuf(vp, V_SAVE, ap->a_cred, curlwp, 0, 0);
#5  0xc02fe8cc in VOP_CLOSE (vp=0xcdbbea20, fflag=3, cred=0xffffffff) at 
/usr/src/sys/kern/vnode_if.c:314
314             error = (VCALL(vp, VOFFSET(vop_close), &a));
#6  0xc020bfa4 in ffs_unmount (mp=0xccf4a204, mntflags=524288) at 
/usr/src/sys/ufs/ffs/ffs_vfsops.c:1542
1542            (void)VOP_CLOSE(ump->um_devvp, fs->fs_ronly ? FREAD : FREAD | 
FWRITE,
#7  0xc02eadc6 in VFS_UNMOUNT (mp=0xccf4a204, a=524288) at 
/usr/src/sys/kern/vfs_subr.c:2938
2938            error = (*(mp->mnt_op->vfs_unmount))(mp, a);
#8  0xc02f404c in dounmount (mp=0xccf4a204, flags=524288, l=0xcdbb7ae0) at 
/usr/src/sys/kern/vfs_syscalls.c:767
767                     error = VFS_UNMOUNT(mp, flags);
#9  0xc02eb9e6 in vfs_unmountall (l=0xcdbb7ae0) at 
/usr/src/sys/kern/vfs_subr.c:2287
2287                    if ((error = dounmount(mp, MNT_FORCE, l)) != 0) {
#10 0xc02ebadd in vfs_shutdown () at /usr/src/sys/kern/vfs_subr.c:2344
2344            vfs_unmountall(l);

I can provide the kernel dump, the debug kernel, and a snap of the tree
if desired.
>How-To-Repeat:
        
mount /mnt /dev/raid0; echo poo > /mnt/x; reboot

I'm presuming this is some raidframe wonkiness due to having raid0 and a
failed component (leaving precisely one working component), but I'm not
positive.
>Fix:
        

>Unformatted:
        
        
 Source is as of Wed Feb 11 15:22:13 UTC 2009