Re: boot panic on current(04.20)

> If you type "bt" in the debugger, what are the USB functions being called?
>
>   
db> bt

Tracing pid 46 tid 100059 td 0xc76ced20
strcmp(0,c0d4b100,c77b0000,c77b037e,ea44ebe8,...) at strcmp+0x23
malloc_desc2type(c0d4b100,0,c0d4b8e7,912,ffffffff,...) at 
malloc_desc2type+0x24
usb2_notify_addq(c0d4c056,c77b02f8,c77b037e,c772f420,2,...) at 
usb2_notify_addq+
0x3d
usb2_alloc_device(c7a41280,c7a33cf0,0,0,0,...) at usb2_alloc_device+0x9e8
usb2_bus_attach(c7a33e24,0,c0d53972,51,c0688c49,...) at 
usb2_bus_attach+0x128
usb2_process(c7a33d74,ea44ed38,bfbfed8c,0,0,...) at usb2_process+0xda
fork_exit(c0d3d5f0,c7a33d74,ea44ed38) at fork_exit+0x91
fork_trampoline() at fork_trampoline+0x8
--- trap 0, eip = 0, esp = 0xea44ed70, ebp = 0 ---


   I think more or less like wsk. Mmmm could it be related to the sysctl 
-a problem discussed today ? Will try recompiling fuse and kqemu. Will 
let you know.

   Regards,

   Gus