Bug 122827
| Summary: | USB printing fails | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | David Woodhouse <dwmw2> |
| Component: | kernel | Assignee: | Pete Zaitcev <zaitcev> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2 | CC: | davej |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-04-16 04:26:18 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
David Woodhouse
2004-05-08 19:35:53 UTC
It's very nice that the error persists, because it gives us an opportunity to do this: - Shut down CUPS with "service cups stop" - cat /etc/hosts > /dev/usb/lp0 If it causes the same errors, as it should, do this: - strace -o /tmp/trace.out cat /etc/hosts > /dev/usb/lp0 Interrupt with ^C if the thing loops. Attach the trace to the bug. Bah. It's apparently been doing it all the time while I've been away for the last few weeks, but now I'm trying to reproduce it, it won't -- even when I send PCL jobs from Windows. Dunno if that's because it's actually fixed in 2.6.5-1.354smp, but I don't see that anything relevant changed. I've left cups stracing _every_ print job backend. We're going to see that it ends up in D state in sys_write()... then what? David, what is the status of this? Does it keep happening? What kernel versions? Not entirely sure -- it's only The Boss who prints stuff at home and she hasn't complained recently -- but then again it's the summer holidays so she's mostly watching the Olympics and not really working. I thought I saw another patch which was supposed to fix it in 2.6.7-494.2.2, and I couldn't swear that it's happened since then. Now testing 2.6.8-1.520. I did catch one strace but then tmpwatch ate it. :) I think this should fix this bug (rcomplete=0): http://lkml.org/lkml/2004/7/27/156 It's in 2.6.8, but maybe earlier. The stock 2.6.7 is problematic. The 2.6.7-494.2.2 is fixed, I checked. Please close if it's not a problem anymore. (self-closing - looks like David forgot about it) Just happened again with 2.6.8-1.631.dwmw2smp (which differs only in having the updated speedtouch driver, and the separate kernel-devel stuff) I'm sure it's not your Speedtouch patch, I saw that and it's ok. Was the symptom the same (flood of -110s in the read pipe?) Yes, precisely the same. Also reported on lkml recently:
From: Georg Schild <dangertools>
Subject: Weird behaviour of usb printer (drivers/usb/class/usblp.c:
usblp0: error -110 reading printer status)
Date: Sun, 17 Oct 2004 23:34:12 +0200
Message-ID: <4172E554.1000906>
fixed in 2.6.9 ? No, Dave, don't needinfo this... It's a bug on my special list of unsolvable cases (I mean... unsolvable without the equipment access). I keep the printer driver same between 2.6 and 2.4, fixes go both directions. No hope for 2.6 separate from 2.4. Fedora Core 2 has now reached end of life, and no further updates will be provided by Red Hat. The Fedora legacy project will be producing further kernel updates for security problems only. If this bug has not been fixed in the latest Fedora Core 2 update kernel, please try to reproduce it under Fedora Core 3, and reopen if necessary, changing the product version accordingly. Thank you. |