Date: Tue, 30 Mar 1999 20:40:20 +0200 (CEST) From: Wilko Bulte <wilko@yedi.iaf.nl> To: rb@gid.co.uk (Bob Bishop) Cc: avalon@coombs.anu.edu.au, dillon@apollo.backplane.com, jkh@zippy.cdrom.com, hackers@FreeBSD.ORG Subject: Re: another ufs panic.. Message-ID: <199903301840.UAA01034@yedi.iaf.nl> In-Reply-To: <3.0.6.32.19990330083127.007bf2f0@192.168.255.1> from Bob Bishop at "Mar 30, 1999 8:31:27 am"
next in thread | previous in thread | raw e-mail | index | archive | help
As Bob Bishop wrote ...
> At 17:53 29/03/99 -0800, Matthew Dillon wrote:
> > Generally speaking, glitches will cause SCSI bus parity errors. Maybe
"Generally" that is true... ;-) I'm just playing the devil's advocate
a bit here.
> > not all glitches, but a high enough percentage that you usually get
> > some sort of indication that there is a problem.
True. But I've heard stories about PCI bridge chips in combination
with specific adapter firmware revs corrupting data. In general, everything in
the datapath can cause you grief. With the crappy PC hardware out there
(and/or overclocked crappy PC h/w to make it worse) anything is possible.
Even without SCSI.
> ...always assuming, of course, that you don't have parity checking turned
> off in the controller config :-)
There is single word to describe that idea: "stupid"
Groeten / Cheers,
Wilko
_ ______________________________________________________________________
| / o / / _ Arnhem, The Netherlands
|/|/ / / /( (_) Bulte WWW : http://www.tcja.nl
_______________________ Powered by FreeBSD ___ http://www.freebsd.org _____
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?199903301840.UAA01034>