From: Alex <mailinglist@miromico.ch>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Init fails with segfault on AVR32
Date: Tue, 12 Feb 2008 12:19:56 +0100 [thread overview]
Message-ID: <47B180DC.1040107@miromico.ch> (raw)
In-Reply-To: <47AB02C4.4060202@miromico.ch>
Hi
While waiting for support from the mailinglist I tried a few more things
to get my atngw100 system running.
I tried to use init from (statically linked) busybox. This will suffer
the same problem but gives me a better clue where
the problem lies.
I found out that in a first step /bin/mount.util-linux is responsible
for the segfault. And this is due to the shared library
"ld-uClibc-0.9.28".
If I replace this library with ld-uClibc-0.9.29 from atmel's buildroot.
The segfault is gone!
There are rumours that some of you have OE running on ATNGW100 hardware.
So what can I make wrong?
Can someone send me his local.conf?
I update OE from time to time in the hope this will save my problems.
I use:
- bitbake version 1.18.11
- monotone 0.31
And I update OE using the following commands:
> mtn --db=/oe/OE.mtn pull monotone.openembedded.org org.openembedded.dev
> cd /oe/org.openembedded.dev && mtn update
Hope someone can help me. I'm trying for weeks to get this stuff
running....
Best regards,
Alex
> Hi
>
> I finally got minimal-image compiled in OE for AVR32 and the kernel can
> boot just to the point where it tries to load init.
>
> This will fail with a segfault. Last messages on boot log:
>
> VFS: Mounted root (jffs2
> filesystem).
> Freeing init memory: 68K (90000000 -
> 90011000)
> init[1]: segfault at 00000008 pc 2aaabbe8 sp 7fabbf40 ecr
> 24
> init has generated signal 11 but has no handler for
> it
> Kernel panic - not syncing: Attempted to kill init!
>
> I tried NFS boot and boot from flash which both produced the same
> result. I am using U-Boot 1.3.0.atmel.2 (from Atmel buildroot).
>
> Anyone an idea what could be wrong?
>
> To find the problem I did the following:
>
> I have a working rootfs (from AVR buildroot). Booting with OE-Kernel and
> Buildroot rootfs works. I can mount OE-rootfs via NFS and then I can
> execute programs such as sbin/init => this seems to be valid AVR32
> binaries.
>
> I copied init.sysvinit into my buildroot-rootfs. Now the system doesn't
> segfault anymore.
>
> Thanks for any hint
>
> Alex
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
next prev parent reply other threads:[~2008-02-12 11:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 13:08 Init fails with segfault on AVR32 Alex
2008-02-12 11:19 ` Alex [this message]
2008-02-12 11:43 ` Richard Purdie
2008-02-12 12:19 ` Alex
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=47B180DC.1040107@miromico.ch \
--to=mailinglist@miromico.ch \
--cc=openembedded-devel@lists.openembedded.org \
/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