From owner-freebsd-current  Thu Jun 22 12:42:03 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id MAA22600
          for current-outgoing; Thu, 22 Jun 1995 12:42:03 -0700
Received: from silver.sms.fi ([194.111.122.1])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA22572
          for <current@freebsd.org>; Thu, 22 Jun 1995 12:41:27 -0700
Received: (from pete@localhost) by silver.sms.fi (8.6.11/8.6.9) id WAA01382; Thu, 22 Jun 1995 22:41:05 +0300
Date: Thu, 22 Jun 1995 22:41:05 +0300
Message-Id: <199506221941.WAA01382@silver.sms.fi>
From: Petri Helenius <pete@sms.fi>
To: Julian Howard Stacey <jhs@vector.eikon.e-technik.tu-muenchen.de>
Cc: current@freebsd.org
Subject: kernel response
In-Reply-To: <199506221515.RAA00867@vector.eikon.e-technik.tu-muenchen.de>
References: <199506221515.RAA00867@vector.eikon.e-technik.tu-muenchen.de>
Sender: current-owner@freebsd.org
Precedence: bulk

Julian Howard Stacey writes:
 > 
 > So it seems the parallel port output flush is running at too high a priority
 > for too long.
 > 
 > If I've forgotten to mention something, please let me know.
 > 
This has happened to me also, both with 2.0R and SNAP-950322. Haven't
upgraded from that so I cannot tell whether it has been fixed.

Pete