From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: AVR32 init segfault: Any resolution?
Date: Fri, 07 Mar 2008 18:21:11 +0100 [thread overview]
Message-ID: <fqrti8$nlt$2@ger.gmane.org> (raw)
In-Reply-To: <200803071113.40387.geoffrey@pager.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Geoffrey Wossum schreef:
| Hi all,
|
| With Richard's help on the toolchain and a patch to the
| conf/machine/at32stk1000.conf (submitted via Bugzilla), I can now boot
the
| kernel on my AVR32 based AT32STK1000.
|
| However, init segfaults. Here's the last boot of the boot activity
before the
| segfault:
|
| Waiting 1sec before mounting root device...
| mmc0: new SD card at address b368
| mmcblk0: mmc0:b368 5 249856KiB
| mmcblk0: p1
| VFS: Mounted root (ext2 filesystem).
| Freeing init memory: 64K (90000000 - 90010000)
| init[1]: segfault at 00000008 pc 2aaabbe8 sp 7ffd0f20 ecr 24
| init has generated signal 11 but has no handler for it
| Kernel panic - not syncing: Attempted to kill init!
|
|
| Alex reported the same bug about a month ago to this mailing list. I
haven't
| seen any resolution to it, though. Is there a resolution to this bug yet?
You should be able to use busybox as init nowadays, or add add uclibc
0.9.29 for avr32 :)
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFH0XmHMkyGM64RGpERAoyPAKC0SkEN9V5EzmhMVt/tPu86JrhRBACfWR30
5V/VdjOq44jCE2osfsGlMvg=
=S29Z
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-03-07 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-07 17:13 AVR32 init segfault: Any resolution? Geoffrey Wossum
2008-03-07 17:21 ` Koen Kooi [this message]
2008-03-07 20:44 ` Robert Wörle
2008-03-10 14:15 ` Geoffrey Wossum
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='fqrti8$nlt$2@ger.gmane.org' \
--to=koen@dominion.kabel.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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