All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bin Meng <bmeng.cn@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] bootefi selftest on qemu-x86_64
Date: Wed, 10 Oct 2018 08:15:08 +0800	[thread overview]
Message-ID: <CAEUhbmWpcE0mM=oX4JRGJx4t9Q0j53Cv1EXxyZMuLcbTX_E-yw@mail.gmail.com> (raw)
In-Reply-To: <CAEUhbmVOpRX8R+1QUuE2neM-Xb0HG-=Y2=FL9Cc554Fsu=w8dw@mail.gmail.com>

Hi Heinrich,

On Wed, Oct 10, 2018 at 7:56 AM Bin Meng <bmeng.cn@gmail.com> wrote:
>
> Hi Heinrich,
>
> On Wed, Oct 10, 2018 at 12:48 AM Heinrich Schuchardt <xypron.glpk@gmx.de> wrote:
> >
> > On 10/09/2018 11:27 AM, Bin Meng wrote:
> > > Hi Heinrich,
> > >
> > > Did you ever get 'bootefi selftest' pass on qemu-x86_64? I got:
> > >
> > > => bootefi selftest
> > > WARNING: booting without device tree
> > > lib/efi_selftest/efi_selftest.c(242):
> > > ERROR: Cannot open loaded image protocol
> > >
> > > Regards,
> > > Bin
> > >
> > Hello Bin,
> >
> > when running qemu-x86_64_defconfig with
> >
> > qemu-system-x86_64 -bios denx/u-boot.rom -machine pc-i440fx-2.5 --nographic
> >
> > it hangs in an endless loop:
> >
> > U-Boot 2018.11-rc1-00130-g0a60a81ba3 (Oct 09 2018 - 18:23:16 +0200)
> >
> > QEMU Virtual CPU version 2.5+DRAM:  128 MiB
> >
> > U-Boot SPL 2018.11-rc1-00130-g0a60a81ba3 (Oct 09 2018 - 18:23:16 +0200)
> > CPU: x86_64, vendor AMD, device 663h
> > Trying to boot from SPI
> > Jumping to 64-bit U-Boot: Note many features are missing
> >
> >
> > U-Boot 2018.11-rc1-00130-g0a60a81ba3 (Oct 09 2018 - 18:23:16 +0200)
> >
> > QEMU Virtual CPU version 2.5+DRAM:  128 MiB
> >
> > U-Boot SPL 2018.11-rc1-00130-g0a60a81ba3 (Oct 09 2018 - 18:23:16 +0200)
> > CPU: x86_64, vendor AMD, device 663h
> > Trying to boot from SPI
> > Jumping to 64-bit U-Boot: Note many features are missing
> >
> >
> > U-Boot 2018.11-rc1-00130-g0a60a81ba3 (Oct 09 2018 - 18:23:16 +0200)
> >
> > QEMU Virtual CPU version 2.5+DRAM:  128 MiB
> >
> > ....
> >
> > How did you succeed to reach the console?
> >

Forgot to mention, that I searched the ML and did see you and Ivan
Gorinov discussed running 'bootefi selftest' on qemu-x86_64 [1] before
and there was patch submitted to support "x86 64-bit setjmp/longjmp"
needed by EFI. So I assume you guys had figured it out. But my testing
shows that the bug (endless reset loop) is still there, and it is
related to compiler being used. But I thought you might get a compiler
that happened to work for you hence I asked the 'bootefi selftest'
status.

Anyway I have figured out the root cause, and please try that.

>
> It is a bug and I noticed this when testing GCC 8.1.0. Patches will be
> sent soon.
>
> > There is a doc/README.x86 but nothing on x86_64. Could you, please, add
> > the missing information in said README.x86.
> >
>
> Will do.
>
> > I could not find qemu-x86_64_defconfig in .travis.yml. Shouldn't we try
> > to run the target there too?
> >
>
> I tried this but it fails with EFI selftesting.
>
> > I am using Debian Buster:
> > gcc 8.2.0
> > qemu 2.12.0
> >

[1] https://lists.denx.de/pipermail/u-boot/2018-June/331836.html

Regards,
Bin

      reply	other threads:[~2018-10-10  0:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-09  9:27 [U-Boot] bootefi selftest on qemu-x86_64 Bin Meng
2018-10-09 16:48 ` Heinrich Schuchardt
2018-10-09 23:56   ` Bin Meng
2018-10-10  0:15     ` Bin Meng [this message]

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='CAEUhbmWpcE0mM=oX4JRGJx4t9Q0j53Cv1EXxyZMuLcbTX_E-yw@mail.gmail.com' \
    --to=bmeng.cn@gmail.com \
    --cc=u-boot@lists.denx.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.