From: Gerd Hoffmann <kraxel@redhat.com>
To: Joe Clifford <joe@thunderbug.co.uk>
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 08:44:23 +0200 [thread overview]
Message-ID: <1461221063.28204.28.camel@redhat.com> (raw)
In-Reply-To: <5717F0E5.2090907@thunderbug.co.uk>
On Mi, 2016-04-20 at 22:13 +0100, Joe Clifford wrote:
> Hi folks,
>
> I'm not a coder by any stretch of the imagination so I don't have a
> patch unfortunately however, this commit:
>
> https://github.com/qemu/qemu/commit/5f77e06baa84323e5bbc96c2c7f4fe627078b210
>
> causes the failure of the ICH9 Universal Host Controller - 2934 and the
> attached "Microsoft Common Controller For Windows Class"->"Xbox 360
> Wireless Receiver for Windows" which is a pass-through usb device
> attached to a Q35 Windows 7 x64 VM running on a Debian Jessie host.
>
> Reverting this commit on current master (as of today) fixes the problem.
>
> I spent some time today bisecting the git master code to find this.
>
> If you require any more information for debugging, please just let me know.
Hmm, quick attempt to reproduce locally failed (slightly different
device though, a microsoft nano receiver for a mouse). It's also not
obvious how that commit breaks usb devices.
Does the device show up in device manager?
If so: It probably has a yellow exclamation mark?
Any error description?
Can you send the "lsusb -v" output of the device?
cheers,
Gerd
next prev parent reply other threads:[~2016-04-21 6:44 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 [this message]
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
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=1461221063.28204.28.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=joe@thunderbug.co.uk \
--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).