From owner-freebsd-current Sat Jan 29 22:24:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 7207B16169 for ; Sat, 29 Jan 2000 22:24:03 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p25-dnz01kiryunisiki.gunma.ocn.ne.jp [210.132.6.154]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id PAA07290; Sun, 30 Jan 2000 15:23:39 +0900 (JST) Message-ID: <3893D34D.7F9C90F6@newsguy.com> Date: Sun, 30 Jan 2000 14:59:41 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Chuck Robey Cc: David Gilbert , "Sean O'Connell" , freebsd-current@FreeBSD.ORG Subject: Re: Printer fiascos. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > > Sheesh. This is a FreeBSD-questions type thing, not current. I disagree. It is obvious that something is getting locked inside the kernel in his setup. This *SHOULDN'T* happen, it's that simple. If his machine locked whenever the printer went out of paper, and *stayed* locked, I'd be willing to believe the problem was caused by hardware. That's not what was reported. What was reported is rather (better) explained by some kernel code waiting indefinitely for an event, while preventing anything else from executing. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message