[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LSU.2.20.1701301409270.25515@cbobk.fhfr.pm>
Date: Mon, 30 Jan 2017 14:10:37 +0100 (CET)
From: Jiri Kosina <jikos@...nel.org>
To: Laura Abbott <labbott@...hat.com>
cc: Matt Fleming <matt@...eblueprint.co.uk>,
"x86@...nel.org" <x86@...nel.org>, linux-kernel@...r.kernel.org,
linux-efi@...r.kernel.org, Justin Forbes <jforbes@...hat.com>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>
Subject: Re: [REGRESSION] EFI mixed mode patch triggers boot failure
On Sat, 28 Jan 2017, Laura Abbott wrote:
> > > Was out for a few days, reporter says the below patch does not work.
> > > There was some confusion with secure boot so I've asked them to re-test
> > > with efi=old_map and secure boot off.
> >
> > FYI, you may want to ask the reporter to try out Jiri's patch if this
> > is still an issue for them,
> >
> > https://lkml.kernel.org/r/alpine.LSU.2.20.1701271638240.25515@cbobk.fhfr.pm
> >
>
> Thanks! I pulled this into the latest Fedora update so I'll be asking
> a couple of people to test.
BTW where exactly is this tracked for Fedora, please? I'd like to get an
idea how widespread this behavior is among different BIOS vendors.
I've found
https://bugzilla.redhat.com/show_bug.cgi?id=1384238
is that the primary tracking bug on your side?
Thanks,
--
Jiri Kosina
SUSE Labs
Powered by blists - more mailing lists