From: "Udo A. Steinberg" <reality@delusion.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Tim Waugh <tim@cyberelk.demon.co.uk>
Subject: Parport fifo stuck when printer out of paper
Date: Tue, 17 Apr 2001 17:54:22 +0200 [thread overview]
Message-ID: <3ADC672E.5F97BAA9@delusion.de> (raw)
Hi,
When my parport printer runs out of paper and there are still
pending print jobs, the kernel will constantly log the following:
DMA write timed out
parport0: FIFO is stuck
parport0: BUSY timeout (1) in compat_write_block_pio
To me it's pretty pointless to fill dmesg and the logfiles with
this rather harmless but still annoying info.
Can this possibly be handled in a nicer way, so that the kernel
keeps quiet about such minor printer issues?
Regards,
Udo.
next reply other threads:[~2001-04-17 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-17 15:54 Udo A. Steinberg [this message]
2001-04-17 21:18 ` Parport fifo stuck when printer out of paper Tim Waugh
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=3ADC672E.5F97BAA9@delusion.de \
--to=reality@delusion.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tim@cyberelk.demon.co.uk \
/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.