From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1753719AbdBARfx (ORCPT <rfc822;w@1wt.eu>);
        Wed, 1 Feb 2017 12:35:53 -0500
Received: from mail-qt0-f177.google.com ([209.85.216.177]:34010 "EHLO
        mail-qt0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1753448AbdBARft (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 1 Feb 2017 12:35:49 -0500
Subject: Re: [REGRESSION] EFI mixed mode patch triggers boot failure
To: Jiri Kosina <jikos@kernel.org>
References: <dc0bc031-f20e-9ad0-57f4-cfa1e04f8f05@redhat.com>
 <7af87cde-ce79-d6e8-0797-54069a77f42b@redhat.com>
 <20161020120357.GB19876@codeblueprint.co.uk>
 <e34311e8-fe39-3b65-bd6d-8f1594e56336@redhat.com>
 <20170127223441.GJ31613@codeblueprint.co.uk>
 <f7d8f786-6000-cbbe-feb2-c97c0378b6e9@redhat.com>
 <alpine.LSU.2.20.1701301409270.25515@cbobk.fhfr.pm>
Cc: Matt Fleming <matt@codeblueprint.co.uk>,
        "x86@kernel.org" <x86@kernel.org>, linux-kernel@vger.kernel.org,
        linux-efi@vger.kernel.org, Justin Forbes <jforbes@redhat.com>,
        Ard Biesheuvel <ard.biesheuvel@linaro.org>
From: Laura Abbott <labbott@redhat.com>
Message-ID: <1208352f-ab6a-4489-d6b1-2f3e537f5e60@redhat.com>
Date: Wed, 1 Feb 2017 09:35:44 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <alpine.LSU.2.20.1701301409270.25515@cbobk.fhfr.pm>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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