From nox@saturn.kn-bremen.de  Fri Dec 17 11:46:05 1999
Return-Path: <nox@saturn.kn-bremen.de>
Received: from blaubaer.kn-bremen.de (blaubaer.kn-bremen.de [195.37.179.254])
	by hub.freebsd.org (Postfix) with ESMTP id 77C5A14DD0
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 17 Dec 1999 11:46:04 -0800 (PST)
	(envelope-from nox@saturn.kn-bremen.de)
Received: from saturn.kn-bremen.de (uucp@localhost)
	by blaubaer.kn-bremen.de (8.9.1/8.9.1) with UUCP id UAA01904
	for FreeBSD-gnats-submit@freebsd.org; Fri, 17 Dec 1999 20:43:08 +0100
Received: (from nox@localhost)
	by saturn.kn-bremen.de (8.9.3/8.8.5) id UAA25488;
	Fri, 17 Dec 1999 20:27:46 +0100 (CET)
Message-Id: <199912171927.UAA25488@saturn.kn-bremen.de>
Date: Fri, 17 Dec 1999 20:27:46 +0100 (CET)
From: Juergen Lock <nox@jelal.kn-bremen.de>
Sender: nox@saturn.kn-bremen.de
Reply-To: nox@jelal.kn-bremen.de
To: FreeBSD-gnats-submit@freebsd.org
Subject: Reboot just to kill a print job?
X-Send-Pr-Version: 3.2

>Number:         15532
>Category:       kern
>Synopsis:       Reboot just to kill a print job?
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Fri Dec 17 11:50:02 PST 1999
>Closed-Date:    Wed Mar 28 11:17:29 PST 2001
>Last-Modified:  Wed Mar 28 11:17:39 PST 2001
>Originator:     Juergen Lock
>Release:        FreeBSD 3.3-STABLE i386
>Organization:
me?  organized?
>Environment:

	3.3-STABLE i386 and an (old) parallel printer

>Description:

	I just lpr'd a page and then heared strange sounds from
the printer:  paper jam...  Now i cannot remember when this printer
last had a paper jam in all the years i have it (if ever, it is
_old_, ink jet printers weren't even invented when i got it i
believe), but one day it had to happen i guess...  Anyway i hit
offline, teared off the offending page (i said the printer is
old :), killed the job and powecycled the printer (there's no other
way to reset it i believe), but when i then sent the job again the
printer only got garbage.  so i had to hit offline again...

	Well turned out the filter processes (gs...) from the jammed
