From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] kernel panic on VIA C3 Samuel2
Date: Mon, 27 May 2013 13:24:55 +0200 [thread overview]
Message-ID: <20130527132455.43298317@skate> (raw)
In-Reply-To: <51A3368F.4010607@gmail.com>
Hello,
On Mon, 27 May 2013 12:33:51 +0200, area234 at gmail.com wrote:
> a root fs built with buildroot-2013.05-rc2 and defconfig BR2_x86_c3=y
> BR2_TOOLCHAIN_EXTERNAL=y, terminates booting with a kernel panic at init
> start, when run on a VIA EPIA PD board with Eden 600+256MB.
> The same root fs works fine on qemu and on a netbook (atom n570+1GB).
> This happens with different types of linux kernels and different boot
> loaders.
The base library configuration for the CodeSourcery x86 toolchain is
Intel Pentium 4. I am not sure the VIA C3 implements the Pentium 4
instruction set, I am not very familiar with those x86 clones.
> The problem disappears changing the busybox of buildroot with a
> statically linked one.
Hum, this is interesting. Maybe when it's statically linked you don't
hit the problematic code paths?
Can you paste the complete panic message, so we can have a look?
> What is wrong with the VIA board? Any suggestion is appreciated, thank
> you in advance.
Probably nothing is wrong with the VIA board, most likely with the
toolchain configuration.
Can you try BR2_x86_c3=y, dynamic linking, with the Buildroot internal
toolchain?
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-05-27 11:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 10:33 [Buildroot] kernel panic on VIA C3 Samuel2 area234 at gmail.com
2013-05-27 11:24 ` Thomas Petazzoni [this message]
2013-05-28 20:51 ` Area234
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=20130527132455.43298317@skate \
--to=thomas.petazzoni@free-electrons.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