Messages in this thread | | | From | (Matthias Urlichs) | Subject | Re: NMI errors in 2.0.30??u | Date | 6 May 1997 19:50:10 +0200 |
| |
R.E.Wolff@BitWizard.nl (Rogier Wolff) writes: > > Although I know that a memory test is not going to find 90% of the > memory errors, I might still want to write a kernel-option that does a > memory test just after boot. Alan, (or anybody else,) would you know
Kernel bloat! Kernel bloat! Kernel bloat! ;-)
> of a generic way to have DMA occurring concurrently with the memory > test to trigger that type of errors? I'm afraid that this would be > impossible right? > If you want to see whether your SIMMs are OK, get a good SIMM checker. A _really_ good SIMM checker.
The problem is that while the SIMM might be perfectly OK, your mainboard et al. might have somewhat-noisy lines, or subtle timing bugs, or...
Such problems are unfindable without a logic analyzer and heaps of experience. Ask anybody who does this professionally. Most people, of course, just swap components until they find a combination that seems to work correctly.
The best memory checker is a kernel recompile, a network download, and a floppy read. At the same time. Repeatedly. I have yet to see a problem that didn't eventually show up under this kind of stress.
-- When in Rome, live in the Roman way. --St. Ambrose -- Matthias Urlichs \ noris network GmbH / Xlink-POP Nürnberg Schleiermacherstraße 12 \ Linux+Internet / EMail: urlichs@noris.de 90491 Nürnberg (Germany) \ Consulting+Programming+Networking+etc'ing PGP: 1024/4F578875 1B 89 E2 1C 43 EA 80 44 15 D2 29 CF C6 C7 E0 DE Click <A HREF="http://info.noris.de/~smurf/finger">here</A>. 42
| |