From owner-freebsd-hackers  Tue Mar 30 18:35:44 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
	by hub.freebsd.org (Postfix) with ESMTP id 130A214DC8
	for <hackers@FreeBSD.ORG>; Tue, 30 Mar 1999 18:35:42 -0800 (PST)
	(envelope-from mjacob@feral.com)
Received: from localhost (mjacob@localhost)
	by feral.com (8.8.7/8.8.7) with ESMTP id SAA00445;
	Tue, 30 Mar 1999 18:34:41 -0800
Date: Tue, 30 Mar 1999 18:34:41 -0800 (PST)
From: Matthew Jacob <mjacob@feral.com>
X-Sender: mjacob@feral-gw
Reply-To: mjacob@feral.com
To: Peter Jeremy <peter.jeremy@auss2.alcatel.com.au>
Cc: hackers@FreeBSD.ORG
Subject: Re: another ufs panic..
In-Reply-To: <99Mar31.114807est.40597@border.alcanet.com.au>
Message-ID: <Pine.LNX.4.04.9903301834340.28-100000@feral-gw>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, 31 Mar 1999, Peter Jeremy wrote:

> 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.
> 

Can't tell.




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