[Bug 88746] Re: ehci_hcd module causes I/O errors in USB 2.0 devices
Troy James Sobotka
troy.sobotka at gmail.com
Wed Dec 10 06:40:11 UTC 2008
@Andy Rabagliati: Absolutely. I have had that bug / regression before.
It most certainly is a mounting problem. It _may_ indeed be related to
whatever underlying chipset Alcor is using as I suspect the Alcor is
ultimately just junk. What would be interesting is to somehow get a
feeling for what underlying hardware is being used at the chipset level
in these devices.
I'd suggest you track down the appropriate bug report and report if
necessary. It might be wise to reference this bug report as I find it
suspect that your card reader also happens to be an Alcor.
I did a further test with the digital SLR camera itself and it mounts
fine and transfers files 100% properly and speedily with _no_ problems.
This gives further credibility to the notion that the crashing of
ehci_hcd is directly related to particular hardware of the actual
devices -- not the host bus controller / combination.
I'd certainly be willing to flag Alcor as a hideous vendor (included in
nGear, NMedia, and other models.) If David Becker's bug is related as
it appears to be (https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/88746/comments/409) it would seem that we could add
Kingston to that list at least in one instance.
What we somehow need to do is:
1) Identify exactly what underlying hardware is the source of the problem in the devices.
2) Provide a way for people who are stuck with onboard card readers of the hardware to have the 'echo "128" >' command automatically done every boot for them.
3) Figure out who we need to contact regarding the bug. Greg Kroah-Hartman suggests at the end of http://bugzilla.kernel.org/show_bug.cgi?id=ehci_hcd to file it to the linux-usb list. I'm not entirely sure that it belongs there though?
Good detective work folks. I think we need someone to help us figure
out the lower level stuffs on the devices somewhere? Perhaps the only
way is through documentation? Is there a way to read more deeply into
the device's ancestry?
--
ehci_hcd module causes I/O errors in USB 2.0 devices
https://bugs.launchpad.net/bugs/88746
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
More information about the kernel-bugs
mailing list