From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11866] iniramfs file system fails to boot using Grub on EFI x86_64
Date: Thu, 05 Mar 2020 08:02:41 +0000 [thread overview]
Message-ID: <bug-11866-163-EcE820QAZK@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11866-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11866
Timo Ketola <timo.ketola@exertus.fi> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |timo.ketola at exertus.fi
--- Comment #4 from Timo Ketola <timo.ketola@exertus.fi> ---
This sounds very much like what I observed too. When I try to boot an ARM
system with U-Boot and with 'silent' flag set, /init fails, kernel panics and
the local display is left with a cursor alone (I watch the kernel messages from
the serial line). U-Boot's 'silent' flag makes it to adjust kernel command line
with 'console=<empty>'.
Here is a proposed patch:
https://patchwork.ozlabs.org/patch/1166017
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-03-05 8:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 21:55 [Buildroot] [Bug 11866] New: iniramfs file system fails to boot using Grub on EFI x86_64 bugzilla at busybox.net
2019-05-10 22:00 ` [Buildroot] [Bug 11866] " bugzilla at busybox.net
2019-05-11 15:50 ` bugzilla at busybox.net
2019-05-13 13:11 ` bugzilla at busybox.net
2020-03-05 8:02 ` bugzilla at busybox.net [this message]
2020-04-24 6:33 ` bugzilla at busybox.net
2020-04-25 1:55 ` bugzilla at busybox.net
2020-04-25 7:40 ` bugzilla at busybox.net
2020-04-25 12:10 ` bugzilla at busybox.net
2020-04-27 5:27 ` bugzilla at busybox.net
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=bug-11866-163-EcE820QAZK@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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