Alan Stern wrote:
On Tue, 17 Jan 2006, Pedro Monjo Florit wrote:
Hi everyone,
I am using kernel 2.6.12 patched with Marcel Holtmann patches
(2.6.12-mh3) and a custom Linux distribution based on Linux From Scratch
6.1. I attach up to three CSR-based Bluetooth dongles, through USB.
I have a problem with the ohci_hcd module. For some (still unknown)
reason, at a random time, I start to get error messages in syslog, at a
rate of about 150 text lines per second, until they fill up the entire
hard disk. This does not happen always, only from time to time. Here is
a sample of the messages:
Dec 22 21:30:21 Host kernel: ohci_hcd 0000:00:13.0: urb c130f7f4 path
1.3 ep1in 5f160000 cc 5 --> status -110
Dec 22 21:30:21 Host kernel: ohci_hcd 0000:00:13.0: urb c130f974 path
1.3 ep2in 5e160000 cc 5 --> status -110
Dec 22 21:30:21 Host last message repeated 3 times
I have found where the error is generated in the kernel souces (file
ohci-q.c), but I am not an expert in USB protocol, so I do not know
exactly when is this triggered. Searching in the kernel archives, I have
seen that this problem was once reported back in June 2004 and Marcel
Holtmann answered that in 2.6.7-rc2 it was already solved; but I think
that the problem was different from mine.
I must add that the problem may be well due to a hardware error, but I
want to make sure that the problem is not in the software. I am trying
to find out the causes of the error.
What does exactly this error mean? When is it generated? Is there any
known reason that could make the kernel enter an infinite loop that
would generate this error continously, even in the absence of the
original condition?
-110 is -ETIMEDOUT. In this case it means that the device is not
responding to data sent by the computer.
I don't know what you mean by "the absence of the original condition".
Presumably that condition (device not responding) is still present. The
driver is probably written so that it keeps on trying to communicate with
the device -- and getting these errors -- until the device is
disconnected.
Alan Stern
Thank you for your answer.
What I meant by "the absence of the original condition" is whether the
kernel code would get in an infinite loop triggered by an error in a USB
device or once this error is solved, the error messages stop.
In any case, how can I know where the error was happening from the log
messages? In a USB hub or in a USB device?
Regards,
Pedro Monjo
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
