From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] random segmentation fault during built
Date: Mon, 18 Jan 2021 20:13:12 +0100 [thread overview]
Message-ID: <20210118201312.47e120d8@gmx.net> (raw)
In-Reply-To: <CAEUhbmWy918HoQtKzGwadJTRPqCenGG+j8K1jQ0DPhckhmKUSw@mail.gmail.com>
Hello Bin,
On Sun, 17 Jan 2021 23:30:51 +0800, Bin Meng <bmeng.cn@gmail.com> wrote:
> Hi Peter,
>
> On Tue, Jan 12, 2021 at 3:30 AM Peter Seiderer <ps.report@gmx.net> wrote:
> >
> > Hello Bin,
> >
> > On Mon, 11 Jan 2021 09:11:48 +0800, Bin Meng <bmeng.cn@gmail.com> wrote:
> >
> > > Hi Peter,
> > >
> > > On Mon, Jan 11, 2021 at 12:04 AM Peter Seiderer <ps.report@gmx.net> wrote:
> > > >
> > > > Hello Bin,
> > > >
> > > > On Sun, 10 Jan 2021 21:57:45 +0800, Bin Meng <bmeng.cn@gmail.com> wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I see a random segmentation fault during the build of buildroot. For example,
> > > > >
> > > > > Makefile:13408: recipe for target 'install-pylibmountexecPYTHON' failed
> > > > > make[4]: *** [install-pylibmountexecPYTHON] Segmentation fault (core dumped)
> > > > > make[4]: *** Waiting for unfinished jobs....
> > > > >
> > > > > Type "make" for the 2nd time with nothing changed, or rarely a 3rd
> > > > > time, get a PASS build.
> > > > >
> > > > > This was observed by builds on Ubuntu 16.04 and Ubuntu 20.04 hosts.
> > > > > Any ideas of what could be wrong?
> > > >
> > > > In case the errors are at random packages/locations (and succeed on iteration)
> > > > check your hardware and/or memory, see e.g. [1]...
> > > >
> > > > Early versions of the AMD Ryzen CPU had heavy-load segfault bug, see [2]...
> > > >
> > > > Regards,
> > > > Peter
> > > >
> > > > [1] https://tldp.org/FAQ/sig11/html/index.html
> > > > [2] https://techreport.com/news/32459/amd-ships-revised-ryzen-cpus-with-a-compile-bug-fix/
> > >
> > > Thank you. I checked the above 2 links and suspect it's not related.
> > >
> > > The issue happens on one Intel Xeon CPU with a Ubuntu 16.04 and one
> > > Intel CORE i9 with a Ubuntu 20.04. The segmentation fault seems to
> > > happen randomly during package "make install" phase.
> >
> > Back to the first question: random packages/locations or always at the same (or
> > similar) location? Always some python (related) package?
>
> Looks it's random, not always some Python packages. For example, I saw
> this today:
>
> make[3]: *** [Makefile:1826: install-pkgconfDATA] Segmentation fault
> make[3]: *** Waiting for unfinished jobs....
>
> >
> > Which buildroot version? Mind to share your .config file?
>
> The current buildroot HEAD with commit
> 6d4f1324d4a4a23938e40cc12a033a3a264b4ec1, plus my patch:
> http://patchwork.ozlabs.org/project/buildroot/patch/1610355672-3008-3-git-send-email-bmeng.cn at gmail.com/
>
> .config file attached
Did test with your .config five times in a row, no problems here (openSUSE
Tumbleweed on AMD Ryzen 7 1800X Eight-Core Processor)..., so it seems to be
something specific to your environment...
Can you send the output of 'ls -ltr build | tail' after failure (to give some
hint which package fails) and a little bit more surroundings of the failure
output?
Regards,
Peter
>
> >
> > Mind to enable core-dump ('ulimit -c unlimited') and take a look at the core
> > file?
> >
>
> Sorry I did not enable core dump. I will have to turn it on now.
>
> Regards,
> Bin
next prev parent reply other threads:[~2021-01-18 19:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 13:57 [Buildroot] random segmentation fault during built Bin Meng
2021-01-10 16:04 ` Peter Seiderer
2021-01-11 1:11 ` Bin Meng
2021-01-11 19:30 ` Peter Seiderer
2021-01-17 15:30 ` Bin Meng
2021-01-18 19:13 ` Peter Seiderer [this message]
[not found] ` <CAEUhbmVC0p2UBGEDg_k9LW-NBfWVdurzynDkZjTL76jA6iZ-3g@mail.gmail.com>
2021-01-18 19:22 ` Peter Seiderer
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=20210118201312.47e120d8@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/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