Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: buildroot@busybox.net
Subject: [Buildroot] linux .config : override: reassigning tosymbolAEABI
Date: Wed, 29 Jul 2009 19:30:00 +0200	[thread overview]
Message-ID: <20090729173000.GT19257@buzzloop.caiaq.de> (raw)
In-Reply-To: <F81DF98CADE6064F81A746D7C8323593782CC1@fr-ex009.groupinfra.com>

On Wed, Jul 29, 2009 at 06:07:33PM +0200, Courousse, Damien wrote:
> > Ok, fine. You're digging at the wrong end then :) Try setting
> > CONFIG_DEBUG_USER in your kernel config and pass user_debug=255 on
> > startup. That will output more details when user space binaries crash.
> > 
> > Daniel
> > 
> [Damien Courouss?] 
> The user_debug option did not change anything :(

It only does if you set CONFIG_DEBUG_USER in your kernel config. You
will need to change it in the config you point your BR2 to.

> And if I add init=/bin/sh at the end of the kernel command line (using busybox), I get this : 
> Kernel command line: root=/dev/nfs rw nfsroot=10.84.34.52:/mnt/fractal/buildroot/buildroot-2009.05/project_build_arm/logica_demo/root ip=10.84.34.8:10.84.34.52:10.84.34.1:255.255.255.192:debian_test:eth0:off user_debug=255 init=/bin/sh
> 
> Looking up port of RPC 100003/2 on 10.84.34.52
> Looking up port of RPC 100005/1 on 10.84.34.52
> VFS: Mounted root (nfs filesystem).
> Freeing init memory: 116K
> Kernel panic - not syncing: Attempted to kill init!

With CONFIG_DEBUG_USER=y, you should see more useful output at this
stage.

> ... and then I have compiled the kernel with initramfs. There I get something working: 
> IP-Config: Complete:
>      device=eth0, addr=10.84.34.8, mask=255.255.255.192, gw=10.84.34.1,
>      host=debian_test, domain=, nis-domain=(none),
>      bootserver=10.84.34.52, rootserver=10.84.34.52, rootpath=
> Freeing init memory: 808K
> Initializing random number generator... done.
> Starting network...
> ifup: interface lo already configured
> Starting NFS statd: touch: /var/lock/subsys/nfslock: No such file or directory
> done
> Starting NFS services: done
> Starting NFS daemon: done
> Starting NFS mountd: Cannot register service: RPC: Unable to receive; errno = Connection refused
> done
> touch: /var/lock/subsys/nfs: No such file or directory
> 
> Welcome to Buildroot
> login: root
> # ls
> # ls /
> bin      dev      init     mnt      root     tmp
> boot     etc      lib      opt      sbin     usr
> config   home     linuxrc  proc     sys      var
> # mount
> rootfs on / type rootfs (rw)
> proc on /proc type proc (rw)
> devpts on /dev/pts type devpts (rw,gid=5,mode=620)
> tmpfs on /tmp type tmpfs (rw)
> sysfs on /sys type sysfs (rw)
> 
> 
> 
> But as you can see nfs root is not mounted (this might be because of a remount of / in inittab), whereas without initramfs, the nfs root is correctly mounted.
> 
> What puzzles me is that I though it would be possible to use a nfs root without initramfs. I will continue digging into this...

It is possible, of course. Once you have more debug output, you might
see where the problem is.

Daniel

  reply	other threads:[~2009-07-29 17:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-29 12:59 [Buildroot] linux .config : override: reassigning to symbol AEABI Courousse, Damien
2009-07-29 13:25 ` Daniel Mack
2009-07-29 13:34   ` [Buildroot] linux .config : override: reassigning to symbolAEABI Courousse, Damien
     [not found]   ` <F81DF98CADE6064F81A746D7C8323593782CAC@fr-ex009.groupinfra.com>
2009-07-29 13:42     ` Daniel Mack
2009-07-29 13:59       ` [Buildroot] linux .config : override: reassigning tosymbolAEABI Courousse, Damien
2009-07-29 14:26         ` Daniel Mack
2009-07-29 16:07           ` Courousse, Damien
2009-07-29 17:30             ` Daniel Mack [this message]
2009-07-31 10:20             ` Thomas Petazzoni
2009-07-31 15:57               ` Courousse, Damien
2009-07-29 18:59 ` [Buildroot] linux .config : override: reassigning to symbol AEABI Peter Korsgaard
2009-07-31  9:33   ` Courousse, Damien

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=20090729173000.GT19257@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