[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-efi
Subject:    Re: Efistub patch breaks 5.10 for me
From:       Ard Biesheuvel <ardb () kernel ! org>
Date:       2020-12-17 13:41:27
Message-ID: CAMj1kXFDN6Y_xpywzksBhYh-S9BuFuDRgfAOdWrUN6LTuKc+WQ () mail ! gmail ! com
[Download RAW message or body]

On Thu, 17 Dec 2020 at 14:39, Klaus Kusche <klaus.kusche@computerix.info> wrote:
>
>
> 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.
>

Thanks for reporting back, and good luck debugging the radeon driver :-)
[prev in list] [next in list] [prev in thread] [next in thread]