RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 769760 - Formatting of usb-storage disk attached on usb-hub fails to end
Summary: Formatting of usb-storage disk attached on usb-hub fails to end
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Gerd Hoffmann
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-22 05:03 UTC by Shaolong Hu
Modified: 2013-01-10 00:38 UTC (History)
14 users (show)

Fixed In Version: qemu-kvm-0.12.1.2-2.268.el6
Doc Type: Bug Fix
Doc Text:
Cause: USB controller didn't wait to finish last transaction before trying to reset. Consequence: If there was any USB operation in progress when doing USB reset, the USB hub never finished it's operation. Fix: Child process detach has been fixed. Result: Formatting usb-storage disk and any other operations finish successfully even when running reset as reset waits till the operation ends.
Clone Of:
Environment:
Last Closed: 2012-06-20 11:38:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0746 0 normal SHIPPED_LIVE qemu-kvm bug fix and enhancement update 2012-06-19 19:31:48 UTC

Description Shaolong Hu 2011-12-22 05:03:27 UTC 
Description of problem:
------------------------
Assigning lots of usb devices to guest, usb-hub will be added automatically, format a usb-storage disk on usb-hub, it fails to end.

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

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

Steps to Reproduce:
--------------------
1.boot guest with "-readconfig ich9-ehci-uhci.cfg"

2.hotplug several usb-storage disks, make partition and format the each disk after plug, they all works fine, when hotplug the fifth usb-storage disk, usb-hub is added, and the fifth usb-storage is attached on the hub:

(qemu) info usb
  Device 0.2, Port 1, Speed 12 Mb/s, Product QEMU USB Tablet
  Device 0.3, Port 2, Speed 480 Mb/s, Product QEMU USB MSD
  Device 0.4, Port 3, Speed 480 Mb/s, Product QEMU USB MSD
  Device 0.5, Port 4, Speed 480 Mb/s, Product QEMU USB MSD
  Device 0.6, Port 5, Speed 480 Mb/s, Product QEMU USB MSD
  Device 0.2, Port 6, Speed 12 Mb/s, Product QEMU USB Hub
  Device 0.3, Port 6.1, Speed 12 Mb/s, Product QEMU USB MSD

dmesg in guest:
csi6 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
scsi 6:0:0:0: Direct-Access     QEMU     QEMU HARDDISK    0.12 PQ: 0 ANSI: 5
sd 6:0:0:0: Attached scsi generic sg5 type 0
sd 6:0:0:0: [sdf] 2097152 512-byte logical blocks: (1.07 GB/1.00 GiB)
sd 6:0:0:0: [sdf] Write Protect is off
sd 6:0:0:0: [sdf] Mode Sense: 1f 00 00 08
sd 6:0:0:0: [sdf] Assuming drive cache: write through
sd 6:0:0:0: [sdf] Assuming drive cache: write through
 sdf: unknown partition table
sd 6:0:0:0: [sdf] Assuming drive cache: write through
sd 6:0:0:0: [sdf] Attached SCSI disk

3.in guest, make partition of the fifth usb-storage disk(/dev/sdf), then format /dev/sdf1, the formatting hangs, no extra dmesg in guest at this point:

#fdisk /dev/sdf
#mkfs.ext4 /dev/sdf1
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
65536 inodes, 262094 blocks
13104 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=268435456
8 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376

Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information:     <---hangs here

4.kill format process, no dmesg in guest, then delete the disk in qemu monitor, in the guest, a lot of dmesg shows:

