[PATCH] Display progress during getmemsize() so the kernel doesn't look like it hanged

Patrick Powell papowell at astart.com
Sat Jan 17 16:57:51 UTC 2015


On 01/16/15 13:56, Ed Maste wrote:
> On 16 January 2015 at 10:02, Patrick Powell <papowell at 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.

Right.  But at least it gets you crawling...  or staggering... so you 
can do further diagnostics.

Bad memory is a *((*&^( NASTY problem.

Since we seem to have diverged a bit on topic,  any recommendations for 
stand-alone memory tests?

-- 
Patrick Powell                 Astart Technologies
papowell at astart.com            1530 Jamacha Rd, Suite X
Network and System             San Diego, CA 92019
   Consulting                   858-874-6543 FAX 858-751-2435
Web: www.astart.com



More information about the freebsd-hackers mailing list