From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:52186) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1atGto-0001gr-4m for qemu-devel@nongnu.org; Thu, 21 Apr 2016 11:52:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1atGti-0003R1-Ea for qemu-devel@nongnu.org; Thu, 21 Apr 2016 11:52:12 -0400 Received: from hawk.thunderbug.co.uk ([149.202.60.219]:46490) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1atGti-0003Qw-8I for qemu-devel@nongnu.org; Thu, 21 Apr 2016 11:52:06 -0400 References: <5717F0E5.2090907@thunderbug.co.uk> <1461221063.28204.28.camel@redhat.com> <5718BFA2.4050101@thunderbug.co.uk> <1461248234.28204.31.camel@redhat.com> <5718F4BA.9020203@thunderbug.co.uk> From: Joe Clifford Message-ID: <5718F71F.9090507@thunderbug.co.uk> Date: Thu, 21 Apr 2016 16:51:59 +0100 MIME-Version: 1.0 In-Reply-To: <5718F4BA.9020203@thunderbug.co.uk> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Bug (Regression?) in hw/usb/hcd-uhci.c causes failure of ICH9 host controller and attached Xbox 360 Wireless Receiver List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: qemu-devel@nongnu.org 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.