On Thu, Aug 08, 2002, Adam J. Richter <adam@yggdrasil.com> wrote:
> Mark J Roberts writes:
> >Printing complicated postscript documents makes my Kyocera FS-1010
> >hit that timeout. I increased it to 240 seconds and the problem
> >seems to have disappeared.
> >
> >I guess there ought to be a blacklist or something.
>
> I saw a similar thing a few weeks ago (under 2.5.27?) with the
> Hewlett-Packard 656C ink jet printer, which only occurred when I would
> send a page with images on it, so the printer really would need a long
> time before it was ready to accept more data.
>
> I would hope that the kernel should be able to wait as long
> as the printer wants before the printer indicates that it is ready for
> more data. I don't know if this is a bug in these printers' USB
> implementations or if it is a real kernel bug. I just haven't had
> time to investigate it yet (and I no longer have access to that printer,
> although 656C's are only $30 at Fry's).
I suspect it's a bug in the kernel.
It sounds like the printer is NAKing all of the transfers while it's
busy flushing out the data sent to it. This is to be expected because it
can only store so much data and sending data is MUCH faster than it can
print it.
I think the problem is that the printer driver has a timeout. I don't
think it should. It just doesn't make sense in this case. I say let the
device NAK as long as it wants. It's the applications job to decide if
it's been too long or not.
JE
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Aug 15 2002 - 22:00:18 EST