Re: usb stick/hub detach panic

["Sepherosa Ziehau" <sepherosa@xxxxxxxxx>]

On 2/12/07, Simon 'corecode' Schubert <corecode@fs.ei.tum.de> wrote:
> hey,
>
> 100% reproducible panic on detach of my usb stick.  ehci is loaded as well.  UP system.
>
> #12 0xc0194734 in kprintf (fmt=0xdeadc0de <Address 0xdeadc0de out of bounds>)
>     at /usr/build/src/sys/kern/subr_prf.c:304
> #13 0xc0260cfd in usb_disconnect_port (up=0xc415a178, parent=0xdeadc0de)
>     at /usr/build/src/sys/bus/usb/usb_subr.c:1382
> #14 0xc02621a3 in uhub_detach (self=0xc415a100) at /usr/build/src/sys/bus/usb/uhub.c:610
> #15 0xc018d9ae in device_detach (dev=0xc415a100) at device_if.h:48
> #16 0xc018cef9 in device_delete_child (dev=0xdeadc0de, child=0xc415a100)
>     at /usr/build/src/sys/kern/subr_bus.c:591
> #17 0xc0260d4b in usb_disconnect_port (up=0xc698b1f4, parent=0xdeadc0de)
>     at /usr/build/src/sys/bus/usb/usb_subr.c:1387

No further child deletion means uhub has no children (i.e. umass) at
this point.  Children probably detached long before we reach here but
uhub was not informed about the detaching.

Please
1) uncomment uhub.c line 744 recompile kernel and modules.
uhub_child_detached() is the place where uhub is informed about
children detaching.  If child is not found in the upper loop, then
things probably go very wrong :(
2) give me the dmesg after you plugin the stick
3) give me the message printed on console immediately before panic

Best Regards,
sephe

--
Live Free or Die