From: Klaus Kusche <klaus.kusche@computerix.info>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Arvind Sankar <nivedita@alum.mit.edu>,
"Limonciello, Mario" <mario.limonciello@dell.com>,
Jacobo Pantoja <jacobopantoja@gmail.com>,
Peter Jones <pjones@redhat.com>,
linux-efi <linux-efi@vger.kernel.org>
Subject: Re: Efistub patch breaks 5.10 for me
Date: Thu, 17 Dec 2020 14:39:46 +0100 [thread overview]
Message-ID: <21bee914-35d0-c33d-b68c-20574f8e6fb6@computerix.info> (raw)
In-Reply-To: <CAMj1kXHSSZftuv-M9Gg-V+XFTJtFtii8Jfqin03kstSuF9DRJA@mail.gmail.com>
Hello,
On 17/12/2020 13:41, Ard Biesheuvel wrote:
>> tried to boot 5.10.1 (my first attempt to boot a 5.10.x).
>>
>> Displays
>>
>> EFI stub: WARNING: [Firmware Bug]: LoadOptions is an EFI_LOAD_OPTION descriptor
>> EFI stub: WARNING: [Firmware Bug]: Using OptionalData as a workaround
>>
>> for one or two seconds on the notebook display.
>>
>> Then, the notebook display becomes completely black
>> and the notebook does not boot and does not react to anything
>> (hard poweroff needed).
>
> Hello Klaus,
>
> Please try reverting
>
> 4a568ce29d3f48df95919f82a80e4b9be7ea0dc1
>
> "efi/x86: Add a quirk to support command line arguments on Dell EFI firmware"
Thanks for the quick response.
Efistub is *not* the culprit:
With the patch reverted, the two efistub error messages are gone.
And with the two errormessages not occupying the display and my attention,
I noticed that the kernel actually came up for fractions of a second
before the display went dark.
AMD radeon seems to be the culprit:
After unconfiguring it, the system comes up fine in text mode,
both with and without the efistub patch.
And with the efistub patch applied,
dmesg actually shows an empty command line instead of the \x01,
as it should.
--
Prof. Dr. Klaus Kusche
Private address: Rosenberg 41, 07546 Gera, Germany
+49 365 20413058 klaus.kusche@computerix.info https://www.computerix.info
Office address: DHGE Gera, Weg der Freundschaft 4, 07546 Gera, Germany
+49 365 4341 306 klaus.kusche@dhge.de https://www.dhge.de
next prev parent reply other threads:[~2020-12-17 13:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 12:13 Efistub patch breaks 5.10 for me Klaus Kusche
2020-12-17 12:41 ` Ard Biesheuvel
2020-12-17 13:39 ` Klaus Kusche [this message]
2020-12-17 13:41 ` Ard Biesheuvel
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=21bee914-35d0-c33d-b68c-20574f8e6fb6@computerix.info \
--to=klaus.kusche@computerix.info \
--cc=ardb@kernel.org \
--cc=jacobopantoja@gmail.com \
--cc=linux-efi@vger.kernel.org \
--cc=mario.limonciello@dell.com \
--cc=nivedita@alum.mit.edu \
--cc=pjones@redhat.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