Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] bifferboard: new board
Date: Sun, 18 Mar 2012 18:13:30 +0100	[thread overview]
Message-ID: <201203181813.30601.arnout@mind.be> (raw)
In-Reply-To: <4F660977.4040806@yahoo.co.uk>

On Sunday 18 March 2012 17:12:39 bifferos wrote:
> On 03/18/2012 01:50 PM, Arnout Vandecappelle wrote:
> > On Monday 12 March 2012 02:23:35 bifferos wrote:
> >> Write protecting the kernel text: 1048k
> >> Write protecting the kernel read-only data: 164k
> >> init[1]: segfault at 0 ip   (null) sp bf95bf40 error 4 in
> >> busybox[8048000+7c000]
> >   Since this segmentation fault is in init, it will be tough to debug.
> > Judging from the address, it in fact happens even before init is
> > started.  Is it possible that there isn't enough RAM to run busybox?
> >
> 
> I have a hard time believing there is not enough RAM  I have copied the 
> generated busybox onto the working system and run it there, and it 
> executes OK, so the same system can execute two instances of the busybox 
> binary (from two different places on rootfs), and they both run OK.

 It was just a guess based on the fact that it segfaults before it starts.


> I learnt something new the other day - an initramfs compiled into the 
> kernel can be compressed, however the kernel compression works ontop of 
> that.  So if you specify CONFIG_INITRAMFS_SOURCE it is pointless to 
> specify initramfs compression other than 'None'

 Hm, good point, we should probably change our initramfs setup to disable
compression if the kernel image itself is compressed.

[snip]

> Now I'm wondering if there is something that has been activated in 
> busybox, some feature, which requires kernel support, and (since my 
> kernel is minimal) perhaps it doesn't have it, and perhaps init doesn't 
> handle the lack of that support gracefully and crashes.  Nothing comes 
> to mind though.

 Since init segfaults before any instruction is executed, it seems 
unlikely.  The binary formats seem OK as well.  You could try to
enable CONFIG_BINFMT_AOUT.

 Hang on, I realize something.  CONFIG_BINFMT_MISC wasn't enabled in
the config I sent, so /init can't be executed (/init is a shell script
that mounts devtmpfs).  Can you enable BINFMT_MISC and try again?

 Regards,
 Arnout


-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2012-03-18 17:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-01  0:52 [Buildroot] Kernel and buildroot in 1MB bifferos
2012-03-01  7:50 ` Thomas Petazzoni
2012-03-01 11:13   ` bifferos
2012-03-03 15:29     ` Arnout Vandecappelle
2012-03-03 15:35       ` [Buildroot] [PATCH] bifferboard: new board Arnout Vandecappelle
2012-03-05  9:49         ` Thomas Petazzoni
2012-03-06  7:00           ` Arnout Vandecappelle
2012-03-11 10:58           ` [Buildroot] [PATCH v2] " Arnout Vandecappelle
2012-03-12 14:46             ` bifferos
2012-03-12  1:23         ` [Buildroot] [PATCH] " bifferos
2012-03-16  1:58           ` [Buildroot] Debugging /sbin/init startup issues bifferos
2012-03-17  4:03             ` Charles Krinke
2012-03-17 14:10               ` bifferos
2012-03-18 13:50           ` [Buildroot] [PATCH] bifferboard: new board Arnout Vandecappelle
2012-03-18 16:12             ` bifferos
2012-03-18 17:13               ` Arnout Vandecappelle [this message]
2012-03-18 19:51                 ` Alexandre Pereira da Silva
2012-03-18 20:54                 ` bifferos
2012-03-18 21:40                   ` Arnout Vandecappelle
2012-03-19 12:36                     ` bifferos
     [not found]       ` <4F525794.5010406@yahoo.co.uk>
2012-03-03 17:00         ` [Buildroot] Kernel and buildroot in 1MB Arnout Vandecappelle
2012-03-01 12:18 ` Peter Korsgaard

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=201203181813.30601.arnout@mind.be \
    --to=arnout@mind.be \
    --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