Date: Fri, 14 Jul 2000 17:10:26 +0100 From: Mike Bristow <mike@urgle.com> To: Doug Barton <Doug@gorean.org> Cc: Thomas Stromberg <tstromberg@rtci.com>, freebsd-current@freebsd.org Subject: Re: SB Live (or RAM parity?) crash on today's -CURRENT Message-ID: <20000714171026.A52843@lindt.urgle.com> In-Reply-To: <Pine.BSF.4.21.0007061831360.31780-100000@dt052n3e.san.rr.com>; from Doug@gorean.org on Thu, Jul 06, 2000 at 06:32:49PM -0700 References: <Pine.GSO.4.20.0007061413500.22502-100000@barracuda.aquarium.rtci.com> <Pine.BSF.4.21.0007061831360.31780-100000@dt052n3e.san.rr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 06, 2000 at 06:32:49PM -0700, Doug Barton wrote: > On Thu, 6 Jul 2000, Thomas Stromberg wrote: > > > 'panic: RAM parity error, likely hardware failure.' > > > > This one had me confused at first, because it blamed a RAM parity > > error. As this is a brand new machine (Gateway GP-800), so I first thought > > I got a bad batch. Then I realized this only happens with apps that try to > > do sound stuff. > > This is a known problem with all PCI sound cards. It happens most > often with ECC ram, but it also happens without. What kind of NIC do you > have, and specifically, is it a PCI card or ISA? We're trying to track > that bit down too. I see it with: mike@gurgle:~$ dmesg | grep vr0 vr0: <VIA VT3043 Rhine I 10/100BaseTX> port 0xb000-0xb07f mem 0xdf800000-0xdf80007f irq 10 at device 10.0 on pci0 The machine does have ECC ram. If you need more, let me know and I'll give you what you need... -- Mike Bristow, seebitwopie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000714171026.A52843>