From owner-freebsd-hackers Mon Mar 29 17:53:42 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 96B5C14CEF for ; Mon, 29 Mar 1999 17:53:40 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA36139; Mon, 29 Mar 1999 17:53:17 -0800 (PST) (envelope-from dillon) Date: Mon, 29 Mar 1999 17:53:17 -0800 (PST) From: Matthew Dillon Message-Id: <199903300153.RAA36139@apollo.backplane.com> To: Wilko Bulte Cc: avalon@coombs.anu.edu.au (Darren Reed), jkh@zippy.cdrom.com, hackers@FreeBSD.ORG Subject: Re: another ufs panic.. References: <199903292217.AAA03483@yedi.iaf.nl> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Which does not *have* to mean anything. Glitches on the control lines on the :SCSI bus can cause devices to latch wrong data from that same bus. :Guess what ufs thinks of this ;-) : :But admittedly, this is rare. So, it is probably safe to assume :there is another cause for your grief. : :Groeten / Cheers, :Wilko 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. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message