Date: Wed, 23 Mar 2011 20:48:59 +0200 From: Andriy Gapon <avg@freebsd.org> To: John Baldwin <jhb@freebsd.org> Cc: Alexander Best <arundel@freebsd.org>, bz@freebsd.org, Oliver Fromme <olli@lurza.secnetix.de>, freebsd-arch@freebsd.org Subject: Re: kernel memory checks on boot vs. boot time Message-ID: <4D8A409B.6090801@freebsd.org> In-Reply-To: <201103231426.27750.jhb@freebsd.org> References: <alpine.BSF.2.00.1103221634241.6104@ai.fobar.qr> <201103231029.p2NATtwg090498@lurza.secnetix.de> <20110323171443.GA59972@freebsd.org> <201103231426.27750.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D8A409B.6090801>