From owner-freebsd-stable Wed Sep 20 22:26:16 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id 1429D37B423 for ; Wed, 20 Sep 2000 22:26:14 -0700 (PDT) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id AAA05811; Thu, 21 Sep 2000 00:26:09 -0500 (CDT) (envelope-from jeff-ml@mountin.net) Received: from dial-72.max1.wa.cyberlynk.net(207.227.118.72) by peak.mountin.net via smap (V1.3) id sma005802; Thu Sep 21 00:25:51 2000 Message-Id: <4.3.2.20000921001853.00b93270@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Thu, 21 Sep 2000 00:22:35 -0500 To: BSD , Chris Dillon From: "Jeffrey J. Mountin" Subject: Re: Constant panics on 4.1-STABLE! Cc: stable@FreeBSD.ORG In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dropping -bugs CC At 08:11 PM 9/20/00 -0500, BSD wrote: >On Wed, 20 Sep 2000, Chris Dillon wrote: > > I hate to tell you this, but this is most certainly a memory problem. > > Get some memory that has been tested and approved by your motherboard > > manufacturer for that board, and to be double-sure, make it ECC memory > > and then enable ECC in the motherboard's BIOS. If you STILL have > > problems after that, then you can start blaming the problem on > > something else. The ONLY other time I have had problems like this is > > when overclocking the processor. You aren't overclocking those > > processors are you? > > Are you saying all 3 sticks are bad at 133MHz (KA7) and one >or more is bad at 66MHz (BP6)? The likelihood of that is extremely small. >Also, a 512MB stick of RAM would cost me $1,600CAD. Sigh. That's not >going to happen anytime soon. Furthermore, I stress tested each stick of >RAM, with make -j64 buildworld. Nothing failed there. The panics >happenned when the system was just doing its normal tasks. I'll try to >post more detailed reports (including crash dumps). What Chris suggested is even more important if you are populating all memory slots. There is a limit to how many chips total can be driven. Try removing one from any system that is fully loaded. Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message