Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 258318 - Failure to mount usb-storage device (gentoo-sources-2.6.28-r1)
Summary: Failure to mount usb-storage device (gentoo-sources-2.6.28-r1)
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers
URL:
Whiteboard: linux-2.6.28
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-09 11:53 UTC by Ted Baker
Modified: 2009-02-12 21:13 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
dmesg log (dmesg.log,3.99 KB, text/plain)
2009-02-09 11:55 UTC, Ted Baker
Details
Output of lsusb (lsusb.log,479 bytes, text/plain)
2009-02-09 20:31 UTC, Ted Baker
Details
output of udevinfo (udevinfo.log,4.42 KB, text/plain)
2009-02-09 20:32 UTC, Ted Baker
Details
/proc//bus/usb/devices (usb-devices,6.79 KB, text/plain)
2009-02-09 20:33 UTC, Ted Baker
Details
Output of lsusb -v (lsusb.log,65.41 KB, text/plain)
2009-02-10 08:18 UTC, Ted Baker
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ted Baker 2009-02-09 11:53:19 UTC
This is clearly related to bugs 250789 and 253034. I was hoping 2.6.28-r1 was going to fix it but sadly not :(

Reproducible: Always

Steps to Reproduce:
1.make clean && make && make modules_install && make install
2.Reboot to 2.6.28-r1
3.Turn on USB external drive

Actual Results:  
External device not recognized looping error message in dmesg

Expected Results:  
Create device /dev/sd??
Comment 1 Ted Baker 2009-02-09 11:55:21 UTC
Created attachment 181428 [details]
dmesg log

I've edited out most of the error messages loop to save space
Comment 2 LiorD 2009-02-09 15:13:08 UTC
Bugs 250789 and 253034 are probably related but each one is on different device.
If you have the same problem then your problematic device must be added to the list.
You should attach the output of lsusb so the proper IDs could be added to the kernel.
Comment 3 Ted Baker 2009-02-09 20:31:18 UTC
Created attachment 181477 [details]
Output of lsusb
Comment 4 Ted Baker 2009-02-09 20:32:20 UTC
Created attachment 181478 [details]
output of udevinfo
Comment 5 Ted Baker 2009-02-09 20:33:12 UTC
Created attachment 181479 [details]
/proc//bus/usb/devices
Comment 6 George Kadianakis (RETIRED) gentoo-dev 2009-02-09 20:34:30 UTC
(In reply to comment #3)
> Created an attachment (id=181477) [edit]
> Output of lsusb
> 

The output of: lsusb -v
would be a bit more helpful ;)
Comment 7 Ted Baker 2009-02-10 08:18:00 UTC
Created attachment 181519 [details]
Output of lsusb -v
Comment 8 Ted Baker 2009-02-10 08:20:00 UTC
(In reply to comment #6)
> The output of: lsusb -v
> would be a bit more helpful ;)
 
Guess you can tell I'm not a kernel hacker. Just did as I was told ... ;)
Comment 9 LiorD 2009-02-10 09:12:45 UTC
It seems that a device with the same vendor and product ID was added to vanilla kernel 2.6.28.3.
If you can try the latest vanilla kernel and see if it solves your problem.
Comment 10 Ted Baker 2009-02-11 12:45:08 UTC
(In reply to comment #9)
> It seems that a device with the same vendor and product ID was added to vanilla
> kernel 2.6.28.3.

Works fine with this kernel.

Bug can be closed.

Thanks for everyone's help