hub 4-2:1.0: cannot reset port 1 (err = -71)
hub 4-2:1.0: cannot reset port 1 (err = -71)
hub 4-2:1.0: cannot reset port 1 (err = -71)
hub 4-2:1.0: cannot reset port 1 (err = -71)
hub 4-2:1.0: cannot reset port 1 (err = -71)
hub 4-2:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
hub 4-2:1.0: cannot disable port 1 (err = -71)
hub 4-2:1.0: cannot reset port 1 (err = -71)
hub 4-2:1.0: cannot reset port 1 (err = -71)
hub 4-2:1.0: cannot reset port 1 (err = -71)
hub 4-2:1.0: cannot reset port 1 (err = -71)
hub 4-2:1.0: cannot reset port 1 (err = -71)
hub 4-2:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
hub 4-2:1.0: cannot disable port 1 (err = -71)
hub 4-2:1.0: cannot reset port 1 (err = -71)
hub 4-2:1.0: cannot reset port 1 (err = -71)
hub 4-2:1.0: cannot reset port 1 (err = -71)
hub 4-2:1.0: cannot reset port 1 (err = -71)
hub 4-2:1.0: cannot reset port 1 (err = -71)
hub 4-2:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
hub 4-2:1.0: cannot disable port 1 (err = -71)
hub 4-2:1.0: cannot reset port 1 (err = -71)
hub 4-2:1.0: cannot reset port 1 (err = -71)
hub 4-2:1.0: cannot reset port 1 (err = -71)
hub 4-2:1.0: cannot reset port 1 (err = -71)
hub 4-2:1.0: cannot reset port 1 (err = -71)
hub 4-2:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
hub 4-2:1.0: cannot disable port 1 (err = -71)
hub 4-2:1.0: cannot disable port 1 (err = -71)
hub 4-2:1.0: hub_port_status failed (err = -71)
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 4d dd 00 00 80 00
end_request: I/O error, dev sdf, sector 544221
Buffer I/O error on device sdf1, logical block 544160
lost page write due to I/O error on sdf1
Buffer I/O error on device sdf1, logical block 544161
lost page write due to I/O error on sdf1
Buffer I/O error on device sdf1, logical block 544162
lost page write due to I/O error on sdf1
Buffer I/O error on device sdf1, logical block 544163
lost page write due to I/O error on sdf1
Buffer I/O error on device sdf1, logical block 544164
lost page write due to I/O error on sdf1
Buffer I/O error on device sdf1, logical block 544165
lost page write due to I/O error on sdf1
Buffer I/O error on device sdf1, logical block 544166
lost page write due to I/O error on sdf1
Buffer I/O error on device sdf1, logical block 544167
lost page write due to I/O error on sdf1
Buffer I/O error on device sdf1, logical block 544168
lost page write due to I/O error on sdf1
Buffer I/O error on device sdf1, logical block 544169
lost page write due to I/O error on sdf1
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 4e 5d 00 00 80 00
end_request: I/O error, dev sdf, sector 544349
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 4e dd 00 00 80 00
end_request: I/O error, dev sdf, sector 544477
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 4f 5d 00 00 80 00
end_request: I/O error, dev sdf, sector 544605
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 48 55 00 00 80 00
end_request: I/O error, dev sdf, sector 542805
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 48 d5 00 00 08 00
end_request: I/O error, dev sdf, sector 542933
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 58 65 00 00 80 00
end_request: I/O error, dev sdf, sector 546917
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 58 e5 00 00 80 00
end_request: I/O error, dev sdf, sector 547045
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 59 65 00 00 80 00
end_request: I/O error, dev sdf, sector 547173
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 59 e5 00 00 80 00
end_request: I/O error, dev sdf, sector 547301
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 5a 65 00 00 80 00
end_request: I/O error, dev sdf, sector 547429
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 5a e5 00 00 80 00
end_request: I/O error, dev sdf, sector 547557
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 5b 65 00 00 80 00
end_request: I/O error, dev sdf, sector 547685
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 5b e5 00 00 80 00
end_request: I/O error, dev sdf, sector 547813
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 5c 65 00 00 80 00
end_request: I/O error, dev sdf, sector 547941
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 5c e5 00 00 80 00
end_request: I/O error, dev sdf, sector 548069
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 5d 65 00 00 80 00
end_request: I/O error, dev sdf, sector 548197
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 5d e5 00 00 80 00
end_request: I/O error, dev sdf, sector 548325
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 5e 65 00 00 80 00
end_request: I/O error, dev sdf, sector 548453
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 5e e5 00 00 80 00
end_request: I/O error, dev sdf, sector 548581
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 4f dd 00 00 80 00
end_request: I/O error, dev sdf, sector 544733
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 50 5d 00 00 80 00
end_request: I/O error, dev sdf, sector 544861
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 50 dd 00 00 80 00
end_request: I/O error, dev sdf, sector 544989
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 5f 65 00 00 80 00
end_request: I/O error, dev sdf, sector 548709
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 5f e5 00 00 80 00
end_request: I/O error, dev sdf, sector 548837
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 60 65 00 00 80 00
end_request: I/O error, dev sdf, sector 548965
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 60 e5 00 00 80 00
end_request: I/O error, dev sdf, sector 549093
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 61 65 00 00 80 00
end_request: I/O error, dev sdf, sector 549221
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 61 e5 00 00 80 00
end_request: I/O error, dev sdf, sector 549349
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 51 5d 00 00 80 00
end_request: I/O error, dev sdf, sector 545117
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 51 dd 00 00 80 00
end_request: I/O error, dev sdf, sector 545245
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 52 5d 00 00 80 00
end_request: I/O error, dev sdf, sector 545373
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 52 dd 00 00 80 00
end_request: I/O error, dev sdf, sector 545501
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 62 65 00 00 80 00
end_request: I/O error, dev sdf, sector 549477
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 62 e5 00 00 80 00
end_request: I/O error, dev sdf, sector 549605
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 63 65 00 00 80 00
end_request: I/O error, dev sdf, sector 549733
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 63 e5 00 00 80 00
end_request: I/O error, dev sdf, sector 549861
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 64 65 00 00 80 00
end_request: I/O error, dev sdf, sector 549989
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 64 e5 00 00 80 00
end_request: I/O error, dev sdf, sector 550117
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 53 5d 00 00 80 00
end_request: I/O error, dev sdf, sector 545629
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 53 dd 00 00 80 00
end_request: I/O error, dev sdf, sector 545757
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 54 5d 00 00 80 00
end_request: I/O error, dev sdf, sector 545885
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 65 65 00 00 80 00
end_request: I/O error, dev sdf, sector 550245
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 65 e5 00 00 80 00
end_request: I/O error, dev sdf, sector 550373
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 66 65 00 00 80 00
end_request: I/O error, dev sdf, sector 550501
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 66 e5 00 00 80 00
end_request: I/O error, dev sdf, sector 550629
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 67 65 00 00 80 00
end_request: I/O error, dev sdf, sector 550757
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 67 e5 00 00 08 00
end_request: I/O error, dev sdf, sector 550885
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 54 dd 00 00 80 00
end_request: I/O error, dev sdf, sector 546013
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 55 5d 00 00 80 00
end_request: I/O error, dev sdf, sector 546141
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 55 dd 00 00 80 00
end_request: I/O error, dev sdf, sector 546269
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 77 75 00 00 80 00
end_request: I/O error, dev sdf, sector 554869
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 77 f5 00 00 80 00
end_request: I/O error, dev sdf, sector 554997
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 78 75 00 00 80 00
end_request: I/O error, dev sdf, sector 555125
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 78 f5 00 00 80 00
end_request: I/O error, dev sdf, sector 555253
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 79 75 00 00 80 00
end_request: I/O error, dev sdf, sector 555381
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 79 f5 00 00 80 00
end_request: I/O error, dev sdf, sector 555509
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 56 5d 00 00 80 00
end_request: I/O error, dev sdf, sector 546397
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 56 dd 00 00 80 00
end_request: I/O error, dev sdf, sector 546525
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 57 5d 00 00 80 00
end_request: I/O error, dev sdf, sector 546653
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 7a 75 00 00 80 00
end_request: I/O error, dev sdf, sector 555637
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 7a f5 00 00 80 00
end_request: I/O error, dev sdf, sector 555765
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 7b 75 00 00 80 00
end_request: I/O error, dev sdf, sector 555893
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 7b f5 00 00 80 00
end_request: I/O error, dev sdf, sector 556021
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 7c 75 00 00 80 00
end_request: I/O error, dev sdf, sector 556149
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 7c f5 00 00 80 00
end_request: I/O error, dev sdf, sector 556277
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 57 dd 00 00 80 00
end_request: I/O error, dev sdf, sector 546781
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 58 5d 00 00 08 00
end_request: I/O error, dev sdf, sector 546909
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 67 ed 00 00 80 00
end_request: I/O error, dev sdf, sector 550893
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 7d 75 00 00 80 00
end_request: I/O error, dev sdf, sector 556405
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 7d f5 00 00 80 00
end_request: I/O error, dev sdf, sector 556533
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 7e 75 00 00 80 00
end_request: I/O error, dev sdf, sector 556661
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 7e f5 00 00 80 00
end_request: I/O error, dev sdf, sector 556789
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 7f 75 00 00 80 00
end_request: I/O error, dev sdf, sector 556917
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 7f f5 00 00 48 00
end_request: I/O error, dev sdf, sector 557045
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 68 6d 00 00 80 00
end_request: I/O error, dev sdf, sector 551021
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 68 ed 00 00 80 00
end_request: I/O error, dev sdf, sector 551149
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 69 6d 00 00 80 00
end_request: I/O error, dev sdf, sector 551277
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 0c 00 3d 00 00 02 00
end_request: I/O error, dev sdf, sector 786493
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 0c 00 45 00 00 08 00
end_request: I/O error, dev sdf, sector 786501
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 14 00 3d 00 00 02 00
end_request: I/O error, dev sdf, sector 1310781
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 14 00 45 00 00 08 00
end_request: I/O error, dev sdf, sector 1310789
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 1c 00 3d 00 00 02 00
end_request: I/O error, dev sdf, sector 1835069
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 1c 00 45 00 00 08 00
end_request: I/O error, dev sdf, sector 1835077
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 69 ed 00 00 80 00
end_request: I/O error, dev sdf, sector 551405
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 6a 6d 00 00 80 00
end_request: I/O error, dev sdf, sector 551533
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 08 6a ed 00 00 80 00
end_request: I/O error, dev sdf, sector 551661
sd 6:0:0:0: [sdf] Unhandled error code
sd 6:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
sd 6:0:0:0: [sdf] CDB: Write(10): 2a 00 00 1f fd bd 00 00 80 00
end_request: I/O error, dev sdf, sector 2096573

