All of lore.kernel.org
 help / color / mirror / Atom feed
From: Klaus Kusche <klaus.kusche@computerix.info>
To: nivedita@alum.mit.edu
Cc: mario.limonciello@dell.com, jacobopantoja@gmail.com,
	ardb@kernel.org, pjones@redhat.com, linux-efi@vger.kernel.org
Subject: Efistub patch breaks 5.10 for me
Date: Thu, 17 Dec 2020 13:13:08 +0100	[thread overview]
Message-ID: <242ea718-89f8-e74f-e48a-e6b0fa436ed1@computerix.info> (raw)


Hello,

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).

5.9.15 works fine.

Of course, this could be some other change 5.9 --> 5.10,
but I think Efistub is the first suspect.

Directly booting from UEFI to linux, no bootloader.

Dell Precision Mobile 7740,
dmidecode says BIOS version 1.7.0, 01/07/2020.

My kernel has *no* command line arguments at all
or at least, it should not have any
(fully static kernel with no modules or initrd,
all kernel parameters configured into the kernel).

In 5.9.15, dmesg displays only a \x01 for the command line.

Next step?
Is there sonething to try out?
Are there any patches I should reverse-apply?
Should I open a bug at buzilla.kernel.org?

Thanks for any help!

-- 
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

             reply	other threads:[~2020-12-17 12:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17 12:13 Klaus Kusche [this message]
2020-12-17 12:41 ` Efistub patch breaks 5.10 for me Ard Biesheuvel
2020-12-17 13:39   ` Klaus Kusche
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=242ea718-89f8-e74f-e48a-e6b0fa436ed1@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 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.