From owner-freebsd-current Thu Jul 6 19:30:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from barracuda.aquarium.rtci.com (barracuda.aquarium.rtci.com [208.11.247.5]) by hub.freebsd.org (Postfix) with ESMTP id 4776A37BAE8 for ; Thu, 6 Jul 2000 19:30:41 -0700 (PDT) (envelope-from tstromberg@rtci.com) Received: from barracuda (barracuda [208.11.247.5]) by barracuda.aquarium.rtci.com (8.9.3+Sun/8.9.3) with ESMTP id WAA17098; Thu, 6 Jul 2000 22:30:33 -0400 (EDT) Date: Thu, 6 Jul 2000 22:30:18 -0400 (EDT) From: Thomas Stromberg X-Sender: tstromberg@barracuda.aquarium.rtci.com To: Doug Barton Cc: freebsd-current@freebsd.org Subject: Re: SB Live (or RAM parity?) crash on today's -CURRENT In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Its in the dmesg from my post, but: CPU: Pentium III/Pentium III Xeon/Celeron (796.54-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383f9ff real memory = 134217728 (131072K bytes) avail memory = 127098880 (124120K bytes) .. pcib0: on motherboard pci0: on pcib0 pci0: at 0.0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 11 .. pci0: at 7.2 irq 9 pci0: at 7.3 pcm0: port 0x10a0-0x10bf irq 11 at device 14.0 on pci0 xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0x1000-0x107f mem 0xf4000000-0xf400007f irq 10 at device 15.0 on pci0 Good luck.. happy to test patches. ------------------------------------------------------------------------ thomas r. stromberg tstromberg@rtci.com senior systems administrator http://www.afterthought.org/ research triangle commerce, inc. 1.919.657.1317 bless(\$Perl++); # the power to hack. http://www.perl.com/ #include /* the power to serve. http://www.freebsd.org/ */ ------------------------------------------------------------------------ On Thu, 6 Jul 2000, 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. > > Doug > -- > "Live free or die" > - State motto of my ancestral homeland, New Hampshire > > Do YOU Yahoo!? > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message