From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42118) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1at8Lr-00072R-6j for qemu-devel@nongnu.org; Thu, 21 Apr 2016 02:44:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1at8Lo-0006cx-0R for qemu-devel@nongnu.org; Thu, 21 Apr 2016 02:44:35 -0400 Received: from mx1.redhat.com ([209.132.183.28]:44648) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1at8Ln-0006br-RU for qemu-devel@nongnu.org; Thu, 21 Apr 2016 02:44:31 -0400 Message-ID: <1461221063.28204.28.camel@redhat.com> From: Gerd Hoffmann Date: Thu, 21 Apr 2016 08:44:23 +0200 In-Reply-To: <5717F0E5.2090907@thunderbug.co.uk> References: <5717F0E5.2090907@thunderbug.co.uk> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 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: Joe Clifford Cc: qemu-devel@nongnu.org On Mi, 2016-04-20 at 22:13 +0100, Joe Clifford wrote: > Hi folks, >=20 > I'm not a coder by any stretch of the imagination so I don't have a=20 > patch unfortunately however, this commit: >=20 > https://github.com/qemu/qemu/commit/5f77e06baa84323e5bbc96c2c7f4fe627078b= 210 >=20 > causes the failure of the ICH9 Universal Host Controller - 2934 and the= =20 > attached "Microsoft Common Controller For Windows Class"->"Xbox 360=20 > Wireless Receiver for Windows" which is a pass-through usb device=20 > attached to a Q35 Windows 7 x64 VM running on a Debian Jessie host. >=20 > Reverting this commit on current master (as of today) fixes the problem. >=20 > I spent some time today bisecting the git master code to find this. >=20 > If you require any more information for debugging, please just let me kno= w. 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