From: Daniel Blueman <daniel.blueman@gmx.net>
To: David Brownell <david-b@pacbell.net>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] [2.6.0-test2-bk5] OHCI USB printing causing system lockup...
Date: Thu, 7 Aug 2003 09:37:36 +0200 (MEST) [thread overview]
Message-ID: <4210.1060241856@www4.gmx.net> (raw)
In-Reply-To: <3F319CD5.7060706@pacbell.net>
It does seem that it's the usblp driver, and I think the way forward is to
collect more information with compiling the driver with debugging to see more
of what's happening here. I'll do this tonight and report findings.
The module author string is "Michael Gee, Pavel Machek, Vojtech Pavlik,
Randy Dunlap, Pete Zaitcev, David Paschal" - who should I CC my results to?
Thanks!
> Daniel Blueman wrote:
> > When printing a test page on an Epson C62 through an unpowered USB 1.1
> hub,
> > the printer printed part of the page, then stopped.
> >
> > The 'error -110' messages were being sent to the syslogs, and after
> pulling
> > the connector to the USB hub, the system locked up.
>
> So it seems like there are two errors:
>
> - timeouts during printing, reported recently on UHCI too;
>
> - the usb_buffer_free() oops from printer cleanup, likewise.
>
> Seems more related to the printer driver than to OHCI ...
--
Daniel J Blueman
COMPUTERBILD 15/03: Premium-e-mail-Dienste im Test
--------------------------------------------------
1. GMX TopMail - Platz 1 und Testsieger!
2. GMX ProMail - Platz 2 und Preis-Qualitätssieger!
3. Arcor - 4. web.de - 5. T-Online - 6. freenet.de - 7. daybyday - 8. e-Post
prev parent reply other threads:[~2003-08-07 7:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 22:31 Daniel Blueman
2003-08-07 0:27 ` [linux-usb-devel] " David Brownell
2003-08-07 7:37 ` Daniel Blueman [this message]
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=4210.1060241856@www4.gmx.net \
--to=daniel.blueman@gmx.net \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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®