Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christian SCHWARZ <christian.schwarz@st.com>
To: buildroot@busybox.net
Subject: [Buildroot] zImage corruption
Date: Fri, 21 Mar 2008 09:05:25 +0100	[thread overview]
Message-ID: <47E36C45.5060507@st.com> (raw)
In-Reply-To: <47E2B60B.70106@carallon.com>

Hey Will,

I have similar troubles related to the rootfs created by buildroot, also 
on a custom ARM11 target. In my case, the Linux kernel is not able to 
start init (errors either -2, -8 or -14). In my case I had to replace 
the bin/ and etc/ directories with ones created outside in an (older) 
busybox directory.
The image sizes created by a "make" in buildroot vary greatly, sometimes 
there are 3 - 4 MB of space left in the image, sometimes only a few 
hundred kB.

cheers,
Christian


Will Wagner wrote:
> Hi All,
> 
> I have been happily using buildroot for a while (thanks all its a great 
> tool).
> 
> However I have started seeing a problem where the linux zImage being 
> built gets corrupted and does not boot.
> 
> I am building a custom arm device using initramfs. If I checkout from 
> clean and build it all works great and get a working zImage that is 
> ~7.5MB. However if I then run make again I get a zImage file that is 
> ~6.5MB and does not boot.
> 
> I have compared the root filesystems before and after calling make again 
> and can see no difference. I have also tried doing a dirclean on the 
> kernel and rebuilding and this still leads to a corrupt zImage.
> 
> Has anyone seen this before? Can anyone suggest what could be going on?
> 
> I can supply more config info if needed.
> 
> Thanks,
> Will

      reply	other threads:[~2008-03-21  8:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-20 19:07 [Buildroot] zImage corruption Will Wagner
2008-03-21  8:05 ` Christian SCHWARZ [this message]

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=47E36C45.5060507@st.com \
    --to=christian.schwarz@st.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