From owner-freebsd-questions@FreeBSD.ORG Thu Jul 7 21:08:11 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C85F16A41C for ; Thu, 7 Jul 2005 21:08:11 +0000 (GMT) (envelope-from ml@t-b-o-h.net) Received: from vjofn.tucs-beachin-obx-house.com (vjofn.tucs-beachin-obx-house.com [204.107.90.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83F5843D48 for ; Thu, 7 Jul 2005 21:08:10 +0000 (GMT) (envelope-from ml@t-b-o-h.net) Received: from himinbjorg.tucs-beachin-obx-house.com (ool-44c511d8.dyn.optonline.net [68.197.17.216]) (authenticated bits=128) by vjofn.tucs-beachin-obx-house.com (8.12.9/8.12.9) with ESMTP id j67L4Ovd072659; Thu, 7 Jul 2005 17:04:25 -0400 (EDT) Received: from himinbjorg.tucs-beachin-obx-house.com (localhost.tucs-beachin-obx-house.com [127.0.0.1]) by himinbjorg.tucs-beachin-obx-house.com (8.13.3/8.12.10) with ESMTP id j67L81te018340; Thu, 7 Jul 2005 17:08:01 -0400 (EDT) (envelope-from ml@t-b-o-h.net) Received: (from tbohml@localhost) by himinbjorg.tucs-beachin-obx-house.com (8.13.3/8.13.1/Submit) id j67L81Vs018338; Thu, 7 Jul 2005 17:08:01 -0400 (EDT) (envelope-from tbohml) From: Tuc at T-B-O-H Message-Id: <200507072108.j67L81Vs018338@himinbjorg.tucs-beachin-obx-house.com> To: xfb52@dial.pipex.com (Alex Zbyslaw) Date: Thu, 7 Jul 2005 17:08:01 -0400 (EDT) In-Reply-To: <42B84964.6070909@dial.pipex.com> from "Alex Zbyslaw" at Jun 21, 2005 06:07:48 PM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Tuc at T-B-O-H , freebsd-questions@freebsd.org Subject: Re: Problems since 5.3-RELEASE-p15 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jul 2005 21:08:11 -0000 > >>If the problem is intermittent then I would suspect the hardware (I > >>know, everyone always says that, but I really have used a brand new > >>server which segfaulted randomly and it really was a memory problem). > >>Try building a memtest86 CD from the ports (from a different machine > >>perhaps) and running it for at least several hours, though it might not > >>take that long. Your BIOS might also support extended memory tests (try > >>disabling quick POST) though they are supposed to be less effective than > >>memtest86. > >> > >> > >> > > Ok, will try that. I run SETI so I think I'm constantly stressing > >the machine. But I'll give it a try. > > > *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. Tuc