From owner-freebsd-current Thu Nov 25 14:26:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id DEC8714C94 for ; Thu, 25 Nov 1999 14:26:45 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.3/8.7.3) id PAA00144; Thu, 25 Nov 1999 15:16:08 -0700 (MST) Date: Thu, 25 Nov 1999 15:16:08 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199911252216.PAA00144@narnia.plutotech.com> To: Gianmarco Giovannelli Cc: current@FreeBSD.org Subject: Re: AHC0 fireworks ? X-Newsgroups: pluto.freebsd.current In-Reply-To: <4.2.0.58.19991120091815.00c2ced0@194.184.65.4> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <4.2.0.58.19991120091815.00c2ced0@194.184.65.4> you wrote: > Hi, > I am running 4.0-current of: > FreeBSD gmarco.eclipse.org 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Thu Nov 18 > 09:33:43 CET > 1999 gmarco@gmarco.eclipse.org:/usr/src/sys/compile/GMARCO i386 > > But I have now a lot of errors (as you can see in this logs) on my scsi chain. > I had never experienced such things in the near past (even if as an old > current user sometimes I see also worse things :-) > > Btw I don't see in the current mailing list threads about iussues on the > scsi subsystem recently so it can be a problem related to my hardware (even > if I didn't experience it before)... > > I append the logs of my system (sorry for the long post): > > Now I am trying to make a "blind" make world to see it changes something... Parity errors indicate that data integrity is compromised on your SCSI cable. Perhaps you bumped a connector, or a connector had been loose for a long time and has just shifted to the point of causing a failure. Open your case, reseat everything and see if the problem clears up. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message