Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #286822

Re: bad RAM (Was: Schrödinger's hash)

From Charles Curley <charlescurley@charlescurley.com>
Newsgroups linux.debian.user
Subject Re: bad RAM (Was: Schrödinger's hash)
Date 2026-05-22 23:10 +0200
Message-ID <MXFi2-77gr-5@gated-at.bofh.it> (permalink)
References <MXAs1-73P1-5@gated-at.bofh.it> <MXABI-749f-11@gated-at.bofh.it> <MXC0N-74Uj-1@gated-at.bofh.it> <MXElX-76CR-7@gated-at.bofh.it> <MXEFn-76K4-53@gated-at.bofh.it>
Organization occasionally

Show all headers | View raw


On Fri, 22 May 2026 15:22:05 -0500
nwe <nwe@gitcoding.net> 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/

Back to linux.debian.user | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Schrödinger's hash Charles Curley <charlescurley@charlescurley.com> - 2026-05-22 18:00 +0200
  Re: Schrödinger's hash Andrew Latham <lathama@gmail.com> - 2026-05-22 18:10 +0200
    Re: Schrödinger's hash Charles Curley <charlescurley@charlescurley.com> - 2026-05-22 18:20 +0200
      Re: Schrödinger's hash Andrew Latham <lathama@gmail.com> - 2026-05-22 18:30 +0200
        Re: Schrödinger's hash Charles Curley <charlescurley@charlescurley.com> - 2026-05-22 19:00 +0200
    bad RAM (Was: Schrödinger's hash) nwe <nwe@gitcoding.net> - 2026-05-22 19:40 +0200
      Re: bad RAM (Was: Schrödinger's hash) Charles Curley <charlescurley@charlescurley.com> - 2026-05-22 22:10 +0200
        Re: bad RAM (Was: Schrödinger's hash) nwe <nwe@gitcoding.net> - 2026-05-22 22:30 +0200
          Re: bad RAM (Was: Schrödinger's hash) Charles Curley <charlescurley@charlescurley.com> - 2026-05-22 23:10 +0200
            Re: bad RAM (Was: Schrödinger's hash) nwe <nwe@gitcoding.net> - 2026-05-22 23:30 +0200
          Re: bad RAM (Was: Schrödinger's hash) David Christensen <dpchrist@holgerdanske.com> - 2026-05-23 02:00 +0200
            Re: bad RAM (Was: Schrödinger's  hash) Andy Smith <andy@strugglers.net> - 2026-05-25 13:20 +0200
              Re: bad RAM (Was: Schrödinger's hash) David Christensen <dpchrist@holgerdanske.com> - 2026-05-25 23:20 +0200
          Re: bad RAM Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2026-05-25 11:50 +0200
  Re: Schrödinger's hash The Wanderer <wanderer@fastmail.fm> - 2026-05-22 18:20 +0200
    Re: Schrödinger's hash Charles Curley <charlescurley@charlescurley.com> - 2026-05-22 19:10 +0200
  Re: Schrödinger's hash David Christensen <dpchrist@holgerdanske.com> - 2026-05-22 20:10 +0200
  Re: Schrödinger's hash Van Snyder <van.snyder@sbcglobal.net> - 2026-05-22 20:40 +0200
    Re: Schrödinger's hash nwe <nwe@gitcoding.net> - 2026-05-22 21:50 +0200
      Re: Schrödinger's hash David Christensen <dpchrist@holgerdanske.com> - 2026-05-23 01:30 +0200
        Re: Schrödinger's hash Van Snyder <van.snyder@sbcglobal.net> - 2026-05-23 01:40 +0200
        Re: Schrödinger's hash nwe <nwe@gitcoding.net> - 2026-05-23 02:20 +0200
          Re: Schrödinger's hash David Christensen <dpchrist@holgerdanske.com> - 2026-05-23 07:50 +0200
            Home server (Was: Re: Schrödinger's hash) nwe <nwe@gitcoding.net> - 2026-05-23 17:00 +0200
              Re: Home server (Was: Re: Schrödinger's hash) David Christensen <dpchrist@holgerdanske.com> - 2026-05-24 04:30 +0200

csiph-web