From: Pedro Monjo Florit <pmonjo2000@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Error in ohci_hcd with bluetooth dongles
Date: Wed, 04 Jan 2006 09:49:17 +0100 [thread overview]
Message-ID: <43BB8C0D.1030302@yahoo.com> (raw)
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 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
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
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
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 2 times
Dec 22 21:30:21 Host kernel: ohci_hcd 0000:00:13.0: urb c130f974 path 1.3 ep2in 5e160110
Dec 22 21:30:21 Host kernel: ohci_hcd 0000:00:13.0: urb c130f974 path 1.3 ep2in 5e1110
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 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
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
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 archives, I have seen
that this problem was once reported back in June 2004 and Marcel
answered that in 2.6.7-rc2 it was already solved.
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.
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?
Cheers,
Pedro Monjo
reply other threads:[~2006-01-04 8:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43BB8C0D.1030302@yahoo.com \
--to=pmonjo2000@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox