Most recent kernel where this bug did not occur: 2.6.17-rc3
Hardware Environment: amd64 && a8n-premium
Probably copy of Bug: 5835|6201
Steps to reproduce:
Boot the system with a kernel wich has ehci_hcd enabled and plug the device in
any usb port.
Created attachment 8019 [details]
syslog, messages information
lsusb will not work as soon the device is attached.
So this worked in 2.6.17-rc3, yet it does not work now?
When did this last work?
And what are the kernel log messages you get when you plug the device in?
Ok, usb-storage issue, that's matt's area...
Interesting.... basic communication works for a little while, then the device
Can you turn off HALD and UDEVD and re-test?
Created attachment 8024 [details]
syslog - no udev [and no hal]
Most recent kernel where this bug did not occur: --
Please excuse for skimming over this:( UMS && ehci_hcd never worked on this
system in combination with linux:( The device works fine at other computers
(eg. my old pc && pre udev kernel [< 2.6.13 afaik]) and on this pc using the
I am not sure about your request concerning HALD, i think that i do not have
the hal or hal-device-manager package installed. And i was not able to find any
hald executable anywhere. In case it should still be turned on please tell me
how to deactivate it.
If usb-storage and ehci_hcd never worked on this system, then it's likely an
EHCI problem. The fact that the unit works on other systems with relatively
recent kernels is a futher indication that something is wrong with the
Greg, please re-assign.
I found this when I increased my system memory from 2GB to 4GB. It had worked
previously. If I
#modprobe -i ehci_hcd
All is well again.
Kernels include 2.6.16-1.2096_FC5 and 184.108.40.206-4-smp (Suse 10.1).
Motherboards include Asus A8N32SLI Deluxe
and Gigaabyte GA-K8NPRO-SLI.
Created attachment 8296 [details]
apply NForce workaround earlier
This patch may well resolve the problem with nforce and
more than 2 GB memory ...
I can confirm this bug...
Has been around from earlier 2.6.1X kernels, and still is not solved.
Please test David's last patch everyone...
*** Bug 6214 has been marked as a duplicate of this bug. ***
The patch from this bug was included in kernel 2.6.18.