From: Arvind Sankar <nivedita@alum.mit.edu>
To: Like Xu <like.xu@linux.intel.com>
Cc: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
linux-x86_64@vger.kernel.org, nivedita@alum.mit.edu
Subject: Re: [Bug report] Kernel 5.7 become unbootable
Date: Fri, 10 Apr 2020 10:29:20 -0400 [thread overview]
Message-ID: <20200410142920.GA936997@rani.riverdale.lan> (raw)
In-Reply-To: <1d02e4f3-8d83-4c55-bce2-f5aa4af2e363@linux.intel.com>
On Fri, Apr 10, 2020 at 04:16:58PM +0800, Like Xu wrote:
> On 2020/4/10 3:12, Mikhail Gavrilov wrote:
> > Hi folks.
> > I use Fedora Rawhide and today's update came with the new kernel
> > 5.7.0-0.rc0.git6.1.
> > As it turned out this kernel won't boot. Instead, I see the black
> > screen and some times see messages:
> > exit_boot() failed!
> > efi_main() failed!
> >
> > The last working kernel is kernel-core-5.7.0-0.rc0.git2.1
> >
> > I looked at the spec file and found out that the last bootable kernel
> > was related to the commit cad18da0afb1
> > (https://src.fedoraproject.org/rpms/kernel/c/9949db6070c6ca501d7235760ca8aba120db7448?branch=master),
> > and the first non-bootable kernel related to the commit a10c9c710f9e
> > (https://src.fedoraproject.org/rpms/kernel/c/0561e0bf0e459dd4b27a77670de838128b87bd0e?branch=master)
> >
> > Of course, knowing these two commits, I made bisecting with the vanilla kernel:
> >
> >
> > Can anyone here help me with this issue?
>
> I encountered the same issue as you:
>
> exit_boot() failed!
> efi_main() failed!
>
> and the following patches are very suspicious:
>
> x86/boot/compressed/64: Use LEA to initialize boot stack pointer
> x86/boot/compressed/64: Use 32-bit (zero-extended) MOV for z_output_len
> x86/boot/compressed/64: Remove .bss/.pgtable from bzImage
> x86/boot/compressed: Remove .eh_frame section from bzImage
>
> I am not sure if reverting these patches can help you.
>
> Thanks,
> Like Xu
>
Please try with the patches at
https://lore.kernel.org/linux-efi/20200409130434.6736-1-ardb@kernel.org/
In particular, patches 3 and 4. The first one is a fix for upstream
commit 3ee372ccce4d ("x86/boot/compressed/64: Remove .bss/.pgtable from bzImage")
next prev parent reply other threads:[~2020-04-10 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 19:12 Mikhail Gavrilov
2020-04-10 8:16 ` Like Xu
2020-04-10 14:29 ` Arvind Sankar [this message]
2020-04-10 19:23 ` Mikhail Gavrilov
2020-04-11 1:09 ` Arvind Sankar
[not found] ` <20200411020051.20448-1-hdanton@sina.com>
2020-04-12 20:00 ` Mikhail Gavrilov
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=20200410142920.GA936997@rani.riverdale.lan \
--to=nivedita@alum.mit.edu \
--cc=like.xu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-x86_64@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
/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
all inboxes | Powered by JetHome®