#13343: QEMU XHCI Devices not bootable
--------------------------------+----------------------------
Reporter: kallisti5 | Owner: nobody
Type: bug | Status: new
Priority: high | Milestone: R1/beta1
Component: Drivers/USB/XHCI | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking: 12895
Has a Patch: 0 | Platform: All
--------------------------------+----------------------------
Comment (by kallisti5):
Interestingly, on qemu we see the following:
{{{
usb xhci -1: successfully started the controller
usb xhci -1: No-Op test...
usb xhci -1: Noop
usb xhci -1: command[0] = 17 (0x0000000000000000, 0x00000000, 0x00005c00)
usb xhci -1: Ding Dong! slot:0 endpoint 0
usb xhci -1: Event Interrupt
usb xhci -1: event[0] = 33 (0x0000000006503d40 0x05000000 0x00008401)
usb xhci -1: event[0] = 33 (0x0000000006503d40 0x05000000 0x00008401)
usb xhci -1: Received command event
usb xhci -1: event[1] = 0 (0x0000000000000000 0x00000000 0x00000000)
usb xhci -1: Command Complete. Result: 5
usb error xhci -1: unsuccessful command TRB (5)
usb xhci -1: Storing trb 0x05000000 0x00008401
usb xhci -1: No-Op unsuccessful
usb stack 0: module busses/usb/xhci successfully loaded
}}}
So:
* Noop command issued
* "something" sends command 17 (reset). 0x00005c00 is the reset TRB with
everything else 0'ed out.
* I say something because in these logs I never see the
"XHCI::ResetDevice" trace message with tracing enabled.
* We see successful results, followed by the initial No-Op being
unsuccessful (DoCommand error)
--
Ticket URL: <https://dev.haiku-os.org/ticket/13343#comment:14>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.
