recent USB MFCs cause panics

[Julian Elischer]

Helge Oldach wrote:

>Julian Elischer:
>  
>
>>any chance of getting a stack trace or a core dump?
>>    
>>
>
>Ok, here we go:
>
>  
>

>#6  0xc016f772 in device_get_ivars (dev=0x0) at /usr/src/sys/kern/subr_bus.c:998
>#7  0xc0237d5d in usb_disconnect_port (up=0xc18971c4, parent=0xc1897280)
>    at /usr/src/sys/dev/usb/usb_subr.c:1440
>  
>
can you go to this frame
"up 7"
and print dev and  i and *dev

>#8  0xc02423b4 in uhub_explore (dev=0xc1897380) at /usr/src/sys/dev/usb/uhub.c:488
>#9  0xc02424f1 in uhub_explore (dev=0xc1813400) at /usr/src/sys/dev/usb/uhub.c:571
>#10 0xc02340cf in usb_discover (v=0xc18110c0) at /usr/src/sys/dev/usb/usb.c:745
>#11 0xc0233b92 in usb_event_thread (arg=0xc18110c0) at /usr/src/sys/dev/usb/usb.c:431
>(kgdb) list *0xc016f772
>0xc016f772 is in device_get_ivars (/usr/src/sys/kern/subr_bus.c:999).
>994	}
>995	
>996	void *
>997	device_get_ivars(device_t dev)
>998	{
>999	    return dev->ivars;
>1000	}
>1001	
>1002	void
>1003	device_set_ivars(device_t dev, void * ivars)
>(kgdb) quit
>  
>