Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 388558[details]
Guest kernel logs
Description of problem:
When I write to a virtual USB disk, Linux outputs lots of I/O errors and resets in the kernel log. In the end, the transferred data seems to be fine, though. This was tested with a RHEL 5.3 and a Fedora 11 guest. It happens both with UHCI and OHCI emulation.
Steps to Reproduce:
1. Start a guest with a small scratch image (-device usb-storage,drive=usb -drive id=usb,if=none,file=/tmp/scratch.img)
2. In the guest, write to the disk: dd if=/dev/urandom of=/dev/sda
3. If the messages don't appear on the console, use dmesg
Actual results:
The data is correctly transferred (you can verify by writing into a temporary file first and md5sum this file and the scratch image on the host), but lots of error messages appear.
Expected results:
No error messages should appear.
Additional info:
Attaching the kernel logs of the guest.
Comment 2RHEL Program Management
2010-02-03 16:37:21 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
inclusion.
Kevin, Thanks for the info. It is strange in that you reported it and someone else elevated it as a test blocker. I moved the target to RC, but left as a blocker. Putting it in needinfo to get justification.
caiqian, when asserting blocker, please add a comment with some justification.
Is this a really a blocker? If not please drop the flag.
There used to be a few issues ...
upstream/master should be fine now in case anyone cares to try.
RHEL-6.2 needs tons of USB backports for EHCI anyway,
I'll go fix this along the way.
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/RHSA-2011-1531.html
Created attachment 388558 [details] Guest kernel logs Description of problem: When I write to a virtual USB disk, Linux outputs lots of I/O errors and resets in the kernel log. In the end, the transferred data seems to be fine, though. This was tested with a RHEL 5.3 and a Fedora 11 guest. It happens both with UHCI and OHCI emulation. Steps to Reproduce: 1. Start a guest with a small scratch image (-device usb-storage,drive=usb -drive id=usb,if=none,file=/tmp/scratch.img) 2. In the guest, write to the disk: dd if=/dev/urandom of=/dev/sda 3. If the messages don't appear on the console, use dmesg Actual results: The data is correctly transferred (you can verify by writing into a temporary file first and md5sum this file and the scratch image on the host), but lots of error messages appear. Expected results: No error messages should appear. Additional info: Attaching the kernel logs of the guest.