From owner-freebsd-hackers  Tue Mar 30 18: 2:44 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10])
	by hub.freebsd.org (Postfix) with ESMTP id 3A08C15544
	for <hackers@FreeBSD.ORG>; Tue, 30 Mar 1999 18:02:36 -0800 (PST)
	(envelope-from peter.jeremy@auss2.alcatel.com.au)
Received: by border.alcanet.com.au id <40597>; Wed, 31 Mar 1999 11:48:07 +1000
Date: Wed, 31 Mar 1999 08:14:15 +1000
From: Peter Jeremy <peter.jeremy@auss2.alcatel.com.au>
Subject: Re: another ufs panic..
To: hackers@FreeBSD.ORG
Message-Id: <99Mar31.114807est.40597@border.alcanet.com.au>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Matthew Dillon <dillon@apollo.backplane.com> wrote:
>    Nobody in their right mind turns off parity checking on a SCSI bus.

Sounds like it would be useful for the kernel to warn if a SCSI target
(including the controller) has parity disabled.  How easy is it to
detect this?  I can't quickly see it in the device-independent parts
of of a drive spec.

Peter


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message