From owner-freebsd-current@FreeBSD.ORG  Mon Sep 24 11:15:53 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 1621716A420
	for <freebsd-current@freebsd.org>; Mon, 24 Sep 2007 11:15:53 +0000 (UTC)
	(envelope-from serguey-grigoriev@yandex.ru)
Received: from webmail31.mail.yandex.net (webmail31.mail.yandex.net
	[213.180.223.177])
	by mx1.freebsd.org (Postfix) with ESMTP id 50D4313C44B
	for <freebsd-current@freebsd.org>; Mon, 24 Sep 2007 11:15:52 +0000 (UTC)
	(envelope-from serguey-grigoriev@yandex.ru)
Received: from YAMAIL (webmail31) by mail.yandex.ru id S6455822AbXIXLPp for
	<freebsd-current@freebsd.org>; Mon, 24 Sep 2007 15:15:45 +0400
X-Yandex-Spam: 1
Received: from [77.244.18.3] ([77.244.18.3]) by mail.yandex.ru with HTTP;
	Mon, 24 Sep 2007 15:15:45 +0400
From: "S.N.Grigoriev" <serguey-grigoriev@yandex.ru>
To: freebsd-current@freebsd.org
MIME-Version: 1.0
Message-Id: <1291921190632545@webmail31.yandex.ru>
Date: Mon, 24 Sep 2007 15:15:45 +0400
X-Mailer: Yamail [ http://yandex.ru ] 5.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailman-Approved-At: Tue, 25 Sep 2007 08:28:28 +0000
Subject: Re: Parallel port printing crashes 7.0 system
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Sep 2007 11:15:53 -0000

Hi, list,

This problem has already been reported this year at least twice.
I can confirm it still exists. Probably it has been introduced
near the beginning of May because April and earlyer sources
handle parallel printing correctly.

This problem is dealt with the parallel port interrupt handling.
There is a workaround to avoid system crashes during printing:
to switch parallel ports to the polling mode. But the system
behaviour in this situation is not completely correct. For example
the mouse pointer is periodically blocked on the screen for a few
seconds.

Regards,
Serguey.