From: Ilias Apalodimas <ilias.apalodimas@linaro.org>
To: Michal Simek <michal.simek@xilinx.com>
Cc: AKASHI Takahiro <takahiro.akashi@linaro.org>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Sughosh Ganu <sughosh.ganu@linaro.org>,
U-Boot Mailing List <u-boot@lists.denx.de>,
Simon Glass <sjg@chromium.org>,
Vincent Stehle <Vincent.Stehle@arm.com>
Subject: Re: EFI from usb HDD
Date: Wed, 4 Aug 2021 13:50:32 +0300 [thread overview]
Message-ID: <CAC_iWjLh3rWU9aaKskkDe-Az+uxvN501YWTQ2E38DGSxs_-L_A@mail.gmail.com> (raw)
In-Reply-To: <65818adc-728c-8a84-973d-0333e3c6e8b2@xilinx.com>
Hi Michal
Apologies for my late reply, I was on vacation!
[...]
> >>
> >> When Abort happened I connected Xilinx debugger via jtag and look at cpu
> >> backtrace.
> >
> > OK, but we are already in grub here and such a trace (in U-Boot)
> > doesn't make sense. Right?
>
> Correct grub already started. But I expect it is still using U-Boot
> drivers and all exception handlers are still in place from u-boot.
Yes, U-Boot is still alive and GRUB is accessing some of the
functionality via Boottime services.
>
> Maybe it is just sata/scsi related issue in EFI but weird is that when
> disks are scan just before command everything is working fine.
>
> Should I try to initialize and populate EFI object list all the time?
> (Remove this code for testing)
> /* Initialize once only */
> if (efi_obj_list_initialized != OBJ_LIST_NOT_INITIALIZED)
> return efi_obj_list_initialized;
>
> Or based on this thread to try your series pointed above?
This smells like a different init sequence when a command is issued first.
I'll try having a closer look. Let me know if you find anything else
Cheers
/Ilias
>
> Thanks,
> Michal
>
next prev parent reply other threads:[~2021-08-04 10:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 8:44 EFI from usb HDD Michal Simek
2021-06-10 9:47 ` Heinrich Schuchardt
2021-06-10 10:04 ` Michal Simek
2021-06-10 10:51 ` Heinrich Schuchardt
2021-06-10 12:31 ` Michal Simek
2021-06-10 12:59 ` AKASHI Takahiro
2021-07-29 14:09 ` Michal Simek
2021-07-30 2:35 ` AKASHI Takahiro
2021-07-30 4:41 ` Michal Simek
2021-07-30 5:33 ` AKASHI Takahiro
2021-07-30 6:22 ` Michal Simek
2021-08-04 10:50 ` Ilias Apalodimas [this message]
2021-08-11 12:28 ` Michal Simek
2021-08-12 9:43 ` AKASHI Takahiro
2021-08-17 7:20 ` Michal Simek
2021-08-18 5:13 ` AKASHI Takahiro
2021-08-18 9:07 ` Michal Simek
2021-08-19 4:14 ` AKASHI Takahiro
2021-08-19 5:38 ` Michal Simek
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=CAC_iWjLh3rWU9aaKskkDe-Az+uxvN501YWTQ2E38DGSxs_-L_A@mail.gmail.com \
--to=ilias.apalodimas@linaro.org \
--cc=Vincent.Stehle@arm.com \
--cc=michal.simek@xilinx.com \
--cc=sjg@chromium.org \
--cc=sughosh.ganu@linaro.org \
--cc=takahiro.akashi@linaro.org \
--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 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.