All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Otte" <jrg.otte@gmail.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-efi <linux-efi@vger.kernel.org>,
	Arvind Sankar <nivedita@alum.mit.edu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Kernel V5.7-rc1 doesn't boot (EFI?)
Date: Tue, 14 Apr 2020 18:32:32 +0200	[thread overview]
Message-ID: <CADDKRnAvC7U6kWdiqmib40cJ7r41COyic4LTdO9utsp4GOJnvA@mail.gmail.com> (raw)
In-Reply-To: <CAMj1kXGuMjHi=E6cVGGpwrKF_-KXcj0VRcvAdFS_vmwV7PudCQ@mail.gmail.com>

Am Di., 14. Apr. 2020 um 12:50 Uhr schrieb Ard Biesheuvel <ardb@kernel.org>:
>
> On Tue, 14 Apr 2020 at 12:40, Jörg Otte <jrg.otte@gmail.com> wrote:
> >
> > Booting my notebook with kernel V57-rc1 I get following
> > display:
> >
> > exit_boot() failed!
> > efi_main() failed!
> > StartImage failed: Buffer Too Small
> >
> > Booting Kernel V5.6 works well.
> >
> > From dmesg (kernel V5.6):
> > efi: EFI v2.31 by Phoenix Technologies Ltd.
> > efi:  ACPI=0xdcffe000  ACPI 2.0=0xdcffe014  SMBIOS=0xdce80000  RNG=0xdc3cd198
> > efi: seeding entropy pool
> > efi: [Firmware Bug]: Invalid EFI memory map entries:
> > efi: mem47: [Reserved           |   |  |  |  |  |  |  |  |   |  |  |
> > |  ] range=[0x0000000000000000-0x0000000000000000] (invalid)
> > efi: mem48: [Reserved           |   |  |  |  |  |  |  |  |   |  |  |
> > |  ] range=[0x0000000000000000-0x0000000000000000] (invalid)
> > efi: mem49: [Reserved           |   |  |  |  |  |  |  |  |   |  |  |
> > |  ] range=[0x0000000000000000-0x0000000000000000] (invalid)
> > efi: mem50: [Reserved           |   |  |  |  |  |  |  |  |   |  |  |
> > |  ] range=[0x0000000000000000-0x0000000000000000] (invalid)
> > efi: mem51: [Reserved           |   |  |  |  |  |  |  |  |   |  |  |
> > |  ] range=[0x0000000000000000-0x0000000000000000] (invalid)
> > efi: Removing 5 invalid memory map entries.
> >
>
> Thanks for the report.
>
> Can you try booting with efi=no_disable_early_pci_dma passed via the
> kernel command line? [*]
>
Yes, that works!

> If that does not help, can you try to reproduce with this branch?
>
> https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/log/?h=efi/urgent

Should I give that branch a try anyway?

Thanks, Jörg

  reply	other threads:[~2020-04-14 16:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-14 10:40 Kernel V5.7-rc1 doesn't boot (EFI?) Jörg Otte
2020-04-14 10:50 ` Ard Biesheuvel
2020-04-14 16:32   ` Jörg Otte [this message]
2020-04-14 16:35     ` Ard Biesheuvel
2020-04-15  7:45       ` Ingo Molnar
2020-04-15  8:35       ` Jörg Otte
2020-04-15  9:58         ` Ard Biesheuvel
2020-04-14 18:27   ` Linus Torvalds
2020-04-14 18:32     ` Ard Biesheuvel
2020-04-14 18:44       ` Linus Torvalds

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=CADDKRnAvC7U6kWdiqmib40cJ7r41COyic4LTdO9utsp4GOJnvA@mail.gmail.com \
    --to=jrg.otte@gmail.com \
    --cc=ardb@kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nivedita@alum.mit.edu \
    --cc=torvalds@linux-foundation.org \
    /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.