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

From	nwe <nwe@gitcoding.net>
Newsgroups	linux.debian.user
Subject	Re: bad RAM (Was: Schrödinger's hash)
Date	2026-05-22 22:30 +0200
Message-ID	<MXEFn-76K4-53@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>
Organization	linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

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. 
On my desktop without ECC it does not. I think no noise = good, however, 
I have rasdaemon installed on the server, I think it may take a 
combination of that + ECC to make the RAM errors log. 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.

Back to linux.debian.user | Previous | Next — Previous 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