5. can not hotplug usb-storage device correctly any more
Comment 1 Gerd Hoffmann 2012-01-05 10:23:19 UTC 
Sure mkfs hangs forever?  Note that the hub is a 1.1 hub, so the stick connected this way doesn't run at full speed, so the mkfs will take noticable longer than with the other sticks which are hooked up to 2.0 usb ports.  Expect a few minutes minimum (depending on the stick size).

The guest kernel throwing disk errors is normal too, that happens because it has pending I/O requests to the device just removed.

The usb hub errors ...

hub 4-2:1.0: cannot reset port 1 (err = -71)
hub 4-2:1.0: Cannot enable port 1.  Maybe the USB cable is bad?

... should not happen though.

Can you try whenever this scratch build fixes it for you?

http://brewweb.devel.redhat.com/brew/taskinfo?taskID=3920756
Comment 2 Shaolong Hu 2012-01-09 10:00:51 UTC 
(In reply to comment #1)
> Sure mkfs hangs forever?  Note that the hub is a 1.1 hub, so the stick
> connected this way doesn't run at full speed, so the mkfs will take noticable
> longer than with the other sticks which are hooked up to 2.0 usb ports.  Expect
> a few minutes minimum (depending on the stick size).

Yes, i confirm that mkfs does finish, however the time is too long, it takes about 9 minutes for a 1G usb stick, with ehci bus it only takes about 2 seconds. 

> 
> The guest kernel throwing disk errors is normal too, that happens because it
> has pending I/O requests to the device just removed.
> 
> The usb hub errors ...
> 
> hub 4-2:1.0: cannot reset port 1 (err = -71)
> hub 4-2:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
> 
> ... should not happen though.
> 
> Can you try whenever this scratch build fixes it for you?
> 
> http://brewweb.devel.redhat.com/brew/taskinfo?taskID=3920756

This build eliminates the hub error in dmesg, and after delete usb stick in qemu monitor, mkfs finish immediately:

# mkfs.ext4 /dev/sda1
-------------------------------
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
65536 inodes, 262094 blocks
13104 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=268435456
8 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376

Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 31 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.


at this point, dmesg in the guest:
--------------------------------------
usb 1-2.1: USB disconnect, address 4
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 00 00 05 c5 00 00 80 00
end_request: I/O error, dev sda, sector 1477
Buffer I/O error on device sda1, logical block 1416
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 1417
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 1418
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 1419
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 1420
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 1421
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 1422
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 1423
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 1424
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 1425
lost page write due to I/O error on sda1
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
sd 2:0:0:0: [sda] CDB: Write(10): 2a 00 00 00 06 45 00 00 80 00
end_request: I/O error, dev sda, sector 1605
Comment 3 Gerd Hoffmann 2012-01-10 11:20:42 UTC 
Yea, 9 minutes are ok for such a big usb stick via usb 1.1.
There is a reason why we have usb 2.0 after all ;)

