mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Paulo Marques <pmarques@grupopie.com>
Cc: Greg KH <greg@kroah.com>, Andy Lutomirski <luto@myrealbox.com>,
	linux-usb-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: [BUG] usblp_write spins forever after an error
Date: Thu, 04 Mar 2004 11:25:33 +0000	[thread overview]
Message-ID: <1078399532.4619.129.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <4030DEC5.2060609@grupopie.com>

On Mon, 2004-02-16 at 15:16 +0000, Paulo Marques wrote:
> This patch corrected a problem for me, that happened when a printer presents an 
> out-of-paper status while printing a document. The driver would send endless 
> garbage to the printer.

This patch went in to 2.6.4-rc1, didn't it? It seems to have exacerbated
a problem which used to be occasional, but now seems to happen after
every print job.

I see the following, and the error repeats until I power cycle the
printer (HPLJ 1200 on AMD768 OHCI):

usb 1-1.3.2: control timeout on ep0in
drivers/usb/class/usblp.c: usblp0: error -110 reading printer status



-- 
dwmw2


  reply	other threads:[~2004-03-04 11:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-15 21:55 Andy Lutomirski
2004-02-16  3:58 ` Greg KH
2004-02-16 15:16   ` [linux-usb-devel] " Paulo Marques
2004-03-04 11:25     ` David Woodhouse [this message]
2004-03-04 12:33       ` Paulo Marques
2004-03-05  9:41         ` David Woodhouse
2004-03-05 14:27           ` Paulo Marques
2004-03-05 18:11             ` [PATCH] usblp.c (Was: usblp_write spins forever after an error) Paulo Marques
2004-03-11  1:33               ` Greg KH
2004-05-10 11:34               ` David Woodhouse
2004-02-17  4:40   ` [BUG] usblp_write spins forever after an error Andy Lutomirski

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=1078399532.4619.129.camel@hades.cambridge.redhat.com \
    --to=dwmw2@infradead.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=luto@myrealbox.com \
    --cc=pmarques@grupopie.com \
    /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®