From: "Matwey V. Kornilov" <matwey.kornilov@gmail.com>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: michael@walle.cc, Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: BISECTED f3866909e350 ("distro_bootcmd: call EFI bootmgr even without having /EFI/boot")
Date: Sun, 6 Jun 2021 17:37:21 +0300 [thread overview]
Message-ID: <CAJs94EYZ63zGV3aG_ag6Eafwc+97p0C9H+-3frLWD+rj5qkogw@mail.gmail.com> (raw)
Hi,
I've found that
f3866909e350 ("distro_bootcmd: call EFI bootmgr even without having /EFI/boot")
breaks running EFI application from USB device on BeagleBone Black
(am335x) device.
With this patch I see the following:
Booting /efi\boot\bootarm.efi
Welcome to GRUB!
data abort
pc : [<9ce0b6d0>] lr : [<9ffab7c7>]
reloc pc : [<7d69d6d0>] lr : [<8083d7c7>]
sp : 9df44e28 ip : 9ffdfe90 fp : 00000003
r10: 9ffe3300 r9 : 00000000 r8 : 9df6fe88
r7 : 00000000 r6 : 9ce5da08 r5 : 9ce571f8 r4 : 9ce2c040
r3 : 00000000 r2 : 00000001 r1 : 9ce56598 r0 : 00000000
Flags: NzCv IRQs off FIQs on Mode SVC_32
Code: e3500000 0a000015 e590000c eb00f96e (e5d03000)
UEFI image [0x9ce46000:0x9cf28fff] '/efi\boot\bootarm.efi'
Resetting CPU ...
while without the patch, GRUB works as usual.
Could you please help me to figure out what is going wrong here?
--
With best regards,
Matwey V. Kornilov
next reply other threads:[~2021-06-06 14:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 14:37 Matwey V. Kornilov [this message]
2021-06-06 15:20 ` BISECTED f3866909e350 ("distro_bootcmd: call EFI bootmgr even without having /EFI/boot") Heinrich Schuchardt
2021-06-06 15:42 ` Matwey V. Kornilov
2021-06-06 16:21 ` Heinrich Schuchardt
2021-06-06 16:47 ` Heinrich Schuchardt
2021-06-07 17:51 ` Matwey V. Kornilov
2021-06-10 20:05 ` Heinrich Schuchardt
2021-06-10 21:02 ` Heinrich Schuchardt
2021-06-11 15:18 ` Matwey V. Kornilov
2021-06-11 15:08 ` Matwey V. Kornilov
2021-06-12 2:05 ` AKASHI Takahiro
2021-06-12 13:50 ` Matwey V. Kornilov
2021-06-13 5:28 ` AKASHI Takahiro
2021-06-07 17:36 ` Matwey V. Kornilov
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=CAJs94EYZ63zGV3aG_ag6Eafwc+97p0C9H+-3frLWD+rj5qkogw@mail.gmail.com \
--to=matwey.kornilov@gmail.com \
--cc=michael@walle.cc \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).