All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: "Walter, Stefan" <stefan.walter@iml.fraunhofer.de>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] Boot process stuck at "GRUB loading.." since 2021.02.1
Date: Thu, 7 Oct 2021 23:50:19 +0200	[thread overview]
Message-ID: <20211007235019.51751a53@gmx.net> (raw)
In-Reply-To: <DB6P194MB00220117F126EF57A84FB509B7B19@DB6P194MB0022.EURP194.PROD.OUTLOOK.COM>

Hello Walter,

On Thu, 7 Oct 2021 20:36:07 +0000, "Walter, Stefan" <stefan.walter@iml.fraunhofer.de> wrote:

> Hi,
>
> the following used to work until Buildroot 2021.02, i.e. the resulting image booted normally. Ever since Buildroot 2021.02.1 and up until 2021.02.5, the resulting image does not boot any more - the boot process either gets stuck right after displaying "GRUB loading..", or it reboots at that point, leading to an infinite boot loop.
>
> What I'm doing:
>
> 1. Run Buildroot to create a root partition image (my_defconfig attached).
> 2. Create a GRUB image like this (grub_early.cfg attached):
>
> /path/to/buildroot-sdk/host/bin/grub-mkimage --config=grub_early.cfg --directory=/path/to/buildroot-sdk/host/lib/grub/i386-pc -o ./genimage_input_tmp/grub_core.img --format=i386-pc --prefix==/boot/grub biosdisk part_msdos ext2 normal linux configfile
>
> 3. Create a home partition image like this:
>
> MKE2FS_CONFIG=/path/to/buildroot-sdk/host/etc/mke2fs.conf /path/to/buildroot-sdk/host/sbin/mke2fs -d home_partition_prep/home -j -L home -t ext3 -U random -b 4096 ./genimage_input_tmp/home.ext3 25M
>
> 4. Create a disk image like this (genimage.cfg attached):
>
> /path/to/buildroot-sdk/host/bin/genimage --loglevel=1 --config=genimage.cfg --inputpath=./genimage_input_tmp --outputpath=images --rootpath=home_partition_prep --tmppath=./genimage_tmp --tune2fs=/path/to/buildroot-sdk/host/usr/sbin/tune2fs --e2fsck=/path/to/buildroot-sdk/host/usr/sbin/e2fsck
>
> Does anyone have any idea what's going wrong here since 2021.02.1?

Only known issue was 'Bug 13586 - grub failure with BR2_OPTIMIZE_3' (see [1]),
but should be fixed by commit 'boot/grub2: workaround breakage with -O2,
-O3 build' (see [2])

Regards,
Peter

[1] https://bugs.busybox.net/show_bug.cgi?id=13586
[2] https://git.buildroot.net/buildroot/commit/?id=7cb51d4843caaa9144270d92f86e60d8b5a2a1ec

>
> Best regards,
> Stefan

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2021-10-07 21:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-07 20:36 [Buildroot] Boot process stuck at "GRUB loading.." since 2021.02.1 Walter, Stefan
2021-10-07 21:50 ` Peter Seiderer [this message]
2021-10-08 14:27   ` Walter, Stefan
2021-10-08 17:25     ` Peter Seiderer
2021-10-11 12:23       ` Walter, Stefan
2021-10-11 17:29         ` Walter, Stefan
2021-10-18 22:22           ` Peter Seiderer
2021-10-19 15:17             ` Walter, Stefan
2021-10-19 21:02               ` Peter Seiderer
2021-10-21 17:59                 ` Yann E. MORIN
2021-10-22  9:48                   ` Köry Maincent
2021-10-22 17:42                     ` Peter Seiderer
2021-10-08 16:53 ` Alexander Dahl

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=20211007235019.51751a53@gmx.net \
    --to=ps.report@gmx.net \
    --cc=buildroot@buildroot.org \
    --cc=stefan.walter@iml.fraunhofer.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.