From: Daniel Mack <daniel@caiaq.de>
To: buildroot@busybox.net
Subject: [Buildroot] Undefined instruction on PXA270
Date: Sun, 2 Dec 2007 23:31:10 +0100 [thread overview]
Message-ID: <20071202223110.GA22365@buzzloop.caiaq.de> (raw)
In-Reply-To: <474556AE.8060209@studiofuga.com>
Hi,
On Thu, Nov 22, 2007 at 11:15:10AM +0100, ing. Federico Fuga wrote:
> > we've been trying to hunt a bug of our buildroot based rootfs here
> > without success. The platform is based on a PXA270 (Compulab's EM-X270)
> > and buildroot is a recent svn checkout.
> >
> > Out kernel 2.6.23 was successfully built with the toolchain set up by
> > buildroot and can mount root filesystems provided by the vendor of the
> > module. However, whenever trying to nfs-mount a rootfs built by BR2, we
> > end up having messages like this:
> >
> I am working on the same platform and board, emx270 from compulab, and
> never found that problem. The only problem I had was with the
> monotonic_syscall option you told, but never happened again.
Do you have the DOPIC config option set in uClibc?
I debugged around for a while after the same thing happend again on a
completely different build machine with another type of embedded system.
All they have in common is that they're both based on a PXA270. It turned
out that busybox actually dies on instructions built with (PLT) ending
up with the messages I described. With the option unset, everything is
just fine.
However, this option is set by default so I really wonder why nobody
else runs into this issue than me?
Maybe anybody with more in-depth knowledge about what actually happens
with PIC-only in conjunction with (PLT) assembly could enlighten me, I'd
appreciate that :)
Thanks,
Daniel
next prev parent reply other threads:[~2007-12-02 22:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 23:35 [Buildroot] Undefined instruction on PXA270 Daniel Mack
2007-11-22 9:03 ` Ivan Kuten
2007-11-22 10:15 ` ing. Federico Fuga
2007-12-02 22:31 ` Daniel Mack [this message]
2007-12-04 18:53 ` ing. Federico Fuga
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=20071202223110.GA22365@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--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