qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Joe Clifford <joe@thunderbug.co.uk>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Bug (Regression?) in hw/usb/hcd-uhci.c causes failure of ICH9 host controller and attached Xbox 360 Wireless Receiver
Date: Thu, 21 Apr 2016 16:41:46 +0100	[thread overview]
Message-ID: <5718F4BA.9020203@thunderbug.co.uk> (raw)
In-Reply-To: <1461248234.28204.31.camel@redhat.com>

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

  reply	other threads:[~2016-04-21 15:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20 21:13 [Qemu-devel] Bug (Regression?) in hw/usb/hcd-uhci.c causes failure of ICH9 host controller and attached Xbox 360 Wireless Receiver Joe Clifford
2016-04-21  6:44 ` Gerd Hoffmann
2016-04-21 11:55   ` Joe Clifford
2016-04-21 14:17     ` Gerd Hoffmann
2016-04-21 15:41       ` Joe Clifford [this message]
2016-04-21 15:51         ` Joe Clifford
2016-04-22 10:05           ` Gerd Hoffmann
2016-04-22 10:04         ` Gerd Hoffmann
2016-04-22 10:32           ` joe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5718F4BA.9020203@thunderbug.co.uk \
    --to=joe@thunderbug.co.uk \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).