Date: Sat, 16 Feb 2002 10:19:09 -0500 From: stan <stanb@awod.com> To: freebsd-stable@freebsd.org Subject: Re: panic on 4.5-RELEASE Message-ID: <20020216151909.GA27401@teddy.fas.com> In-Reply-To: <3C6E66EC.2050403@potentialtech.com> References: <20020213230828.34F3341EF4@mail.flipdog.com> <20020215175541.8BB33422CF@mail.flipdog.com> <3C6E66EC.2050403@potentialtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Feb 16, 2002 at 09:04:28AM -0500, Bill Moran wrote: > Jan L. Peterson wrote: > >Yes, yes, following up to my own post and all that... > > > >It appears that it may have been bad RAM. I have swapped out the RAM > >on the machine with the new disk and have not seen the problem. If I > >see it again, I'll send out a new report. > > You know, I see this all the time. Bad RAM seems to be about the most > common harware problem out there. > Just a few days ago, I spend an entire morning trying to figure out why > a brand new machine kept panicing on install. The panic messages seemed > to suggest the HDD and I tried 3 different HDDs before I got smart and > swapped out the RAM. It installed and has been running fine for 3 days > now. > I've never experienced it, but I've heard a lot of people mention that > some other OS ran fine, but installing FreeBSD uncovered a problem with > RAM. Does anyone know why this is? What does FreeBSD do differently > with RAM that causes it to expose flaky RAM more than Windows-ish OSes? > For what it's worth metmtest86 seems to be the best resource I have ever seen for testing ram. -- "They that would give up essential liberty for temporary safety deserve neither liberty nor safety." -- Benjamin Franklin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020216151909.GA27401>