From owner-freebsd-arch@FreeBSD.ORG Wed Mar 23 18:49:03 2011 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D0D4106566C; Wed, 23 Mar 2011 18:49:03 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id DB40C8FC19; Wed, 23 Mar 2011 18:49:01 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id UAA13083; Wed, 23 Mar 2011 20:48:59 +0200 (EET) (envelope-from avg@freebsd.org) Message-ID: <4D8A409B.6090801@freebsd.org> Date: Wed, 23 Mar 2011 20:48:59 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Lightning/1.0b2 Thunderbird/3.1.9 MIME-Version: 1.0 To: John Baldwin References: <201103231029.p2NATtwg090498@lurza.secnetix.de> <20110323171443.GA59972@freebsd.org> <201103231426.27750.jhb@freebsd.org> In-Reply-To: <201103231426.27750.jhb@freebsd.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Alexander Best , bz@freebsd.org, Oliver Fromme , freebsd-arch@freebsd.org Subject: Re: kernel memory checks on boot vs. boot time X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Mar 2011 18:49:03 -0000 on 23/03/2011 20:26 John Baldwin said the following: > I think that doing *real* memory checks isn't really the role of our kernel. > Better effort would be spent on improving memtest86 since it is already trying > to solve this problem. Something that would be nice would be a way to invoke > memtest86 from the loader. Just a note that with sysutils/memtest86+ port you can already do that. But of course the utility is not headless and lacks the advanced functionality that you describe below. > Assuming you could pass arguments (such as a time > limit) to the memtest "kernel", then you could install memtest to > /boot/memtest and do something like 'nextboot -k memtest -o "-t 120"' to run > memtest for 2 hours on the next boot then reboot back into the stock OS after > it finishes, etc. -- Andriy Gapon