Date: Fri, 2 Nov 2001 21:16:21 +0100 From: Wilko Bulte <wkb@freebie.xs4all.nl> To: Gary Jennejohn <garyj@jennejohn.org> 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> In-Reply-To: <200111021942.fA2Jg3q65108@peedub.muc.de>; from garyj@jennejohn.org on Fri, Nov 02, 2001 at 09:52:28AM %2B0100 References: <20011102002122.A7708@freebie.xs4all.nl> <200111021942.fA2Jg3q65108@peedub.muc.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011102211621.A16992>