From: Daniel Robbins <drobbins@gentoo.org>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.3-bk9 QA testing: firewire good, USB printing dead
Date: Fri, 27 Feb 2004 19:57:32 -0700 [thread overview]
Message-ID: <1077937052.14653.40.camel@wave.gentoo.org> (raw)
In-Reply-To: <20040228021040.GA14836@kroah.com>
On Fri, 2004-02-27 at 19:10, Greg KH wrote:
> Yes, I am. Do you get any error messages in your syslog when the
> printer hangs?
In some cases, I did. In other cases, I did not. Here are some "greatest
hits... and I was also turning printers on and off and changing cables
and testing different USB ports, so this first batch of log messages
could correspond to those types of changes:
Feb 27 10:52:11 [kernel] drivers/usb/class/usblp.c: usblp0: off-line
Feb 27 10:52:44 [kernel] drivers/usb/class/usblp.c: usblp0: error -71 reading printer status
- Last output repeated 1140 times -
Feb 27 10:52:45 [kernel] usb 1-4: USB disconnect, address 9
Feb 27 10:52:45 [kernel] drivers/usb/class/usblp.c: usblp0: error -71 reading printer status
Feb 27 10:52:45 [kernel] drivers/usb/class/usblp.c: usblp0: removed
Then when I was doing my initial testing with the Epson Stylus Photo 960
and the escputil program (as well as catting printer data directly to
the printer,) I saw a bunch of stuff like this:
Feb 27 10:30:30 [kernel] usb 1-4.3: new full speed USB device using address 11
Feb 27 10:30:30 [kernel] ehci_hcd 0000:00:02.2: qh c1b91700 (#0) state 1
Feb 27 10:30:30 [kernel] drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 11 if 0 alt 0 proto 2 vid 0x04B8 pid 0x0005
Feb 27 10:31:01 [kernel] drivers/usb/class/usblp.c: usblp0: on fire
Specific symptoms were not having the printers respond to an escputil
(Epson printer utility from gimp-print) head cleaning run. On the laser
printer, data would get to the printer, but seemingly slowly, and I'd
need to hit the "go" button on the printer to get the sheet to print
rather than have the printer print on its own. It seems that both
printers did not get the full amount of data that they were expecting,
and either didn't respond at all or didn't complete the print job
without manual assistance.
The problems with the laser printer didn't generally produce any log
messages. Those with the Epson (particularly escputil) generally did.
With 2.6.3-bk9, I also had a block of two mainboard USB ports simply
stop functioning -- to the point of even no longer sending power to the
USB hub that I was using.
Hope that helps and let me know if you need any more info,
Daniel
next prev parent reply other threads:[~2004-02-28 2:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 2:01 2.6.3-bk9 QA testing: firewire good, USB printing dead Daniel Robbins
2004-02-28 2:10 ` Greg KH
2004-02-28 2:57 ` Daniel Robbins [this message]
2004-02-28 3:39 ` Kevin P. Fleming
2004-02-28 6:44 ` Greg KH
2004-02-28 21:22 ` Mike
2004-02-29 9:51 ` Jens Axboe
2004-03-01 7:43 ` [PATCH] " Barry K. Nathan
2004-03-01 8:02 ` Jens Axboe
2004-03-02 3:01 ` Mike
2004-03-02 13:09 ` Paulo Marques
2004-03-02 15:18 ` firewire good, USB printing fixed, CD-ROM block device IO errors near end of media Daniel Robbins
2004-03-02 19:26 ` [PATCH] Re: 2.6.3-bk9 QA testing: firewire good, USB printing dead Greg KH
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=1077937052.14653.40.camel@wave.gentoo.org \
--to=drobbins@gentoo.org \
--cc=greg@kroah.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