On Saturday 2023-08-12 15:29, Stan Johnson wrote:
On 8/12/23 3:33 AM, Gregor Riepl wrote:
... The V215 is very picky about RAM
(requires buffered DDR-333 modules with ECC).
I've attached logs from two kernel panics for reference. One happened at
boot time, the other after some heavy compilation and debugging. Both
aren't reproducible reliably, but they did happen a few times.
...
I've seen similar errors on other systems (mostly x86 and powerpc) that
did turn out to be intermittent memory errors. Have you tried memtester?
Even though it won't test all the memory, running memtester in
single-user mode should test most of it.
Anecdote from my side:
It isn't always memory which is at fault.
I have had encounters with e.g. VIA KT266 (or something in that time
of that questionable quality) where something in the southbridge or
IDE cable must have been messed up enough that reads from harddisk
would bitflip occassionally. So when a .so file was read (or re-read
after pushed out of the pagecache) and it flipped, some instruction
would now access '[eax+0x80000002]' rather than '[eax+2]', all
programs utilizing that would suddenly but reliably SIGSEGV, but it'd
be gone at the next boot for a while -- and memtest86 wouldn't
show a damn thing.
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)