Date: Fri, 16 Jan 2015 16:56:04 -0500 From: Ed Maste <emaste@freebsd.org> To: papowell@astart.com Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: [PATCH] Display progress during getmemsize() so the kernel doesn't look like it hanged Message-ID: <CAPyFy2Cg3hRJ6sqN7JOtBJxmfBBwjcYFCpu0749Su=9Jycc6CA@mail.gmail.com> In-Reply-To: <54B927F9.1010401@astart.com> References: <D0DCA0FF.129C55%rpokala@panasas.com> <54B7656D.9000704@freebsd.org> <54B927F9.1010401@astart.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 16 January 2015 at 10:02, Patrick Powell <papowell@astart.com> wrote: > On 01/14/15 22:59, Allan Jude wrote: >> >> Glad to see this, thanks for doing the work Ravi. Also, I agree with jhb@, >> we should disable the test by default in stable/10 (i think it is off by >> default only for VMs currently). > > > Please please do not disable memory tests by default. If you do, when > trying to boot from a CD/Memory Stick > image on a system with bad memory (which would be found by the tests) then > it gets quite difficult to find this > problem. The boot time "memory test" is not particularly valuable, especially on contemporary amd64 hardware. While it won't have any false positives, there are a huge number of failure modes it will not catch. It also does not inform the user of "failure" -- it just removes that memory from the kernel's map. It's really a test of memory presence, not quality.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2Cg3hRJ6sqN7JOtBJxmfBBwjcYFCpu0749Su=9Jycc6CA>