From owner-freebsd-current Fri Jul 14 9:10:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from lindt.urgle.com (lindt.urgle.com [195.173.172.169]) by hub.freebsd.org (Postfix) with ESMTP id C4B1837B87C for ; Fri, 14 Jul 2000 09:10:38 -0700 (PDT) (envelope-from mike@urgle.com) Received: from mike by lindt.urgle.com with local (Exim 3.03 #1) id 13D82k-000Dkb-00; Fri, 14 Jul 2000 17:10:26 +0100 Date: Fri, 14 Jul 2000 17:10:26 +0100 From: Mike Bristow To: Doug Barton Cc: Thomas Stromberg , freebsd-current@freebsd.org Subject: Re: SB Live (or RAM parity?) crash on today's -CURRENT Message-ID: <20000714171026.A52843@lindt.urgle.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from Doug@gorean.org on Thu, Jul 06, 2000 at 06:32:49PM -0700 X-Rated: Cocaine, COSCO, Tony Blair Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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: 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