From owner-freebsd-stable Wed Jun 26 23: 6:55 2002 Delivered-To: freebsd-stable@freebsd.org Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by hub.freebsd.org (Postfix) with ESMTP id 7A7B637B4AA for ; Wed, 26 Jun 2002 23:06:27 -0700 (PDT) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.3/8.12.3) with ESMTP id g5R66MM1092390; Wed, 26 Jun 2002 23:06:25 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Message-Id: <200206270606.g5R66MM1092390@gw.catspoiler.org> Date: Wed, 26 Jun 2002 23:06:22 -0700 (PDT) From: Don Lewis Subject: Re: ahc0 data parity error To: ianjhart@ntlworld.com Cc: behanna@zbzoom.net, stable@FreeBSD.ORG In-Reply-To: <3D1A0EDB.FCD45974@ntlworld.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 26 Jun, ian j hart wrote: > Chris BeHanna wrote: >> >> On Wed, 26 Jun 2002, ict technician wrote: >> >> > I'm trying out some new motherboards and I'm getting these errors >> > when I stress the ATA disk. >> > >> > ahc0: PCI error Interrupt at seqaddr = 0x9 >> > ahc0: Data Parity Error Detected during address or write data phase >> >> I see this all the time on my 3950U2B (which is plugged into a >> Gigabyte GA-7DX, AMD chipset), even when there's no data traffic on >> the SCSI channels. I didn't see these on a 440BX-based motherboard. I haven't seen that with my Gigabyte GA-7DX+ and 2940UW. There are some documented compatibility issues between the AMD-761 northbridge and VIA southbridge on these boards (see AMD's web site, though the symptoms don't sound all that similar), and there have been issues with VIA chipsets getting properly initialized by the BIOS. Maybe Gigabyte fixed the hardware between the GA-7DX and GA-7DX+, or maybe there is a BIOS update that fixes this problem. >> The only SCSI device I have in the box currently is a CD-RW, and >> I've never had errors on it. >> > > I couldn't reproduce the problem using the LEX board, so I went > with that. > > If this is harmless why write a bright warning to the console? > (Not to mension filling the log file). If I saw these errors, I'd be worried. Something that causes parity errors could also be corrupting data. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message