[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200410112605.GA3344@localhost.localdomain>
Date: Fri, 10 Apr 2020 13:26:05 +0200
From: Thomas Meyer <thomas@...3r.de>
To: Arvind Sankar <nivedita@...m.mit.edu>
Cc: Ard Biesheuvel <ardb@...nel.org>, Borislav Petkov <bp@...en8.de>,
Sergey Shatunov <me@...k.pw>, hpa@...or.com,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
mingo@...hat.com, Thomas Gleixner <tglx@...utronix.de>,
x86@...nel.org, linux-efi <linux-efi@...r.kernel.org>,
initramfs@...r.kernel.org,
Donovan Tremura <neurognostic@...tonmail.ch>,
Harald Hoyer <harald@...er.xyz>
Subject: Re: [PATCH 1/2] efi/x86: Move efi stub globals from .bss to .data
On Mon, Apr 06, 2020 at 02:06:13PM -0400, Arvind Sankar wrote:
Hi,
I did write an email to x86@...nel.org, which sadly seems to have no
mailing list archive, I wonder if my problem has anything to do with the
patches you are discussing here:
I found this reply, which contains my original email in my inbox:
Subject: Kernel v5.5 doesn't boot on my x86 laptop
Hi,
I'm using an old MacBookPro1,1 to run Fedora 30 (the last one to support
x86) and a upstream up-to-date kernel, currently 5.4.16.
I'm using sd-boot to boot into an EFI-enabled kernel which contains
an embedded initram cpio image (because loading the image from kernel's
EFI stub doesn't seem to work for some unknown reason, I tried to debug
this but my early debugging foo is too weak).
Kernel 5.4.x works correctly with this setup (but resuming from disk
seems to have broken in 5.4.x or maybe even earlier - when resuming from
disk I get all kind of funky OOPSes/errors, but that's another story, hopefully
5.5.x was fixed in this regards).
So I did have a look at the commits under arch/x86/boot and "x86/boot:
Introduce setup_indirect" (b3c72fc9a78e74161f9d05ef7191706060628f8c) did
talk about "bump setup_header version in arch/x86/boot/header.S", so I
did revert above commit and I was finally able to boot into v5.5 kernel!
So either sd-boot also needs an upgrade or this commit does break
something.
Any help is welcome, don't hesitate to get in contact with me if you
have any questions.
mfg
thomas
Powered by blists - more mailing lists