Bug 179191
Summary: | USB Flash disk not assigned a device name | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Scott Purcell <scott_purcell> | ||||
Component: | kernel | Assignee: | Pete Zaitcev <zaitcev> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 4.0 | CC: | jbaron | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | 2.6.9-34.EL | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2006-09-12 00:14:49 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Scott Purcell
2006-01-27 23:09:46 UTC
Created attachment 123811 [details]
lsusb output using -vv and -s parameters on the affected device
This is my output from
lsusb -vv -s 001:004
/var/log/messages output when the device (having been inserted before boot) was removed and then reinserted: Jan 27 17:06:32 localhost kernel: usb 1-6: USB disconnect, address 4 Jan 27 17:07:11 localhost kernel: usb 1-6: new high speed USB device using address 5 Jan 27 17:07:11 localhost kernel: scsi1 : SCSI emulation for USB Mass Storage devices Jan 27 17:07:26 localhost hal.hotplug[4430]: timout(10000 ms) waiting for /devices/pci0000:00/0000:00:1d.7/usb1/1-6/1-6:1.0 If I install and boot to the 2.6.9-5.EL kernel from RHEL4 Gold, the device works as expected. I should note that I have seen the same behaviour with other Kingston Data Travelers. I suspect it is a problem with the identification of the vendor ID or the device ID. Updating priority and severity because I'm uncomfortable being forced to run an out-of-date kernel just to have functionality with my USB device and because I can't see that this bug report has even been noticed in the past week. If it needs to be downgraded again, I'm fine with that -- I'm just looking for some confirmation that it has been seen. Does the U3 work? Please verify that it fixes the problem and close the bug. I have fixed regressions with 08ec/0012 devices, by bug 161613 and bug 160308. Yes, the 2.6.9-34.EL kernel does resolve the problem. Thank you! I've attempted to mark the bug as resolved by the current kernel version, but apparently I do not have the appropriate Bugzilla privileges to do that. It can be closed as far as I am concerned, but I'm unable to do it myself. |