kern/71357: Panic when starting vinum at boot

[Mark Derbyshire]

>Number:         71357
>Category:       kern
>Synopsis:       Panic when starting vinum at boot
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Sep 04 03:10:30 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator:     Mark Derbyshire
>Release:        FreeBSD 5.3-BETA2
>Organization:
>Environment:
FreeBSD newbsd.taom.com 5.3-BETA2 FreeBSD 5.3-BETA2 #1: Sat Aug 28 21:29:15 UTC 2004     root at mack.dcsl.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386

ABIT VT7 mainboard
>Description:
      When start_vinum="YES" is set in rc.conf, system panics on boot even when there are no vinum disks. Handcopied console messages:

Mounting root from ufs:/dev/ad0s1a
Pre-seeding PRNG: kickstart.
Loading configuration files.
Entropy harvesting: interrupts ethernet point_to_point kickstart.
vinum: loaded
panic: umount: dangling vnode
cpuid = 0;
KDB: enter: panic
[thread 100063]
stopped at   kdb_enter+0x2b: nop
db> trace
kdb_enter+0x2b
panic+0x131
vfs_mount_destroy+0x1d
getdiskbyname+0x173
open_drive+0x21
init_drive+0x1c
read_drive_label+0x11
check_drive+0x4c
vinum_scan_disk+0x220
vinum_super_ioctl+0x4d0
vinum_ioctl+0x39
spec_ioctl+0x152
spec_vnoperate+0x13
vn_ioctl+0x19f
ioctl+0x3e0
syscall(2f, 2f, 2f, 0, 1)+0x217
Xint0x80_syscall+0x1f
>How-To-Repeat:
      Add start_vinum="YES" to rc.conf and reboot. My system configuration contained a PATA drive as IDE 1 bus master, a DVD as IDE 2 bus master. The mainboard has two SATA channels that normally attach to the vinum drives, but these were not connected at the time.
>Fix:
      
>Release-Note:
>Audit-Trail:
>Unformatted: