[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1208352f-ab6a-4489-d6b1-2f3e537f5e60@redhat.com>
Date: Wed, 1 Feb 2017 09:35:44 -0800
From: Laura Abbott <labbott@...hat.com>
To: Jiri Kosina <jikos@...nel.org>
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 01/30/2017 05:10 AM, Jiri Kosina wrote:
> 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,
>
That's the main one where debugging was happening. There may be a couple
of others floating around that I hadn't had time to fully investigate.
I'll dupe them to the above if I find them.
Thanks,
Laura
Powered by blists - more mailing lists