From: J. L. Sloan <jsloan@diag.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot for AT91RM9200-EK?
Date: Tue, 29 Jul 2008 17:28:58 -0600 [thread overview]
Message-ID: <00e101c8f1d2$e4df1330$ae9d3990$@com> (raw)
In-Reply-To: <00c101c8f1c9$ad9f5500$08ddff00$@com>
Just rebuilt everything from scratch (starting from svn co) for EABI (and
verified with readelf -h against both vmlinux and busybox for "Version4
EABI") with exactly the same result. The kernel is build with EABI and with
OABI compat. Padzero/clear_user goes south trying to load /init.
(gdb) where
#0 0xc00f920c in __clear_user ()
#1 0xc00aa9ec in padzero (elf_bss=665549) at include/asm/uaccess.h:420
#2 0xc00ab8a8 in load_elf_binary (bprm=0xc1c25b00, regs=0xc1c19f00)
at fs/binfmt_elf.c:896
#3 0xc0082700 in search_binary_handler (bprm=0xc1c25b00, regs=0xc1c19f00)
at fs/exec.c:1235
#4 0xc00837e4 in do_execve (filename=dwarf2_read_address: Corrupted DWARF
expression.
) at fs/exec.c:1339
#5 0xc0025928 in kernel_execve (filename=0xc022fea0 "/init",
argv=0xc039a1f4,
envp=0xc039a168) at arch/arm/kernel/sys_arm.c:288
#6 0xc0022278 in run_init_process (
init_filename=0xa27cd <Address 0xa27cd out of bounds>) at
init/main.c:763
#7 0xc00222e4 in init_post () at init/main.c:784
#8 0xc0008900 in kernel_init (unused=<value optimized out>) at
init/main.c:856
#9 0xc0034928 in sys_waitid (which=<value optimized out>, upid=2099,
infop=0x0, options=0, ru=0x0) at kernel/exit.c:1613 Backtrace stopped:
previous frame inner to this frame (corrupt stack?)
(gdb)
Again, thanks for any pointers (so to speak).
--
<http://www.diag.com/navigation/metadata/jsloan.html> John Sloan
Consulting Technologist
<mailto:jsloan@diag.com> jsloan at diag.com <http://www.diag.com/>
Digital Aggregates Corporation
+1 303 489 5178 (Mobile)
<http://www.google.com/maps?f=q&hl=en&geocode=&q=Arvada+Colorado&ie=UTF8&z=1
1&iwloc=addr&om=1> Arvada Colorado 80001-0587 USA
+1 303 940 9064 (Office) <http://www.diag.com/> www.diag.com
From: buildroot-bounces@uclibc.org [mailto:buildroot-bounces at uclibc.org] On
Behalf Of J. L. Sloan
Sent: Tuesday, July 29, 2008 4:23 PM
To: buildroot at uclibc.org
Subject: [Buildroot] Buildroot for AT91RM9200-EK?
Just to make sure I'm not spinning my wheels, has anyone gotten Buildroot
(22987 is what I'm using right now) working for the Atmel AT91RM9200-EK
board (Atmel AT91 ARM9)?
I've got the 2.6.25.10 kernel booting okay, but as soon as it goes to run
/init (really, busybox) wackiness ensues. It traps in clear_user trying to
zero out part of the loaded ELF. GDB+BDI suggests that the address passed
from padzero to clear_user is bogus, but I'm not sure I'm trusting what it's
telling me (some of the other stuff on the stack trace looks questionable).
readelf-h suggests AFAIK that everything is built as OABI. (I may restart
from the beginning with EABI, but I'm not sure how U-Boot on the EK was
built, and I'm not sure if that really matters. But U-Boot does "call" the
kernel to start it.)
Thanks for any insight.
--
John Sloan <http://www.diag.com/navigation/metadata/jsloan.html>
Consulting Technologist
jsloan at diag.com Digital Aggregates Corporation
<http://www.diag.com/>
+1 303 489 5178 (Mobile) Arvada
<http://www.google.com/maps?f=q&hl=en&geocode=&q=Arvada+Colorado&ie=UTF8&z=1
1&iwloc=addr&om=1> Colorado 80001-0587 USA
+1 303 940 9064 (Office) www.diag.com <http://www.diag.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20080729/5369fb54/attachment-0001.htm
next prev parent reply other threads:[~2008-07-29 23:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 22:23 [Buildroot] Buildroot for AT91RM9200-EK? J. L. Sloan
2008-07-29 23:28 ` J. L. Sloan [this message]
2008-07-30 14:07 ` J. L. Sloan
2008-07-30 20:19 ` J. L. Sloan
2008-07-30 22:39 ` J. L. Sloan
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='00e101c8f1d2$e4df1330$ae9d3990$@com' \
--to=jsloan@diag.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 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.