Good to hear that the usb hub issue is fixed, patch sent.
Comment 6 Shaolong Hu 2012-02-01 07:42:51 UTC 
Verify on qemu-kvm-0.12.1.2-2.222.el6:

After delete usb stick in qemu monitor, mkfs finish immediately, just the dmesg differs from previous scratch build, is this ok?

------------------------------------------------------------------
end_request: I/O error, dev sde, sector 17861
usb 5-2: reset full speed USB device using uhci_hcd and address 2
usb 5-2: device descriptor read/64, error -71
usb 5-2: device descriptor read/64, error -71
usb 5-2: reset full speed USB device using uhci_hcd and address 2
usb 5-2: device descriptor read/64, error -71
usb 5-2: device descriptor read/64, error -71
usb 5-2: reset full speed USB device using uhci_hcd and address 2
usb 5-2: device not accepting address 2, error -71
usb 5-2: reset full speed USB device using uhci_hcd and address 2
usb 5-2: device not accepting address 2, error -71
hub 5-2:1.0: hub_port_status failed (err = -19)
hub 5-2:1.0: hub_port_status failed (err = -19)
hub 5-2:1.0: hub_port_status failed (err = -19)
hub 5-2:1.0: hub_port_status failed (err = -19)
hub 5-2:1.0: hub_port_status failed (err = -19)
hub 5-2:1.0: hub_port_status failed (err = -19)
hub 5-2:1.0: hub_port_status failed (err = -19)
hub 5-2:1.0: hub_port_status failed (err = -19)
hub 5-2:1.0: activate --> -19
usb 5-2: USB disconnect, address 2
usb 5-2: new full speed USB device using uhci_hcd and address 4
usb 5-2: device descriptor read/64, error -71
usb 5-2: device descriptor read/64, error -71
usb 5-2: new full speed USB device using uhci_hcd and address 5
usb 5-2: device descriptor read/64, error -71
usb 5-2: device descriptor read/64, error -71
usb 5-2: new full speed USB device using uhci_hcd and address 6
usb 5-2: device not accepting address 6, error -71
usb 5-2: new full speed USB device using uhci_hcd and address 7
usb 5-2: device not accepting address 7, error -71
hub 5-0:1.0: unable to enumerate USB device on port 2
Comment 7 Gerd Hoffmann 2012-02-06 08:15:14 UTC 
Hmm, "hub_port_status failed" is back, not good.
Comment 8 Gerd Hoffmann 2012-03-26 12:46:41 UTC 
http://patchwork.ozlabs.org/patch/148734/
Comment 9 Gerd Hoffmann 2012-03-27 10:31:41 UTC 
patch posted.
Comment 14 langfang 2012-04-18 09:12:28 UTC 
Reproduced this issue with steps and  environment as follows:
version:
# uname -r
2.6.32-262.el6.x86_64
#uname -r |grep qemu-kvm
qemu-kvm-0.12.1.2-2.267.el6.x86_64