job were still around, and i couldn't kill them either because they
were hanging on the (now offline again) printer device.  So the
only fix seemed to be a reboot. :/  (Or is there some way for a
device on the parallel port to indicate a reset/poweroff that this
printer just doesn't use?)

>How-To-Repeat:

	Switch offline and reset printer and kill the job when the
filter isn't yet finished sending data?

>Fix:
	
	??  Maybe add a `wakeup everyone waiting and flush and
ignore all output until close' ioctl to the lpt driver that lprm
could use when killing an active job?

>Release-Note:
>Audit-Trail:

From: Alexander Langer <alex@big.endian.de>
To: Juergen Lock <nox@jelal.kn-bremen.de>
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: kern/15532: Reboot just to kill a print job?
Date: Sat, 18 Dec 1999 11:06:09 +0100

 Also sprach Juergen Lock (nox@jelal.kn-bremen.de):
 
 > old :), killed the job and powecycled the printer (there's no other
 > way to reset it i believe), but when i then sent the job again the
 > printer only got garbage.  so i had to hit offline again...
 
 Yes, that happens to me every time I get those problems.
 Also try booting the machine while the printer prints. The same
 result.
 
 If you reboot your Windows box while the printer prints, the print-job
 is completed at exactly this page where it stopped next boot.
 
 > only fix seemed to be a reboot. :/  (Or is there some way for a
 > device on the parallel port to indicate a reset/poweroff that this
 > printer just doesn't use?)
 
 I usually use a combination of
 lpc down all
 lpc disable all
 killall lpd
 
 switch of the printer
 restart lpd
 
 switch on the printer
 lpc up all
 lpc enable all
 
 Soemthink _like_ this usually fixes it.
 
 Alex
 

From: Juergen Lock <nox@jelal.kn-bremen.de>
To: Alexander Langer <alex@big.endian.de>
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: kern/15532: Reboot just to kill a print job?
Date: Sat, 18 Dec 1999 17:31:38 +0100

 On Sat, Dec 18, 1999 at 11:06:09AM +0100, Alexander Langer wrote:
 > Also sprach Juergen Lock (nox@jelal.kn-bremen.de):
 > 
 > > old :), killed the job and powecycled the printer (there's no other
 > > way to reset it i believe), but when i then sent the job again the
 > > printer only got garbage.  so i had to hit offline again...
 > 
 > Yes, that happens to me every time I get those problems.
 
 Sounds like you get paper jam often?  (What printer is that?)
 
 > Also try booting the machine while the printer prints. The same
 > result.
 > 
  Oh.  even if you reset the printer too?
 
 > If you reboot your Windows box while the printer prints, the print-job
 > is completed at exactly this page where it stopped next boot.
 
  Whow :)  sounds like one thing that M$ did get right.
 (Well of course a unix box isn't supposed to be rebooted as often
 as you need to reboot a crashed wintendo box...  Or like, `The
 mouse cursor has moved.  Please reboot for the change to take
 effect.')
 > 
 > > only fix seemed to be a reboot. :/  (Or is there some way for a
 > > device on the parallel port to indicate a reset/poweroff that this
 > > printer just doesn't use?)
 > 
 > I usually use a combination of
 > lpc down all
 > lpc disable all
 > killall lpd
 > 
 > switch of the printer
 > restart lpd
 > 
 > switch on the printer
 > lpc up all
 > lpc enable all
 > 
 > Soemthink _like_ this usually fixes it.
 
  Hmm.  Does that also help when the filter still hangs blocking on
 the printer device like in my case, with no signal being able to
 kill it?  Somehow i doubt it...
 
  Regards,
 -- 
 Juergen Lock <nox.foo@jelal.kn-bremen.de>
 (remove dot foo from address to reply)
 

From: Alexander Langer <alex@big.endian.de>
To: Juergen Lock <nox@jelal.kn-bremen.de>
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: kern/15532: Reboot just to kill a print job?
Date: Sun, 19 Dec 1999 12:11:55 +0100

 Also sprach Juergen Lock (nox@jelal.kn-bremen.de):
 
 > > > old :), killed the job and powecycled the printer (there's no other
 > > > way to reset it i believe), but when i then sent the job again the
 > > > printer only got garbage.  so i had to hit offline again...
 > > Yes, that happens to me every time I get those problems.
 > Sounds like you get paper jam often?  (What printer is that?)
 
 HP Laserjet 4, but I sometimes use print to both pages, and if the
 page has been printed already ones paper jams occur often.
 It's the bad paper that makes these appear.
 
 > > Also try booting the machine while the printer prints. The same
 > > result.
 >  Oh.  even if you reset the printer too?
 
 Can't remember.
 
 >  Hmm.  Does that also help when the filter still hangs blocking on
 > the printer device like in my case, with no signal being able to
 > kill it?  Somehow i doubt it...
 
 Yes, I doubt it, too.
 
 Alex
 

From: Juergen Lock <nox@jelal.kn-bremen.de>
To: Alexander Langer <alex@big.endian.de>
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: kern/15532: Reboot just to kill a print job?
Date: Mon, 20 Dec 1999 23:33:55 +0100

 On Sun, Dec 19, 1999 at 12:11:55PM +0100, Alexander Langer wrote:
 > Also sprach Juergen Lock (nox@jelal.kn-bremen.de):
 > 
 > > > > old :), killed the job and powecycled the printer (there's no other
 > > > > way to reset it i believe), but when i then sent the job again the
 > > > > printer only got garbage.  so i had to hit offline again...
 > > > Yes, that happens to me every time I get those problems.
 > > Sounds like you get paper jam often?  (What printer is that?)
 > 
 > HP Laserjet 4, but I sometimes use print to both pages, and if the
 > page has been printed already ones paper jams occur often.
 > It's the bad paper that makes these appear.
 > 
 Ooh.  Yes, feeding a laserprinter/photocopier its pages again to print
 on the other side often ends with paper jam.  Somtimes waiting a
 while before the second pass helps if you do have to do this, to let
 the paper cool down...
 
 > > > Also try booting the machine while the printer prints. The same
 > > > result.
 > >  Oh.  even if you reset the printer too?
 > 
 > Can't remember.
 > 
  If that Laserjet 4 is the same/similar model than the one we
 have at work then reset is a two-button combination, no need
 to powercycle.
 
  Regards,
 -- 
 Juergen Lock <nox.foo@jelal.kn-bremen.de>
 (remove dot foo from address to reply)
 
State-Changed-From-To: open->closed 
State-Changed-By: phk 
State-Changed-When: Wed Mar 28 11:17:29 PST 2001 
State-Changed-Why:  
Antique PR. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=15532 
>Unformatted:
