usb/117719: umass plugging with hald running causes kernel panics on 7.0

[Kyryll A Mirnenko aka Mirya]

The following reply was made to PR usb/117719; it has been noted by GNATS.

From: Kyryll A Mirnenko aka Mirya <mirya at zoc.com.ua>
To: bug-followup at freebsd.org,
 mirya at zoc.com.ua
Cc:  
Subject: Re: usb/117719: umass plugging with hald running causes kernel panics on 7.0
Date: Fri, 16 Nov 2007 14:22:24 +0300

 The bug stays the same with BETA2. Here's the kernel stack trace:
 
 # plugging in the device
 umass0: <Western Digital External HDD, class 0/0, rev 2.00/2.40, addr 2> on 
 uhub3
 da0 at umass-sim0 bus 0 target 0 lun 0
 da0: <WDC WD12 00UE-00KVT0 0000> Fixed Direct Access SCSI-0 device
 da0: 40.000MB/s transfers
 da0: 114473MB (234441648 512 byte sectors: 255H 63S/T 14593C)
 # in a few moments...
 panic: msleep
 KDB: stack backtrace
 db_trace_self_wrapper(c0968c2f,c0a19c40,c09697de,cc12cb30,cc12cb30,...) at 
 0xc047b4a6 = db_trace_self_wrapper+0x26
 panic(c09697de,c0a19630,c09697ad,c094a106,8,...) at 0xc05d9bef = panic+0xdf
 _sleep(0,c0a19630,100,c094a106,0,...) at 0xc05e2a57 = _sleep+0x87
 sgread(c31c1f00,cc12cc5c,0,168,0,...) at 0xc046d91f = sgread+0xff
 giant_read(c31c1f00,cc12cc5c,0,0,c00,...) at 0xc05aa188 = giant_read+0x48
 devfs_read_f(c2faa4c8,cc12cc5c,c2809f00,0,c31be630,...) at 0xc0539746 = 
 devfs_read_f+0x76
 dofileread(cc12cc5c,ffffffff,ffffffff,0,c2faa4c8,...) at 0xc061423c = 
 dofileread+0x6c
 kern_readv(c31be630,4,cc12cc5c,cc12cc7c,1,...) at 0xc0615e98 = kern_readv+0x58
 read(c31be630,cc12ccf8,c,c096e2b3,c09c97c8,...) at 0xc0615f80 = read+0x50
 syscall(cc12cd38) at 0xc90642a = syscall+0x13a
 Xint0x80_syscall() at 0xc08eeb20 = Xint0x80_syscall+0x20
 --- syscall (3, FreeBSD ELF 32, read), eip = 0x48381673, esp = 0xbfbfe65c, ebp 
 = 0xbfbfe68b ---
 
 I also was able to get the same crash when unplugging the device above 
 (plugged in before boot, that doesn't cause the panic as stated in my 
 previous message) and plugging in another USB disk with regular FAT 
 at /dev/ad0s1 (though simply plugging in the 2nd disk without having the 1st 
 plugged doesn't cause the panic)