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 839957 - usb-storage: SYNCHRONIZE_CACHE is broken
Summary: usb-storage: SYNCHRONIZE_CACHE is broken
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
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Gerd Hoffmann
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-13 09:49 UTC by Gerd Hoffmann
Modified: 2013-02-21 07:38 UTC (History)
9 users (show)

Fixed In Version: qemu-kvm-0.12.1.2-2.306.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-21 07:38:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
the fedora 17 guest kernel log. (33.01 KB, text/plain)
2012-07-16 08:55 UTC, Sibiao Luo 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0527 0 normal SHIPPED_LIVE qemu-kvm bug fix and enhancement update 2013-02-20 21:51:08 UTC

Description Gerd Hoffmann 2012-07-13 09:49:23 UTC 
Description of problem:
Fedora 17 guest produces a constant stream of "reset high-speed USB device number" when accessing usb-storage devices due to a bug in SYNCHRONIZE_CACHE handling.

Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.295.el6
Comment 1 Gerd Hoffmann 2012-07-13 10:42:54 UTC 
http://patchwork.ozlabs.org/patch/170838/
Comment 2 Sibiao Luo 2012-07-16 08:52:20 UTC 
Hi all,
   
   I reproduce this issue on the kernel-2.6.32-284.el6.x86_64 and qemu-kvm-0.12.1.2-2.295.el6.x86_64 host with the Fedora_17_x86_64 guest.

Version-Release number of selected component (if applicable):
host info:
# uname -r && rpm -q qemu-kvm
2.6.32-284.el6.x86_64
qemu-kvm-0.12.1.2-2.295.el6.x86_64
guest info:
Fedora_17_x86_64

Steps to Reproduce:
1.install fedora 17 guest on rhel 6.3 host.
2.create a usb-storage.
# qemu-img create -f qcow2 usb-storage.qcow2 20G
3.boot the guest adding a usb-storage device.
eg: # /usr/libexec/qemu-kvm -M rhel6.3.0 -cpu host -enable-kvm -m 2048 -smp 2 -usb -name sluo -uuid `uuidgen` -drive file=Fedora_17_x86_64.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,bus=pci.0,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,id=hostnet0,script=/etc/qemu-ifup -device virtio-net-pci,netdev=hostnet0,id=virtio-net-pci0,mac=08:2E:5F:0A:0D:B3 -spice disable-ticketing,port=5931 -vga qxl -global qxl-vga.vram_size=67108864 -device usb-ehci,id=ehci -drive file=/home/usb-storage.qcow2,if=none,id=storage0,media=disk,cache=none,format=qcow2 -device usb-storage,drive=storage0,id=usb-storage0,bus=ehci.0 -monitor stdio
4.write something to it (create filesystem for example).
# fdisk -l --> find the usb-storage disk in guest.
# mkfs.ext4 /dev/sda
5.check the guests kernel log.
# dmesg

Test results:
After the step 5, we can see a constant stream of "reset high-speed USB device number" in Fedora 17 guest's kernel log. I will attach the kernel log later.
# dmesg
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
...
[   57.556246] SELinux: initialized (dev fusectl, type fusectl), uses genfs_contexts
[   57.595447] SELinux: initialized (dev fuse, type fuse), uses genfs_contexts
[  554.995113] usb 1-1: reset high-speed USB device number 2 using ehci_hcd
[  555.241106] usb 1-1: reset high-speed USB device number 2 using ehci_hcd 

   BTW, I also tried the rhel6.3 guest, it do not have this issue.

Best wish.
sluo
Comment 3 Sibiao Luo 2012-07-16 08:55:11 UTC 
Created attachment 598397 [details]
the fedora 17 guest kernel log.
Comment 4 Gerd Hoffmann 2012-08-10 12:21:53 UTC 
patch posted.
Comment 7 Sibiao Luo 2012-10-09 09:09:19 UTC 
I Verify this issue on the kernel-2.6.32-315.el6.x86_64 and
qemu-kvm-0.12.1.2-2.320.el6.x86_64 host with the the same steps as comment #2.

Host info:
# uname -r && rpm -q qemu-kvm
2.6.32-315.el6.x86_64
qemu-kvm-0.12.1.2-2.320.el6.x86_64
Guest info:
Fedora_17_x86_64

Steps:
as same as comment #2

Test results:
After the step 5, 
we *cannot* see any stream of "reset high-speed USB device number" in Fedora 17 guest's kernel log, so this issue disappear.

Base on above and comment #2, this issue has been fixed correctly.
Comment 9 errata-xmlrpc 2013-02-21 07:38:07 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-2013-0527.html
Note You need to log in before you can comment on or make changes to this bug.