Adam and Mario,
1 The box only has 32Mb of ram, so it won’t take forever.
2 I have as much as 5 min to run the self tests. This will be the longest
part of them.
3 The box is expected to be non-responsive during this test. I already
figure interrupts would need to be off.
4 Map, test, map is what I had envisoned, but mapping larger chunks would
shorten the time.
5 The idea of killing everything possible off, and then allocating memory
and testing it sounds interesting, but we would have to ensure that the
program we wanted to run would run in the area we had just tested. Possibly
using a pair of these routines could test most of ram, but what about kernel
memory, shared objects, drivers… that can’t be stopped.
Is there a way to shut down these kernel and driver related memory users,
and relocate them into memory that has been tested, then test the memory
they were using??
We are also exploring the possiblity of using the bios ram check, but we
would have to reboot to use that.
Thanks for the suggestions,
“Adam Mallory” <email@example.com> wrote in message
Mario Charest firstname.lastname@example.org wrote in message
news:bb54he$jsg$> email@example.com> …
Not to mention, the proposed test was destructive - regardless of if
restore what was there. Writing a ‘pattern’ into an area of code is
to cause havoc since for any process (proc/kernel or not).
Not if interrupt are disabled during testing. This is’t real-time
That would be quite difficult to do, since you can’t map much with
interrupts off. I suppose you could map everything first, then turn off
interrupts and go ‘test’, but that will be a very long time to have a
completely non responsive computer. I doubt that would be any more
acceptable. And as an added bonus you might not be able to tell if you
tripped over bad ram and froze, or had a bug and spent your time spinning
somewhere with interrupts off, or are just taking a lot of time hitting
the mapped RAM.