Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Kuten <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot and Linux/ARM on AT91SAM9260
Date: Mon, 17 Dec 2007 22:33:56 +0200 (EET)	[thread overview]
Message-ID: <36574.127.0.0.1.1197923636.squirrel@localhost> (raw)
In-Reply-To: <85F68C4E-6290-4E64-875C-982B0E377695@oregonstate.edu>

>>
>> /sbin/init: can't Kernel panic - not syncing: Attempted to kill init!
>> load library 'libgcc_s.so.1'
>>
>> I checked that there is no libgcc_s.so.1 in rootfs image but I have
>> BR2_GCC_SHARED_LIBGCC=y
>> May be that is a cause why you not getting working rootfs.
>
>
> I'm not using a shared libgcc. It's just freezing after the freeing of
> the initrd memory about the time it should be booting up init. I guess
> my next step is to start throwing in some printk's to see exactly
> where it's dying.
>
> Of course, I can't get a 2.6.23 kernel to even boot at all, but that
> may be the same toolchain issues. My 2.6.21.6 kernel seems to be
> working ok -- that was built with my gcc 4.0.4 based toolchain, the
> only version I've been able to get successful boots from.
>
> Ryan
>
> --
> Ryan Ordway                           E-mail: rordway at oregonstate.edu
> Unix Systems Administrator               rordway at library.oregonstate.edu
> OSU Libraries, Corvallis, OR 97331    Office: Valley Library #4657
>
>

Ryan,

Yes, now I have the same symptoms
After buildroot rebuild libgcc_s.so.1 placed correctly (btw need to investigate why it was not placed there for the
first time). but when booting ramdisk is mounted and then freeze.
I suggest to try run your rootfs via qemu emulator, adjust only console device.

Folks who using ARM buildroot, please tell us your working configs!

Regards,
Ivan

  reply	other threads:[~2007-12-17 20:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29  5:06 [Buildroot] make on MAC OS X Fan Zhang
2007-11-29  6:38 ` [Buildroot] uClibc-nptl? Ryan Ordway
2007-11-29 13:30   ` Steven J. Hill
2007-11-30  7:00     ` Ryan Ordway
2007-12-12 20:17       ` [Buildroot] Buildroot and Linux/ARM on AT91SAM9260 Ryan Ordway
2007-12-17 16:14         ` Ivan Kuten
2007-12-17 19:38           ` Ryan Ordway
2007-12-17 20:33             ` Ivan Kuten [this message]
2007-12-17 22:49             ` Ivan Kuten
2007-12-17 22:53               ` Ryan Ordway
2007-12-17 23:24                 ` Ryan Ordway
2007-12-17 23:36                   ` Ivan Kuten
2007-12-18  0:24                     ` Ryan Ordway
2007-12-18 10:29                       ` Ivan Kuten
2007-12-27 12:42                         ` Ivan Kuten
2008-01-12 16:42                           ` Wayne Keenan
2008-01-12 16:43                             ` Wayne Keenan
2008-01-12 22:39                               ` Wayne Keenan

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=36574.127.0.0.1.1197923636.squirrel@localhost \
    --to=ivan.kuten@promwad.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox