From: Greg KH <greg@kroah.com>
To: Andy Lutomirski <luto@myrealbox.com>
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [BUG] usblp_write spins forever after an error
Date: Sun, 15 Feb 2004 19:58:35 -0800 [thread overview]
Message-ID: <20040216035834.GA4089@kroah.com> (raw)
In-Reply-To: <402FEAD4.8020602@myrealbox.com>
On Sun, Feb 15, 2004 at 01:55:32PM -0800, Andy Lutomirski wrote:
> I recently cancelled a print job with the printer's cancel function, and
> the CUPS backend got stuck in usblp_write (using 100% CPU and not
> responding to signals).
What kernel are you referring to here?
thanks,
greg k-h
next prev parent reply other threads:[~2004-02-16 5:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-15 21:55 [BUG] usblp_write spins forever after an error Andy Lutomirski
2004-02-16 3:58 ` Greg KH [this message]
2004-02-16 15:16 ` [linux-usb-devel] " Paulo Marques
2004-03-04 11:25 ` David Woodhouse
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=20040216035834.GA4089@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=luto@myrealbox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.