From owner-freebsd-current Sat Mar 3 20:25:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id B31E437B719 for ; Sat, 3 Mar 2001 20:25:13 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.11.3/8.11.3) id f244ReE43114; Sat, 3 Mar 2001 20:27:40 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200103040427.f244ReE43114@troutmask.apl.washington.edu> Subject: Re: cvs commit: src/sys/kern kern_intr.c src/sys/sys interrupt.h In-Reply-To: <200103040401.f2441tZ11380@billy-club.village.org> "from Warner Losh at Mar 3, 2001 09:01:55 pm" To: Warner Losh Date: Sat, 3 Mar 2001 20:27:40 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > In message <200103040302.f2432m742565@troutmask.apl.washington.edu> Steve Kargl writes: > : I get an instance panic if I start lpd, so I doubt you can make > : lpr performance any worse ;-) The printer is connected to the > : parallel port. On my work machine, lpd/lpr work fine, but the > : printer is connected via tcp/ip. > > I can start lpd on my machine, but sometimes the machine will panic > when an actual print job hits it. On reboot it will panic when lpd > starts sometimes. Other times it will just work. This is from a Feb > 24th -current. I have printing jobs sitting in the queue, so when lpq fires up my machine panics. I haven't tried deleting the print jobs, restarting lpd, and then printing. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message