memory errors

By: Etienne Lorrain (, March 4, 2021 6:26 am
Room: Moderated Discussions
dmcq ( on March 4, 2021 5:16 am wrote:
> ...
> I think the important thing is error detection - not recovery. Error recovery at a low level is nice to
> have but if the whole business can be fixed at a higher level and the error rate is low enough it is not
> really necessary. Intel leaving out ECC was dreadful, the thing that I think was really criminal and cretinous
> though was cutting out even parity checking. I see it as a cheap trick to obscure errors so people just
> blamed gremlins and pressed ctrl-alt-delete rather than fixing underlyng problems. Of course some memory
> problems would escape that but it would catch memory that is failing and it would give an indication of
> how reliable it is overall.

Historically, I think ECC error detection was removed approximately at the time it took too much time to initialise the memory. At power-up, the parity bit is not initialised: if you dump the DDR before initialisation you get mostly zero bits but you will also get bits set (I do not know why the capacitor is still charged at power-up). If you do a quick power-cycle, it is obvious you will still have bits set.
When the memory of the PC increased to few tens of megabytes, the CPU (at that time) was not able to clear that DRAM (so initialise the ECC) in less than 10 seconds, and the PC never had a powerful DMA to do such work. To cut boot time, they removed the parity bit.

The problem of when to initialise ECC is still there, and on some embedded system I worked on, I was intentionally setting ECC errors on every ECC lines at boot to be sure the O.S. (when present, or the bootloader) do not use directly uninitialised memory. Obviously you can only do that if you take control of the CPU just after reset, any "secure boot" stuff will not help.

You need to ensure you initialise the ECC correctly, one usual problem is if you write less than an ECC line, you may get an ECC error at write time.

That is why IHMO the O.S. should manage itself any ECC (non recoverable) error, ignore it if it is new memory allocated to a process, correct it if it comes from a file-backed page, and stop the owning process(es) if necessary (i.e. cannot correct). And log the address of the error.
Having "secure boot" and virtual boxes do not help, but giving only invalid ECC memory block would probably also detect bugs there.

< Previous Post in ThreadNext Post in Thread >
TopicPosted ByDate
CPU & Memory bit flipsGanon2021/03/03 09:05 AM
  Also "Silent Data Corruption"Adrian2021/03/03 10:42 AM
    Thanks for the referenceGanon2021/03/03 11:47 AM
  Implications for linux page cacheanon2021/03/03 11:54 AM
    Implications for linux page cacheLinus Torvalds2021/03/03 01:54 PM
      memory errorsblaine2021/03/03 02:53 PM
        memory errorsanon22021/03/03 05:30 PM
          memory errorsdmcq2021/03/04 05:16 AM
            memory errorsEtienne Lorrain2021/03/04 06:26 AM
              memory errorsdmcq2021/03/04 06:40 AM
                memory errorsEtienne Lorrain2021/03/04 06:58 AM
                  memory errorsdmcq2021/03/04 07:12 AM
                  memory errorsCarson2021/03/05 02:31 AM
                    memory errorsEtienne Lorrain2021/03/05 06:23 AM
                      memory errorsrwessel2021/03/05 07:48 AM
                      memory errorsdmcq2021/03/05 12:01 PM
                        memory errorsrwessel2021/03/05 12:23 PM
                          memory errorsdmcq2021/03/05 12:51 PM
                      memory errorsBrendan2021/03/05 11:38 PM
                      memory errorsCarson2021/03/06 01:35 AM
                        memory errorsCarson2021/03/06 06:24 AM
                memory errorsDavid Hess2021/03/04 01:44 PM
                  memory errorsrwessel2021/03/04 05:14 PM
                  memory errorsLinus Torvalds2021/03/04 08:21 PM
                    memory errorsanon22021/03/04 09:46 PM
                      memory errorsCarson2021/03/05 02:43 AM
                        memory errorsanon22021/03/05 07:55 AM
                    memory errorsgallier22021/03/05 02:22 AM
                  memory errorsdmcq2021/03/05 12:59 PM
                    memory errorsDavid Hess2021/03/06 04:27 AM
                      memory errorsCarson2021/03/06 06:44 AM
                      memory errorsGabriele Svelto2021/03/06 10:11 AM
                        memory errorsDavid Hess2021/03/06 10:28 AM
                          memory errorsMichael S2021/03/06 02:45 PM
              memory errorsDoug S2021/03/04 10:48 AM
                memory errorsMichael S2021/03/04 11:36 AM
              memory errorsJörn Engel2021/03/04 03:32 PM
                memory errorsLinus Torvalds2021/03/04 08:47 PM
                  memory errorsEtienne Lorrain2021/03/05 01:09 AM
                  memory errorsMichael S2021/03/05 04:06 AM
                    memory errorsLinus Torvalds2021/03/05 11:59 AM
                      memory errorsrwessel2021/03/05 12:32 PM
                        memory errorsrwessel2021/03/05 12:37 PM
                        memory errorszArchJon2021/03/06 08:39 PM
                      memory errorsGabriele Svelto2021/03/06 12:58 PM
                  memory errorsJörn Engel2021/03/05 10:12 AM
                Amiga recoverable RAM disk?Carson2021/03/05 03:03 AM
                  Thanks - TIL a cool Amiga feature (nt) (NT)John2021/03/05 12:51 PM
                    Another cool Amiga feature, datatypesCharles2021/03/06 12:01 AM
                      Another cool Amiga feature, datatypesJukka Larja2021/03/06 01:23 AM
                      Another cool Amiga feature, datatypesAnon2021/03/06 12:40 PM
                      Another cool Amiga feature, filesystemsMarcus2021/03/07 12:28 AM
  CPU & Memory bit flipszArchJon2021/03/04 06:39 AM
    CPU & Memory bit flipsdmcq2021/03/04 06:59 AM
      CPU & Memory bit flipsrwessel2021/03/04 12:27 PM
  speak of the devilRobert Williams2021/03/05 07:53 AM
    speak of the devildmcq2021/03/05 11:26 AM
      speak of the devilRobert Williams2021/03/05 03:15 PM
Reply to this Topic
Body: No Text
How do you spell avocado?