Date: Thu, 07 Jul 2005 23:41:19 +0100 From: Alex Zbyslaw <xfb52@dial.pipex.com> To: Tuc at T-B-O-H <ml@t-b-o-h.net> Cc: freebsd-questions@freebsd.org Subject: Re: Problems since 5.3-RELEASE-p15 Message-ID: <42CDAF8F.5080807@dial.pipex.com> In-Reply-To: <200507072108.j67L81Vs018338@himinbjorg.tucs-beachin-obx-house.com> References: <200507072108.j67L81Vs018338@himinbjorg.tucs-beachin-obx-house.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Tuc at T-B-O-H wrote: >>*If* there are intermittent memory errors, then it could be that SETI >>always happens to get them in the data it is dealing with, in which case >>it might run perfectly happily but just produce the wrong results. >>Memtest is dull, and stops you using your PC, but like Windows virus >>scans, it seems like a necessary evil in this case. >> >> >> > I did the standard tests for 24 hours (21 passes) and it didn't fail. >I ran the 90 minute fading one for 24 hours (8 runs) and it too didn't fail. > > It's almost a shame when a test like this passes. It's much easier to just replace some memory and get on with things than be stuck with an intermittent problem. Could something be overheating? Are you still getting random segfaults? Is there *any* pattern you can see? --Alex
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42CDAF8F.5080807>