From owner-freebsd-current Thu Jul 6 18:33:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt052n3e.san.rr.com (dt052n3e.san.rr.com [204.210.33.62]) by hub.freebsd.org (Postfix) with ESMTP id 0446437BBBA for ; Thu, 6 Jul 2000 18:33:07 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from slave (doug@slave [10.0.0.1]) by dt052n3e.san.rr.com (8.9.3/8.9.3) with ESMTP id SAA31923; Thu, 6 Jul 2000 18:32:49 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Thu, 6 Jul 2000 18:32:49 -0700 (PDT) From: Doug Barton X-Sender: doug@dt052n3e.san.rr.com To: Thomas Stromberg 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 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