From owner-freebsd-current@FreeBSD.ORG Tue Feb 14 17:41:45 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3265916A420 for ; Tue, 14 Feb 2006 17:41:45 +0000 (GMT) (envelope-from V.Konrad@lse.ac.uk) Received: from exic6.lse.ac.uk (exic6.lse.ac.uk [158.143.217.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1106443D49 for ; Tue, 14 Feb 2006 17:41:38 +0000 (GMT) (envelope-from V.Konrad@lse.ac.uk) Received: from ExF1.lse.ac.uk ([158.143.216.11]) by exic6.lse.ac.uk with Microsoft SMTPSVC(5.0.2195.6713); Tue, 14 Feb 2006 17:41:37 +0000 Received: exchange.lse.ac.uk 158.143.216.11 from 158.143.216.101 158.143.216.101 via HTTP with MS-WebStorage 6.0.6249 Received: 158.143.216.101 158.143.216.101 from 158.143.201.23 158.143.201.23 via HTTP with MS-WebStorage 6.0.6249 Received: from whirpool.lse.ac.uk by exchange.lse.ac.uk; 14 Feb 2006 17:41:38 +0000 From: Vladimir Konrad To: FreeBSD Current Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 14 Feb 2006 17:41:38 +0000 Message-Id: <1139938898.2050.70.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 X-OriginalArrivalTime: 14 Feb 2006 17:41:37.0435 (UTC) FILETIME=[E7B77EB0:01C6318D] Subject: memtest - an idea X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Feb 2006 17:41:45 -0000 is it viable to have a memtest like process running full-time (low priority) or scheduled, on running FreeBSD system to discover bad memory sooner than a later (without taking the system off-line)? being on the receiving end of a bad memory module (FreeBSD did random reboots, checked the memory with memtest and there it was), it would be nice if the OS could spot this. vlad