Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 13 May 2019 13:11:35 +0000	[thread overview]
Message-ID: <bug-11866-163-OM5LoclU0F@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11866-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=11866

--- Comment #3 from Pete Morici <pmorici@dev295.com> ---
Looked into this more and the source of the issue is setting the console
argument to certain values causes the boot process to lock up but only when the
initramfs file system is used.  I have been setting the console value to null
which causes the problem and when I changed it back to tty1 I made a typo and
wrote /dev/tty1 which also causes the problem.  None of these values cause a
boot hang when used with a file system other than initramfs.

This might have something to do with the /init script installed as part of the
cpio fs option that initramfs depends on but since there is no output I can't
tell what the exact problem is.

 #!/bin/sh
 # devtmpfs does not get automounted for initramfs
 /bin/mount -t devtmpfs devtmpfs /dev
 exec 0</dev/console
 exec 1>/dev/console
 exec 2>/dev/console
 exec /sbin/init "$@"

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2019-05-13 13:11 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 [this message]
2020-03-05  8:02 ` bugzilla at busybox.net
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-OM5LoclU0F@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