From owner-aic7xxx Wed Jul 29 08:53:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18312 for aic7xxx-outgoing; Wed, 29 Jul 1998 08:53:18 -0700 (PDT) (envelope-from owner-aic7xxx@FreeBSD.ORG) Received: from einstein.phy.duke.edu (root@einstein.phy.duke.edu [152.3.182.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18283 for ; Wed, 29 Jul 1998 08:53:05 -0700 (PDT) (envelope-from rgb@phy.duke.edu) Received: from ganesh.phy.duke.edu (rgb@ganesh.phy.duke.edu [152.3.183.52]) by einstein.phy.duke.edu (8.8.8/8.8.8) with ESMTP id LAA21650; Wed, 29 Jul 1998 11:52:31 -0400 (EDT) Received: from localhost (rgb@localhost) by ganesh.phy.duke.edu (8.8.5/8.8.5) with SMTP id LAA08701; Wed, 29 Jul 1998 11:49:54 -0400 X-Authentication-Warning: ganesh.phy.duke.edu: rgb owned process doing -bs Date: Wed, 29 Jul 1998 11:49:54 -0400 (EDT) From: "Robert G. Brown" To: Steffen Grunewald cc: Matthias Klose , AIC7xxx@FreeBSD.ORG Subject: Re: Made boot images for Debian/GNU 2.0 Linux In-Reply-To: <199807290730.JAA16509@mehl.gfz-potsdam.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-aic7xxx@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 29 Jul 1998, Steffen Grunewald wrote: > Matthias Klose wrote: > |> > |> Btw, the whole day I only got PARITY erros from the SCSI > |> controller. Finally (for another reason) I changed the monitor (!) and > |> the PARITY errors disappeared. PC hardware ... or driver problems? > > radio emissions from them monitor and bad SCSI cables ? > did you try to reduce the transmit rate of your drives ? > could be a serious flaw, so check it out before it's too late. > (we lost 3*9GB lkast week because of bad SCSI cables :-((( ) I hate to even mention it but on one of the systems (the one that worked but then failed) its PCI video card briefly failed after I recabled, then came back spontaneously. I may try something really radical like reseating all the PCI devices. Back in the old days when I did Suns (as in 4/110's and 386i's and SS1's:-) they would occasionally fail their memory test because the SIMMS were in "dirty" slots -- just a bit of dust or corrosion was enough to cause parity errors on considerably slower memory than is used today. I cannot do anything about the onboard SCSI controllers, but maybe the aic7xxx errors are really generic PCI bus errors tweaked when writing to the bus while there is interference on the bus from a "bad" card connection. This could easily depend on macroscopic stuff like how much the boxes were knocked around in transit or how hard I push the cables onto their card connectors. rgb Robert G. Brown http://www.phy.duke.edu/~rgb/ Duke University Dept. of Physics, Box 90305 Durham, N.C. 27708-0305 Phone: 1-919-660-2567 Fax: 919-660-2525 email:rgb@phy.duke.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe aic7xxx" in the body of the message