From owner-freebsd-hackers Tue Mar 30 20:22:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (Postfix) with ESMTP id 8276A155A6 for ; Tue, 30 Mar 1999 20:22:31 -0800 (PST) (envelope-from drew@plutotech.com) Received: from pluto.plutotech.com (drew@pluto.l206.plutotech.com [206.168.67.1]) by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id VAA94479 for ; Tue, 30 Mar 1999 21:22:12 -0700 (MST) (envelope-from drew@plutotech.com) Message-Id: <199903310422.VAA94479@pluto.plutotech.com> To: freebsd-hackers@freebsd.org Subject: Re: another ufs panic.. X-Newsgroups: pluto.freebsd.hackers In-Reply-To: Organization: Date: Tue, 30 Mar 1999 21:22:11 -0700 From: Drew Eckhardt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >On Wed, 31 Mar 1999, Peter Jeremy wrote: >> 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. Some chips (Symbios) allow one to tweak parity for testing purposes. One could take advantage of this by executing some command guaranteed to be supported (test unit ready) with bad parity and watching what happened. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message