public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Package compile failures with "internal compiler error: Segmentation fault".
Date: Thu, 05 Sep 2024 10:36:19 +0100	[thread overview]
Message-ID: <2000420.usQuhbGJ8B@rogueboard> (raw)
In-Reply-To: <Ztl0-PHsdOa4h-ut@schatulle>

[-- Attachment #1: Type: text/plain, Size: 1480 bytes --]

On Thursday 5 September 2024 10:08:08 BST Frank Steinmetzger wrote:
> Am Wed, Sep 04, 2024 at 11:38:01PM +0100 schrieb Michael:
> > Some MoBos are more tolerant than others.
> > 
> > Regarding Dale's question, which has already been answered - yes, anything
> > the bad memory has touched is suspect of corruption.  Without ECC RAM a
> > dodgy module can cause a lot of damage before it is discovered.
> 
> Actually I was wondering: DDR5 has built-in ECC. But that’s not the same as
> the server-grade stuff, because it all happens inside the module with no
> communication to the CPU or the OS. So what is the point of it if it still
> causes errors like in Dale’s case?
> 
> Maybe that it only catches 1-bit errors, but Dale has more broken bits?

Or it could be Dale's kit is DDR4?

Either way, as you say DDR5 is manufactured with On-Die ECC capable of 
correcting a single-bit error, necessary because DDR5 chip density has 
increased to the point where single-bit flip errors become unavoidable.  It 
also allows manufacturers to ship chips which would otherwise fail the JEDEC 
specification.  On-Die ECC will only correct bit flips *within* the memory 
chip.

Conventional Side-Band ECC with one additional chip dedicated to ECC 
correction is capable of correcting errors while data is being moved by the 
memory controller between the memory module and CPU/GPU.  It performs much 
more heavy lifting and this is why ECC memory is slower.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-09-05  9:36 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03 23:28 [gentoo-user] Package compile failures with "internal compiler error: Segmentation fault" Dale
2024-09-04  0:12 ` [gentoo-user] " Grant Edwards
2024-09-04  0:39   ` Dale
2024-09-04  4:16     ` corbin bird
2024-09-06 20:15     ` Dale
2024-09-06 23:17       ` Michael
2024-09-07  3:02         ` Dale
2024-09-07 22:12     ` Wols Lists
2024-09-08  1:59       ` Dale
2024-09-08 13:32         ` Michael
2024-09-08  9:15       ` Michael
2024-09-08 20:19         ` Wol
2024-09-04  7:53   ` Raffaele Belardi
2024-09-04  4:26 ` [gentoo-user] " Eli Schwartz
2024-09-04 10:48 ` [gentoo-user] " Dale
2024-09-04 11:05   ` Frank Steinmetzger
2024-09-04 11:21     ` Dale
2024-09-04 15:57       ` Peter Humphrey
2024-09-04 19:09       ` Grant Edwards
2024-09-04 21:08         ` Frank Steinmetzger
2024-09-04 21:22           ` Grant Edwards
2024-09-04 21:53             ` Dale
2024-09-04 22:07               ` Grant Edwards
2024-09-04 22:14                 ` Dale
2024-09-04 22:38                 ` Michael
2024-09-05  0:11                   ` Dale
2024-09-05  8:05                     ` Michael
2024-09-05  8:36                       ` Dale
2024-09-05  8:42                         ` Michael
2024-09-05 10:53                           ` Dale
2024-09-05 11:08                             ` Michael
2024-09-05 11:30                               ` Dale
2024-09-05 18:55                                 ` Frank Steinmetzger
2024-09-05 22:06                                   ` Michael
2024-09-06  0:43                                     ` Dale
2024-09-06 12:21                                       ` Michael
2024-09-06 21:41                                         ` Frank Steinmetzger
2024-09-07  9:37                                           ` Michael
2024-09-07 16:28                                             ` Frank Steinmetzger
2024-09-07 17:08                                           ` Mark Knecht
2024-09-14 19:46                                           ` Dale
2024-09-15 22:29                                             ` Frank Steinmetzger
2024-09-16 10:24                                               ` Dale
2024-09-07 22:48                                     ` Wols Lists
2024-09-08  9:37                                       ` Michael
2024-09-05  9:08                   ` Frank Steinmetzger
2024-09-05  9:36                     ` Michael [this message]
2024-09-05 10:01                       ` Frank Steinmetzger
2024-09-05 10:59                         ` Dale
2024-09-04 14:21     ` Grant Edwards
2024-09-04 11:37   ` Dale
2024-09-04 14:23     ` Grant Edwards
2024-09-04 15:58       ` Peter Humphrey
2024-09-04 19:28         ` Dale
2024-09-25 20:41 ` Dale

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2000420.usQuhbGJ8B@rogueboard \
    --to=confabulate@kintzios.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox