From owner-freebsd-hackers Mon Mar 29 23:58:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 591AF14D99 for ; Mon, 29 Mar 1999 23:58:17 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA37830; Mon, 29 Mar 1999 23:57:48 -0800 (PST) (envelope-from dillon) Date: Mon, 29 Mar 1999 23:57:48 -0800 (PST) From: Matthew Dillon Message-Id: <199903300757.XAA37830@apollo.backplane.com> To: Bob Bishop Cc: avalon@coombs.anu.edu.au (Darren Reed), Wilko Bulte , jkh@zippy.cdrom.com, hackers@FreeBSD.ORG Subject: Re: another ufs panic.. References: <199903292217.AAA03483@yedi.iaf.nl> <3.0.6.32.19990330083127.007bf2f0@192.168.255.1> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message