From: Hollis Blanchard <hollis_blanchard@mentor.com>
To: buildroot@busybox.net
Subject: [Buildroot] [bug] bootwrapper runs before linking initrd
Date: Thu, 3 Sep 2015 15:00:49 -0700 [thread overview]
Message-ID: <55E8C311.6000404@mentor.com> (raw)
I have a BR config that includes the following:
BR2_LINUX_KERNEL=y
BR2_TARGET_ROOTFS_INITRAMFS=y
BR2_TARGET_BOOT_WRAPPER_AARCH64=y
I expect that Buildroot will:
1. build the kernel
2. build rootfs.cpio
3. link rootfs.cpio into the kernel as an initrd
4. run boot-wrapper-aarch64 on the kernel+initrd
When I do a build, however, I can clearly see that step 4 happens before
step 3. In fact, "Rebuilding kernel with initramfs" is the very last
step of the build. "boot-wrapper-aarch64 Installing to images directory"
happened much earlier.
(Side note: the error is far more catastrophic than a simple "couldn't
find root filesystem" panic; it looks like big chunks of the kernel's
data section are zeroed, so that kernel messages aren't even logged, to
say nothing of no serial output. I don't know why this is.)
A workaround is to remember to manually "make
boot-wrapper-aarch64-rebuild" after a regular build has completed.
What's the real solution? Thanks!
--
Hollis Blanchard
Mentor Graphics Emulation Division
next reply other threads:[~2015-09-03 22:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 22:00 Hollis Blanchard [this message]
2015-09-04 8:54 ` [Buildroot] [bug] bootwrapper runs before linking initrd Thomas Petazzoni
2015-09-04 9:51 ` Peter Korsgaard
2015-09-04 10:39 ` Thomas Petazzoni
2015-09-04 19:52 ` Arnout Vandecappelle
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=55E8C311.6000404@mentor.com \
--to=hollis_blanchard@mentor.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