Date: Thu, 26 Feb 2004 13:26:23 -0500 From: Charles Swiger <cswiger@mac.com> To: Noah <admin2@enabled.com> Cc: freebsd-ports@freebsd.org Subject: Re: python-2.3.3 build failing Message-ID: <47FE3ABA-6889-11D8-8B21-003065ABFD92@mac.com> In-Reply-To: <20040226175856.M6910@enabled.com> References: <20040226153007.M64716@enabled.com> <403E226A.3050202@mac.com> <20040226164721.M5540@enabled.com> <403E26CB.4070701@mac.com> <20040226175856.M6910@enabled.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 26, 2004, at 1:04 PM, Noah wrote: > On Thu, 26 Feb 2004 12:03:07 -0500, Chuck Swiger wrote >> Otherwise, try running sysutils/memtest for a day or so and see >> whether it provokes your hardware into crashing, in which case you >> should do the usual-- check cooling, swap memory and other >> components, etc... > > okay thanks for the Heads up about this utility. is there any issue > with > running memtest on a production box? If your hardware is fine, no. If the memory has issues, it's likely that memtest will crash. It's very unlikely but theoretically possible that memtest could stress bad hardware enough to produce other effects including a system panic, but that indicates a system so marginal that it would likely crash unexpectedly in other circumstances... -- -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47FE3ABA-6889-11D8-8B21-003065ABFD92>