Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 29 Mar 1999 23:57:48 -0800 (PST)
From:      Matthew Dillon <dillon@apollo.backplane.com>
To:        Bob Bishop <rb@gid.co.uk>
Cc:        avalon@coombs.anu.edu.au (Darren Reed), Wilko Bulte <wilko@yedi.iaf.nl>, jkh@zippy.cdrom.com, hackers@FreeBSD.ORG
Subject:   Re: another ufs panic..
Message-ID:  <199903300757.XAA37830@apollo.backplane.com>
References:  <199903292217.AAA03483@yedi.iaf.nl> <3.0.6.32.19990330083127.007bf2f0@192.168.255.1>

next in thread | previous in thread | raw e-mail | index | archive | help

:
:At 17:53 29/03/99 -0800, Matthew Dillon wrote:
:>    Generally speaking, glitches will cause SCSI bus parity errors.  Maybe
:>    not all glitches, but a high enough percentage that you usually get
:>    some sort of indication that there is a problem.
:
:...always assuming, of course, that you don't have parity checking turned
:off in the controller config :-)
:
:--
:Bob Bishop		    +44 118 977 4017
:rb@gid.co.uk		fax +44 118 989 4254 (0800-1800 UK)

    Nobody in their right mind turns off parity checking on a SCSI bus.
    ( At least, anyone who does is beyond any help that hackers can give
    them ).  This line of debate is becoming pointless.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>



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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199903300757.XAA37830>