On Mon, Nov 22, 2010 at 12:46:05PM +0100, MERIGHI Marcus wrote: > http://marc.info/?l=openbsd-bugs&m=122300840417886&w=2 > > [email protected] ([email protected]), 2008.10.02 22:08: > > Synopsis: panic after removal of cardbus card if an usb device is being > used > > > > State-Changed-From-To: open->analyzed > > State-Changed-By: deraadt > > State-Changed-When: Thu Oct 2 16:08:54 MDT 2008 > > State-Changed-Why: > > Please re-test this PR and respond as to whether this problem still > > exists. Our PR database is full of many old errors, and this is an > > effort to seperate the repaired bugs from unrepaired bugs. Please > > use http://cvs.openbsd.org/query-pr.html to refresh your memory about > > the PR. Thank you. > > unfortunately this is not a PR database error, the problem is still > there, as opposed to the original PR it even occurs without using any > device via the pcmcia uhub. below are two tests (labeled "test 1:", > "test 2:"), both with attach-messages, detach-messages and ddb output > as well as the regular sendbug output (labeled "sendbug output:") > with the device attached. > > test 1: > > attach: > uhci3 at cardbus1 dev 0 function 0 "VIA VT83C572 USB" rev 0x62: irq 11 > usb3 at uhci3: USB revision 1.0 > uhub3 at usb3 "VIA UHCI root hub" rev 1.00/1.00 addr 1 > uhci4 at cardbus1 dev 0 function 1 "VIA VT83C572 USB" rev 0x62: irq 11 > usb4 at uhci4: USB revision 1.0 > uhub4 at usb4 "VIA UHCI root hub" rev 1.00/1.00 addr 1 > ehci0 at cardbus1 dev 0 function 2 "VIA VT6202 USB" rev 0x65: irq 11 > usb5 at ehci0: USB revision 2.0 > uhub5 at usb5 "VIA EHCI root hub" rev 2.00/1.00 addr 1 > > detach: > uhci3: host system error > uhci3: host controller process error > uhci3: host controller halted > uhci4: host system error > uhci4: host controller process error > uhci4: host controller halted > ehci0: unrecoverable error, controller halted > ehci0: blocking intrs 0x10 > uhub3 detached > usb3 detached > uhci3 detached > uhub4 detached > usb4 detached > uhci4 detached > uhub5 detached > uvm_fault(0xd0a1a040, 0x0, 0, 1) -> e > kernel: page fault trap, code=0 > Stopped at usbd_do_request_flags_pipe+0x18: movl 0x258(%eax),%ec > x > ddb> > ddb> trace > usbd_do_request_flags_pipe(d1f3ac00,2,dc16aef8,0,0) at > usbd_do_request_flags_pi > pe+0x18 > usbd_do_request_flags(d1f3ac00,dc16aef8,0,0,0) at usbd_do_request_flags+0x3c > usbd_do_request(d1f3ac00,dc16aef8,0,d079ab1d,d0a0f200) at > usbd_do_request+0x37 > usbd_reset_port(d1f3ac00,1,d1f3a980,d03e1d87,40) at usbd_reset_port+0x42 > uhub_explore(d1f3ac00,d1f3accc,dc16af8c,d07978b6,d1f3ac80) at > uhub_explore+0x16 > f > usb_explore(d1f3ac80,20,d097e6b6,0,d6d7f768) at usb_explore+0x3f > usb_task_thread(d6d7f768) at usb_task_thread+0x76
does the device work? does the kernel see devices attached to the USB? -- [email protected] SDF Public Access UNIX System - http://sdf.lonestar.org
