Bug 755846

Summary: initializing failed usb 1.0 device on ehci controller occupies a port
Product: Red Hat Enterprise Linux 6 Reporter: Shaolong Hu <shu>
Component: qemu-kvmAssignee: Gerd Hoffmann <kraxel>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2CC: acathrow, bsarathy, juzhang, knoel, michen, mkenneth, qzhou, tburke, virt-maint
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-17 09:32:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Shaolong Hu 2011-11-22 08:09:24 UTC 
Description of problem:
------------------------
Assign a usb 1.0 device to ehci controller, it fails to initialize, but occupies a port.

Version-Release number of selected component (if applicable):
---------------------------------------------------------------
qemu-kvm-0.12.1.2-2.209.el6.x86_64

How reproducible:
------------------
100%

Steps to Reproduce:
--------------------
1.boot guest with echi controller
2.assign usb-hub to ehci controller

(qemu) device_add usb-hub,id=hub1
Warning: speed mismatch trying to attach usb device QEMU USB Hub to bus ehci.0
Device 'usb-hub' could not be initialized
(qemu) info usb
  Device 0.0, Port 1, Speed 1.5 Mb/s, Product      <-- add this

  
Actual results:
-----------------
if we add 6 usb-hub with different port, the ehci controller has no port left, the 7th usb-hub causes core dump.

Expected results:
-----------------
Assign a usb 1.0 device to ehci controller, it fails to initialize, it should not occupy any port.
Comment 1 Gerd Hoffmann 2011-11-28 08:30:27 UTC 
http://patchwork.ozlabs.org/patch/127362/
http://patchwork.ozlabs.org/patch/127358/
Comment 2 Gerd Hoffmann 2012-02-17 09:32:59 UTC 

*** This bug has been marked as a duplicate of bug 754349 ***