public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Ben-Gershon <mybg@netvision.net.il>
To: linux-kernel@vger.kernel.org
Cc: Tim Waugh <twaugh@redhat.com>
Subject: Re: lpr to HP laserjet stalls
Date: Tue, 04 Sep 2001 14:05:21 +0300	[thread overview]
Message-ID: <3B94B571.772A05F4@netvision.net.il> (raw)
In-Reply-To: <3B93E289.7F121DE9@netvision.net.il> <20010903221142.J20060@redhat.com>

Tim Waugh wrote:
> 
> On Mon, Sep 03, 2001 at 11:05:29PM +0300, Michael Ben-Gershon wrote:
> 
> > It is intermittent, but very frequent. It is difficult to print more
> > than about 10 sheets without it happening sometime.
> 
> Take a look at Documentation/parport.txt: see the 'Troubleshooting'
> section.

OK. Here it is:

Sep  3 00:33:28 linux kernel: 0x378: FIFO is 16 bytes
Sep  3 00:33:29 linux kernel: 0x378: writeIntrThreshold is 8
Sep  3 00:33:29 linux kernel: 0x378: readIntrThreshold is 8
Sep  3 00:33:29 linux kernel: parport0: PC-style at 0x378 (0x778)
[PCSPP,TRISTATE,COMPAT,EPP,ECP]
Sep  3 00:33:29 linux kernel: parport0: irq 7 detected
Sep  3 00:33:29 linux kernel: parport0: Printer, Hewlett-Packard HP LaserJet 6P
Sep  3 00:33:29 linux kernel: lp0: using parport0 (polling).

Here are the contents of the parport directory in /proc:

::::::::::::::
/proc/sys/dev/parport/parport0/autoprobe
::::::::::::::
CLASS:PRINTER;
MODEL:HP LaserJet 6P;
MANUFACTURER:Hewlett-Packard;
DESCRIPTION:Hewlett-Packard LaserJet 6P Printer;
COMMAND SET:PJL,MLC,PCLXL,PCL;
::::::::::::::
/proc/sys/dev/parport/parport0/autoprobe0
::::::::::::::
::::::::::::::
/proc/sys/dev/parport/parport0/autoprobe1
::::::::::::::
::::::::::::::
/proc/sys/dev/parport/parport0/autoprobe2
::::::::::::::
::::::::::::::
/proc/sys/dev/parport/parport0/autoprobe3
::::::::::::::
::::::::::::::
/proc/sys/dev/parport/parport0/base-addr
::::::::::::::
888     1912
::::::::::::::
/proc/sys/dev/parport/parport0/devices/lp/timeslice
200
::::::::::::::
/proc/sys/dev/parport/parport0/dma
::::::::::::::
-1
::::::::::::::
/proc/sys/dev/parport/parport0/irq
::::::::::::::
-1
::::::::::::::
/proc/sys/dev/parport/parport0/modes
::::::::::::::
PCSPP,TRISTATE,COMPAT,EPP,ECP
::::::::::::::
/proc/sys/dev/parport/parport0/spintime
::::::::::::::
500

As far as I can see, although IRQ 7 is detected, it is not used, so
I don't see how starting parport with irq=none would help. Could
CONFIG_PARPORT_PC_FIFO actually improve matters in such a situation?

Michael Ben-Gershon
mybg@netvision.net.il

  parent reply	other threads:[~2001-09-04 11:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-03 20:05 lpr to HP laserjet stalls Michael Ben-Gershon
2001-09-03 21:11 ` Tim Waugh
2001-09-04  0:20   ` Horst von Brand
2001-09-04  8:36     ` Tim Waugh
2001-09-04  0:56   ` Patrick Dreker
2001-09-04  8:50     ` Tim Waugh
2001-09-04 12:07       ` Patrick Dreker
2001-09-04 11:05   ` Michael Ben-Gershon [this message]
     [not found]   ` <3B94B4E7.701C76FA@netvision.net.il>
     [not found]     ` <20010904121523.Q20060@redhat.com>
2001-09-04 11:21       ` Michael Ben-Gershon
2001-09-04 11:27         ` Tim Waugh
2001-09-04 13:22           ` Michael Ben-Gershon
2001-09-04 13:27             ` Tim Waugh
2001-09-04 13:41               ` Michael Ben-Gershon
2001-09-04 13:48                 ` Tim Waugh
2001-09-04 21:17                   ` Michael Ben-Gershon

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=3B94B571.772A05F4@netvision.net.il \
    --to=mybg@netvision.net.il \
    --cc=linux-kernel@vger.kernel.org \
    --cc=twaugh@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox