Date: Sun, 28 Mar 2010 11:34:02 -0600 From: Adam Vande More <amvandemore@gmail.com> To: Masoom Shaikh <masoom.shaikh@gmail.com> Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org, Ivan Voras <ivoras@freebsd.org>, freebsd-questions@freebsd.org Subject: Re: random FreeBSD panics Message-ID: <6201873e1003281034s52636444h113cc8760a007490@mail.gmail.com> In-Reply-To: <b10011eb1003280742i3d45b14bu6492328ce5bc745a@mail.gmail.com> References: <b10011eb1003280128k4034e667v1377205888e7a2d@mail.gmail.com> <honb8m$ncu$1@dough.gmane.org> <b10011eb1003280418l2038c651saf0d09fc48ab3966@mail.gmail.com> <9bbcef731003280503q4993e5b4ud8d874b8e9c376a9@mail.gmail.com> <b10011eb1003280742i3d45b14bu6492328ce5bc745a@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Mar 28, 2010 at 8:42 AM, Masoom Shaikh <masoom.shaikh@gmail.com>wrote: > nopes, this didn't help too, machine freezed again after using for 30 > minutes or so > all it was doing is playing amarok, fetching sources from svn repos, > and using firefox > > lets assume if this is h/w problem, then how can other OSes overcome > this ? is there a way to make FreeBSD ignore this as well, let it > result in reasonable performance penalty. > They would remove or replace the bad hardware. I've seen more that one DIMM which passed every memory checker I could find in it's most extensive testing mode. Only consistently effective option is to replace with a known good piece of memory. -- Adam Vande More
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6201873e1003281034s52636444h113cc8760a007490>