From: joe@thunderbug.co.uk
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org,
Qemu-devel <qemu-devel-bounces+joe=thunderbug.co.uk@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: Fri, 22 Apr 2016 11:32:06 +0100 [thread overview]
Message-ID: <112a7dea40cb0418cae47e4172f6913f@thunderbug.co.uk> (raw)
In-Reply-To: <1461319465.28204.85.camel@redhat.com>
On 2016-04-22 11:04, Gerd Hoffmann wrote:
> Hi,
>
>> 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.
>
> Think I've nailed it. Can you fetch the latest version of the git
> branch (fyi: it's rebased) and try again?
>
> thanks,
> Gerd
Yep, you nailed it!
I've applied
https://www.kraxel.org/cgit/qemu/commit/?h=work/usb-uhci-usb-host-debug&id=c69e5efac15db4340b880c80f27ebe536acd1aeb
to my local copy of current qemu git master and the problem no longer
exists.
The stderr debugging output is also beautifully silent :)
Awesome work, many thanks.
Joe
prev parent reply other threads:[~2016-04-22 10:32 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
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 [this message]
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=112a7dea40cb0418cae47e4172f6913f@thunderbug.co.uk \
--to=joe@thunderbug.co.uk \
--cc=kraxel@redhat.com \
--cc=qemu-devel-bounces+joe=thunderbug.co.uk@nongnu.org \
--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).