From owner-freebsd-hackers Sat Nov 3 2:12:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtpzilla5.xs4all.nl (smtpzilla5.xs4all.nl [194.109.127.141]) by hub.freebsd.org (Postfix) with ESMTP id 34E4837B415; Sat, 3 Nov 2001 02:12:53 -0800 (PST) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtpzilla5.xs4all.nl (8.12.0/8.12.0) with ESMTP id fA3ACobc025870; Sat, 3 Nov 2001 11:12:50 +0100 (CET) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id fA3ACot00344; Sat, 3 Nov 2001 11:12:50 +0100 (CET) (envelope-from wkb) Date: Sat, 3 Nov 2001 11:12:50 +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: <20011103111249.A327@freebie.xs4all.nl> References: <20011102002122.A7708@freebie.xs4all.nl> <200111021942.fA2Jg3q65108@peedub.muc.de> <20011102211621.A16992@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011102211621.A16992@freebie.xs4all.nl>; from wkb@freebie.xs4all.nl on Fri, Nov 02, 2001 at 09:16:21PM +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:16:21PM +0100, Wilko Bulte wrote: > 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 It takes a while, but then it fails: fxtv looses the picture and cc (from the buildworld) started sig11-ing. [No, this is not then RAM, it only happens when fxtv runs] Seems I better loose the TVcard :-/ -- | / 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