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

From	David Christensen <dpchrist@holgerdanske.com>
Newsgroups	linux.debian.user
Subject	Re: bad RAM (Was: Schrödinger's hash)
Date	2026-05-25 23:20 +0200
Message-ID	<MYKSl-7RDO-5@gated-at.bofh.it> (permalink)
References	(2 earlier) <MXC0N-74Uj-1@gated-at.bofh.it> <MXElX-76CR-7@gated-at.bofh.it> <MXEFn-76K4-53@gated-at.bofh.it> <MXHWx-78Om-1@gated-at.bofh.it> <MYBvH-7Lbf-7@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On 5/25/26 04:16, Andy Smith wrote:
> Hi,


Hello.  :-)


> The only machines I have ECC RAM in also have Machine Check Exception
> messages go to a log in the firmware. I have experienced running
> memtest86 for a few successful complete passes and then finding messages
> in the firmware log about things that were corrected, which enabled me
> to locate the bad stick.
> 
> Also, most of the time I've had RAM fail it's done so in a way that ECC
> can't fix, because ECC can only correct a single bit flip.
> 
> So, I have continued ti find memtest86 useful although it would be a bit
> less so if I had no way to see the MCE log.


It sounds like I need to learn about Debian's "collectd-core" module and 
mcelog(8) (?).


David

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