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

[Kyryll A Mirnenko]

>Number:         117719
>Category:       usb
>Synopsis:       umass plugging with hald running causes kernel panics on 7.0
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-usb
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Oct 31 13:50:01 UTC 2007
>Closed-Date:
>Last-Modified:
>Originator:     Kyryll A Mirnenko
>Release:        RELENG_7
>Organization:
>Environment:
FreeBSD miryanote 7.0-BETA1 FreeBSD 7.0-BETA1 #0: Tue Oct 30 18:58:45 EET 2007     mirya at miryanote:/usr/src/sys/i386/compile/MY-LITE  i386
>Description:
I have recent RELENG_7 with hald running (yes, hal port was rebuilt twice). I'm trying to plug in an USB hard disk, here's devices list from dmesg leading to it:

acpi0: <HP 3084> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pci0: <base peripheral> at device 0.1 (no driver attached)
pci0: <base peripheral> at device 0.3 (no driver attached)
ehci0: <Intel 82801DB/L/M (ICH4) USB 2.0 controller> mem 0xe0100000-0xe01003ff irq 11 at device 29.7 on pci0
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb3: EHCI version 1.0
usb3: companion controllers, 2 ports each: usb0 usb1 usb2
usb3: <Intel 82801DB/L/M (ICH4) USB 2.0 controller> on ehci0
usb3: USB revision 2.0
uhub3: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb3
uhub3: 6 ports with 6 removable, self powered
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)

The unusual thing with this disk it that it has a GELI-encrypted FFS put in the root, e.g. without any partitions, so you'll have /dev/da0 and /dev/da0.eli after `geli attach`.

THE PROBLEM: after plugging it in the system crashes with hald-probe-storage as a current process.

Other information useful:
1) when the disk is plugged in before boot (and then hald is run on boot), everything works just well; the same if hald is not run at all
2) the same experiment with a partitioned and FAT-formatted USB flash drive (so I have FAT at /dev/da0s1) didn't cause the panic.
3) the described didn't cause any panics on 6.2

I'll try to get a stacktrace soon and test it with other umass devices
>How-To-Repeat:
1) create a GELI-encrypted FFS in the root of some umass device (so it will be da?.eli, hope other umass devices will work the same)
2) run hald (it runs for me at the boot time)
3) plug in the umass device from (1)
4) except a panic in a few moments
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted: