On Fri, 22 May 2026 15:22:05 -0500 nwe <[email protected]> wrote: > On 5/22/26 3:02 PM, Charles Curley wrote: > > > journalctl | grep -i RAM > > Sure enough, that gets me a boatload of RAM error reports on my > server.
But not one on my desktop. I also went back several boots, and still no errors. > On my desktop without ECC it does not. Possibly because without ECC one has no way to detect the errors. I don't know enough about modern RAM to be sure, so that's a guess. > I think no noise = good, Not always. Maybe if you have ECC. > however, I have rasdaemon installed on the server, I think it may > take a combination of that + ECC to make the RAM errors log. That is consistent with the description provided by "apt show rasdaemon". > It's been a while since I set this up. I think I had > to change a setting in the Dell bios to prevent its log from eating > the error instead of handing it to the os. > > I was simply reading sudo dmesg. > > If I'm correct, memtest86 is nearly useless on ECC RAM. > Maybe. "MemTest86 directly polls ECC errors logged in the chipset/memory controller registers and displays it to the user on-screen. In addition, ECC errors are written to the log and report file. "During testing, MemTest86 may report ECC errors detected by the memory controller if ECC is supported and enabled. This is demonstrated in the following screenshot:" https://www.memtest86.com/ecc.htm#memtest86 -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
