From: Marc Haber <mh+linux-kernel@zugschlus.de>
To: linux-kernel@vger.kernel.org
Subject: pl2303 - pl2303_open - failed submitting interrupt urb, error -28
Date: Tue, 2 Dec 2008 14:18:21 +0100 [thread overview]
Message-ID: <20081202131821.GA25217@torres.zugschlus.de> (raw)
Hi,
the following applies to a "vanilla" 2.6.27.7 kernel built and running
on a Debian unstable system.
To obtain out-of-band access to a number of switches and routers, I
have a seven-port USB hub to which seven identical USB-to-serial
adaptors using the PL2303 chip and driver are connected. All seven
work when only one of them is used at a time.
Cereal is an application which keeps a process (GNU screen) attached
to the tty at all times to be able to log what happens on the serial
port. When I start cereal on all seven ports, I start getting
"pl2303_open - failed submitting interrupt urb, error -28" errors in
my syslog:
Dec 2 14:07:36 alemana kernel: pl2303 ttyUSB2: pl2303_open - failed submitting interrupt urb, error -28
Dec 2 14:07:37 alemana kernel: pl2303 ttyUSB5: pl2303_open - failed submitting interrupt urb, error -28
Dec 2 14:07:38 alemana kernel: pl2303 ttyUSB6: pl2303_open - failed submitting interrupt urb, error -28
Dec 2 14:07:41 alemana kernel: pl2303 ttyUSB2: pl2303_open - failed submitting interrupt urb, error -28
Dec 2 14:07:43 alemana kernel: pl2303 ttyUSB5: pl2303_open - failed submitting interrupt urb, error -28
Dec 2 14:07:43 alemana kernel: pl2303 ttyUSB6: pl2303_open - failed submitting interrupt urb, error -28
Dec 2 14:07:47 alemana kernel: pl2303 ttyUSB2: pl2303_open - failed submitting interrupt urb, error -28
Dec 2 14:07:48 alemana kernel: pl2303 ttyUSB5: pl2303_open - failed submitting interrupt urb, error -28
Dec 2 14:07:49 alemana kernel: pl2303 ttyUSB6: pl2303_open - failed submitting interrupt urb, error -28
The corresponding ports are not useable in that case.
When one googles for this error message, one finds a thread from 2006
with Greg KH commenting. In my case, the error doesn't hose the USB
subsystem, I can unplug the adapters and plug them in again one and a
time without a problem, and I can even use the ports that don't throw
this error message.
As in the 2006 thread, unloading the EHCI driver (ehci_hcd) solves the
issue, but is of course not an attractive option as soon as one wants
to use even a USB stick on the same machine.
If it helps, I can give out root access to the box in question to
anybody who is willing to help and debug. Unfortunately, I cannot
provide any expertise here, I do not even know what an interrupt urb is.
Any hints will be appreciated.
Greetings
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190
next reply other threads:[~2008-12-02 13:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 13:18 Marc Haber [this message]
2008-12-03 9:42 ` Andrew Morton
2008-12-03 15:47 ` Greg KH
2008-12-05 12:10 ` Marc Haber
2008-12-05 16:03 ` Alan Stern
2008-12-09 20:11 ` Marc Haber
2008-12-10 13:43 ` Marc Haber
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=20081202131821.GA25217@torres.zugschlus.de \
--to=mh+linux-kernel@zugschlus.de \
--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
all inboxes | Powered by JetHome®