From owner-freebsd-hackers Fri Nov 2 12:16:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtpzilla2.xs4all.nl (smtpzilla2.xs4all.nl [194.109.127.138]) by hub.freebsd.org (Postfix) with ESMTP id D663237B40D; Fri, 2 Nov 2001 12:16:24 -0800 (PST) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtpzilla2.xs4all.nl (8.12.0/8.12.0) with ESMTP id fA2KGMfB072179; Fri, 2 Nov 2001 21:16:22 +0100 (CET) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id fA2KGMn26986; Fri, 2 Nov 2001 21:16:22 +0100 (CET) (envelope-from wkb) Date: Fri, 2 Nov 2001 21:16:21 +0100 From: Wilko Bulte To: Gary Jennejohn Cc: freebsd-scsi@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: ahc(4) reports PCI parity error interrupt Message-ID: <20011102211621.A16992@freebie.xs4all.nl> References: <20011102002122.A7708@freebie.xs4all.nl> <200111021942.fA2Jg3q65108@peedub.muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200111021942.fA2Jg3q65108@peedub.muc.de>; from garyj@jennejohn.org on Fri, Nov 02, 2001 at 09:52:28AM +0100 X-OS: FreeBSD 4.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Nov 02, 2001 at 09:52:28AM +0100, Gary Jennejohn wrote: > 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. It appears things are more complicated than that. I have swapped the Adaptec 29160 for a 2940UW. I am now running continous buildworlds, a 'dd' of the SCSI disk and fxtv in parallel. This appears to work like a charm until now. I'll let it run and see what develops Wilko -- | / o / /_ _ email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message