steps:

1.boot guest with "-readconfig ich9-ehci-uhci.cfg"

2.hotplug several usb device, 
(qemu) info usb
  Device 0.2, Port 1, Speed 12 Mb/s, Product QEMU USB Tablet
  Device 1.2, Port 1, Speed 480 Mb/s, Product DT 101 G2
  Device 1.0, Port 2, Speed 1.5 Mb/s, Product USB Host Device
  Device 1.0, Port 3, Speed 1.5 Mb/s, Product USB Host Device
  Device 1.0, Port 4, Speed 1.5 Mb/s, Product USB Host Device
  Device 1.0, Port 5, Speed 1.5 Mb/s, Product USB Host Device
3.in guest, make partition of the second usb-storage disk(/dev/sda), then format
/dev/sda, the formatting hangs

#fdisk /dev/sda
#mkfs.ext4 /dev/sdfa1

results:
.....
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information   ---->hang

verify this issue with steps(as same as reproduce) and  environment as follows:

version:

# uname -r
2.6.32-262.el6.x86_64
#uname -r |grep qemu-kvm
qemu-kvm-0.12.1.2-2.277.el6.x86_64

steps as same as reproduce.


my CLI:
/usr/libexec/qemu-kvm -m 2G -smp 2 -cpu Penryn,+x2apic, -usbdevice tablet -drive file=/home/rhel6.3-64.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,werror=stop,rerror=stop,cache=none -device virtio-blk-pci,drive=drive-virtio-disk0,id=ide0-0-0,bootindex=1 -uuid bc898f4c-93e8-48d7-b1f6-05eb4c611129 -rtc base=utc,clock=host,driftfix=slew -no-kvm-pit-reinjection -monitor stdio -name rhel5.7 -spice port=5830,disable-ticketing -vga qxl -netdev tap,sndbuf=0,id=hostnet0,vhost=on,script=/etc/qemu-ifup,downscript=no -device virtio-net-pci,netdev=hostnet0,id=virtio-net-pci0,bootindex=2 -usb -device usb-host,hostbus=1,hostaddr=12,id=hostdev1 -readconfig ich9-ehci-uhci.cfg

results:
root@chardev ~]# mkfs.ext4 /dev/sda2
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
440640 inodes, 1762048 blocks
88102 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=1807745024
54 block groups
32768 blocks per group, 32768 fragments per group
8160 inodes per group
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632

Writing inode tables: done                            
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 33 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.

according to above results ,this issue has been fixed.
Comment 16 Michal Novotny 2012-05-04 09:43:11 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause:
USB controller didn't wait to finish last transaction before trying to reset.

Consequence:
If there was any USB operation in progress when doing USB reset, the USB hub never finished it's operation.

Fix:
Child process detach has been fixed.

Result:
Formatting usb-storage disk and any other operations finish successfully even when running reset as reset waits till the operation ends.
Comment 17 errata-xmlrpc 2012-06-20 11:38:11 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0746.html
Note You need to log in before you can comment on or make changes to this bug.