== This is not bug report, only informational message. ==
Hallo parport developers,
looking into log after _SUCCESFUL_ printing with 2.4.0-test9 I have found many fuzzy messages
in syslog:
Oct 20 10:20:43 utx kernel: 0x378: FIFO is 16 bytes
Oct 20 10:20:43 utx kernel: 0x378: writeIntrThreshold is 16
Oct 20 10:20:43 utx kernel: 0x378: readIntrThreshold is 16
Oct 20 10:20:43 utx kernel: parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
Oct 20 10:20:43 utx kernel: parport0: Printer, Hewlett-Packard HP LaserJet 6P
Oct 20 10:20:43 utx kernel: lp0: using parport0 (interrupt-driven).
Oct 20 10:20:43 utx kernel: 0x378: PWord is 8 bits
Oct 20 10:20:43 utx kernel: 0x378: Interrupts are ISA-Pulses
Oct 20 10:20:43 utx kernel: 0x378: ECP port cfgA=0x10 cfgB=0x40
Oct 20 10:20:43 utx kernel: 0x378: ECP settings irq=<none or set by other means> dma=<none or set by other means>
Oct 20 10:20:43 utx kernel: parport0: cpp_daisy: aa5500ff(98)
Oct 20 10:20:43 utx kernel: parport0: assign_addrs: aa5500ff(98)
Oct 20 10:21:21 utx kernel: DMA write timed out
Oct 20 10:22:01 utx kernel: DMA write timed out
Oct 20 10:23:07 utx last message repeated 3 times
Oct 20 10:24:10 utx last message repeated 3 times
Oct 20 10:24:20 utx kernel: parport0: FIFO is stuck
Oct 20 10:24:20 utx kernel: parport0: BUSY timeout (1) in compat_write_block_pio
Oct 20 10:24:43 utx kernel: DMA write timed out
Oct 20 10:24:55 utx kernel: DMA write timed out
Oct 20 10:26:56 utx kernel: DMA write timed out
Oct 20 10:28:01 utx last message repeated 3 times
Oct 20 10:28:11 utx kernel: parport0: FIFO is stuck
Oct 20 10:28:11 utx kernel: parport0: BUSY timeout (1) in compat_write_block_pio
Oct 20 10:28:29 utx kernel: DMA write timed out
Oct 20 10:29:14 utx kernel: DMA write timed out
Oct 20 10:30:05 utx last message repeated 2 times
Oct 20 10:30:52 utx last message repeated 2 times
Note: I have only one problem with new IRQ driver - if I really need to cancel
running print job. lprm (from LPRng) + reset printer is far from sufficience.
But this is not a problem of kernel.
-- Stanislav Brabec-- To unsubscribe, send mail to: linux-parport-request@torque.net -- -- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2b29 : Fri Oct 20 2000 - 17:01:05 EDT