Re: [Qemu-devel] Bug (Regression?) in hw/usb/hcd-uhci.c causes failure of ICH9 host controller and attached Xbox 360 Wireless Receiver

[Joe Clifford <joe@thunderbug.co.uk>]

On 21/04/16 16:41, Joe Clifford wrote:
> On 21/04/16 15:17, Gerd Hoffmann wrote:
>>> - When booting without the device attached, then running the device
>>> manager to watch what happens, inserting the device results in it
>>> appearing as normal for ~30-50 seconds before the device manager view
>>> refreshes and the yellow warning triangle appears next to the IC9 UHCI
>>> device and the Xbox USB device disappears. (See screen-shot
>>> w7-devman1.png and w7-devman2.png). Sometimes this results in
>>> unresponsive keyboard and mouse in the guest and other times not.
>> Ok, can you try
>> https://www.kraxel.org/cgit/qemu/commit/?h=work/usb-uhci-usb-host-debug&id=f8a731045bbe46a315622a1cc76afc6deb14534e 
>>
>> ?
>>
>> Probably the message gets printed when the yellow warning appears in
>> device manager.
>>
>> thanks,
>>    Gerd
>>
> Starting the guest VM with the UHCI debug patch and the device 
> unplugged results in these two lines just after it starts:
>
> uhci_handle_td: invalid pid token 0x0, raising HCPERR
> uhci_handle_td: invalid pid token 0x0, raising HCPERR
>
> and then the same line repeated 18 times once the Windows desktop is 
> reached and the device is plugged in.
>
> When the yellow warning appears in the device manager, nothing is 
> printed to stderr.
>
> Shutdown of the guest results in 7 more identical lines.
>
> Starting the guest with the device already plugged in is not much 
> different; 20 lines of 'uhci_handle_td: invalid pid token 0x0, raising 
> HCPERR' until desktop is reached, nothing when yellow exclamation 
> appears, 7 more lines on shutdown.
>
> There are various warnings printed in the host syslog that occur in 
> line with the guest starting, the device being plugged in and guest 
> shutdown - you can see the output here:
>
> https://gist.github.com/7hunderbug/a1d271b0e8cab34800e046be06414ab9
>
> Thanks,
>
> Joe
>
I should add that for some unknown reason, my host machine sometimes 
changes the host bus enumeration that has the USB 2.0 hub hanging off 
it, that has the pass-through devices attached to it. It varies from Bus 
03.Port 2 to Bus 01.Port 2. Usually it is Host Bus 03.Port2 but I've no 
idea why it changes from boot to boot, possibly something to do with 
udev.....or a buggy UEFI....

My initial report showed Bus 03.Port 2, the recent debug output shows 
Bus 01.Port 2.