All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Yoann Congal <yoann.congal@smile.fr>,
	davidskeck@fastmail.com, yocto@lists.yoctoproject.org
Subject: Re: [yocto] Importance of ECC RAM on the build computer
Date: Fri, 17 Feb 2023 15:14:42 +0100	[thread overview]
Message-ID: <Y++L0sgJGNkyElAq@mail.local> (raw)
In-Reply-To: <CANNYZj_gGvuJQhPD26C=v9ywja6UwYDa6O=b5CJkdHkJh_bKMQ@mail.gmail.com>

On 17/02/2023 10:41:37+0100, Alexander Kanavin wrote:
> On the other hand, I'm yet to hear an actual case of a broken build
> due to non-ECC. It's not impossible, but it seems exceedingly rare.
> You're far more likely to spend 100x as much time on logical errors or
> out-of-resources problems.

It actually happened in one of our build, were we had a bitflip in the
final binary which was then not working as expected.

We also had multiple cases of headers/source file corruption after the
tarball is extracted but usually those are either caught by the compiler
or don't matter at all.

> 
> Alex
> 
> On Fri, 17 Feb 2023 at 09:31, Yoann Congal <yoann.congal@smile.fr> wrote:
> >
> > Hi!
> >
> > Le ven. 17 f�vr. 2023 � 06:08, <davidskeck@fastmail.com> a �crit :
> >>
> >> Is there generally suggested advice regarding the importance of ECC on the build computer? I'm very new to Yocto so I'm not sure if there is a chance the final build image could experience some corruption due to flipped bits in RAM or if I'm totally overthinking this.
> >
> >
> > Last time I checked. The ECC vs non-ECC price difference was not worth the time you may spend in case of a RAM bitflip.
> > Here, we put ECC RAM in our build systems and I guess it's quite the industry standard.
> >
> >> It is also possible that Yocto does some kind of CRC checking of its own that makes this a non-issue. Any guidance would be appreciated. Thank you!
> >
> >
> > Yocto does source integrity checks (the stuff it downloads from the internet) but it can't do much more after that.
> >
> > I've yet to debug a RAM bitflip but I guess it may trigger any kind of weird behavior which may be hard to debug and time consuming.
> >
> > My advice is : keep your time and sanity, use ECC RAM.
> >
> > Regards,
> > --
> > Yoann Congal
> > Smile ECS - Expert technique
> >
> > 
> >

> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#59239): https://lists.yoctoproject.org/g/yocto/message/59239
> Mute This Topic: https://lists.yoctoproject.org/mt/97022997/3617179
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [alexandre.belloni@bootlin.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 


-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2023-02-17 14:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17  5:08 Importance of ECC RAM on the build computer davidskeck
2023-02-17  8:31 ` [yocto] " Yoann CONGAL
2023-02-17  9:41   ` Alexander Kanavin
2023-02-17 14:14     ` Alexandre Belloni [this message]
2023-02-17 15:41       ` Leon Woestenberg

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=Y++L0sgJGNkyElAq@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=alex.kanavin@gmail.com \
    --cc=davidskeck@fastmail.com \
    --cc=yoann.congal@smile.fr \
    --cc=yocto@lists.yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.