Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] issue with Linux ARM start_kernel
Date: Fri, 07 Apr 2017 21:27:46 +0200	[thread overview]
Message-ID: <87inmgrpal.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CABWt4evkoeQ6deMoLCWSuaZaxKzuR4=_BLEp8g4MKh1KELzjrQ@mail.gmail.com> (Robert Smigielski's message of "Fri, 7 Apr 2017 10:49:16 -0400")

>>>>> "Robert" == Robert Smigielski <ptdropper@gmail.com> writes:

 > Hi everyone,
 > I am a long time Linux device driver writer (about 16 years) and now for 3
 > years creating BSP's using Buildroot.

 > When I build using "make clean" then "make" - without NetworkManager in the
 > .config the board boots and runs for days. Great.
 > When I build using "make clean", reconfigure Buildroot to enable my custom
 > added NetworkManager=y, the build succeeds, the image is loaded on the
 > board, and I get the problem:

 > "Uncompressing Linux... done, booting the kernel."

From this and the description about loading uImage with a bdi, I take it
that your filesystem is an initramfs embedded in the uImage?

It would be interesting to check if your problem relates to the uImage
growing to a specific size (E.G. add some data files to the working
build instead).

What address are you loading the uImage to? It sounds like the
decompressor perhaps ends up overwriting itself.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2017-04-07 19:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-07 14:49 [Buildroot] issue with Linux ARM start_kernel Robert Smigielski
2017-04-07 19:27 ` Peter Korsgaard [this message]
2017-04-07 19:42   ` Robert Smigielski
2017-04-07 20:02     ` Robert Smigielski
2017-04-07 21:32       ` 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=87inmgrpal.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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