Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [Buildroot 2020.02.1] Problems with x86_64-jaguar buildroot-toolchain-built kernel
Date: Mon, 27 Apr 2020 21:35:52 +0200	[thread overview]
Message-ID: <20200427213552.57ea2ac7@windsurf.home> (raw)
In-Reply-To: <BL0PR10MB286624EC6E8417F3DA28E257FFAF0@BL0PR10MB2866.namprd10.prod.outlook.com>

Hello,

On Mon, 27 Apr 2020 06:49:35 +0000
"Olivier, Alain [COMRES/EUR/BLU]" <Alain.Olivier@Emerson.com> wrote:

> I am experiencing the following problem when building a basic environment for a board running on a AMD GX-222GC (should be Jaguar subarch).
> The default external toolchain is amd-2016.11-19 from CodeBench. Kernel built with that toolchain boots correctly.
> Instead, if I build the same kernel, same configuration, with the toolchain built by buildroot, the kernel doen not boot! Not even a kernel panic, machine just resets.

I assume you are the person who also asked the same question on StackOverflow:

  https://stackoverflow.com/questions/61457023/why-is-my-kernel-resetting-my-machine-immediately

The critical bit of information missing in your e-mail, but that you
gave as a reply on stack overflow is that you are testing on 4.4.57.

However, there was an issue in Linux where using a toolchain that uses
binutils >= 2.31 would generate a non-bootable kernel. This was fixed
upstream, and then backported to the 4.4.x stable branch in commit:

  https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=073bb7ddd35ca8f17a170258dacbe384935a43c8

This commit is available in the 4.4.x branch as of 4.4.124.

How do I immediately know that? I debugged exactly this issue last
week, where a Linux 4.4.39 built with Buildroot 2019.11 was booting
fine, but not built with Buildroot 2020.02 :-)

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2020-04-27 19:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BL0PR10MB2866A594CDE0E5FD74BC767BFFAE0@BL0PR10MB2866.namprd10.prod.outlook.com>
2020-04-27  6:49 ` [Buildroot] [Buildroot 2020.02.1] Problems with x86_64-jaguar buildroot-toolchain-built kernel Olivier, Alain
2020-04-27 19:35   ` Thomas Petazzoni [this message]

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=20200427213552.57ea2ac7@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --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