From owner-freebsd-hackers  Fri Nov  2 11:42:34 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mailout06.sul.t-online.de (mailout06.sul.t-online.com [194.25.134.19])
	by hub.freebsd.org (Postfix) with ESMTP
	id ACF3C37B431; Fri,  2 Nov 2001 11:42:16 -0800 (PST)
Received: from fwd05.sul.t-online.de 
	by mailout06.sul.t-online.de with smtp 
	id 15zkCi-00058S-04; Fri, 02 Nov 2001 20:42:12 +0100
Received: from peedub.muc.de (520017439985-0001@[217.80.233.111]) by fmrl05.sul.t-online.com
	with esmtp id 15zkCS-2JnCcqC; Fri, 2 Nov 2001 20:41:56 +0100
Received: by peedub.muc.de (8.11.6/8.11.1) id fA2Jg3q65108;
	Fri, 2 Nov 2001 20:42:03 +0100 (CET)
	(envelope-from garyj)
Message-Id: <200111021942.fA2Jg3q65108@peedub.muc.de>
Content-Type: text/plain;
  charset="iso-8859-1"
From: Gary Jennejohn <garyj@jennejohn.org>
Reply-To: garyj@jennejohn.org
To: Wilko Bulte <wkb@freebie.xs4all.nl>
Subject: Re: ahc(4) reports PCI parity error interrupt
Date: Fri, 2 Nov 2001 09:52:28 +0100
X-Mailer: KMail [version 1.3]
References: <20011102002122.A7708@freebie.xs4all.nl>
In-Reply-To: <20011102002122.A7708@freebie.xs4all.nl>
Cc: freebsd-scsi@freebsd.org, freebsd-hackers@freebsd.org
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Sender: 520017439985-0001@t-dialin.net
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Friday 02 November 2001 00:21, Wilko Bulte wrote:
[snip problem description]
> I ran the same systemdisk & all expansion cards in a PII-266
> with Intel chipset without any issue. The K7V is rock stable
> as long as I keep my fingers from fxtv.
>
> Suggestions on how to analyse/workaround this issue are most
> welcome. Anything in the BIOS setup maybe?
>

Sorry, no idea how to fix this, but I saw a very similar problem 
under Linux while writing a driver for a data-acquisition board. 
On a K7M (AMD chipset) I couldn't access the on-board memory 
reliably, but using an INTEL chipset and CPU everything worked 
just fine. Your report makes me think that there's a generic bug 
in the Athlon and not a problem in the chipsets, which is what I 
originally suspected.

-- 
Gary Jennejohn garyj@jennejohn.org gj@freebsd.org

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message