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 S1751293AbdBWXDJ (ORCPT <rfc822;w@1wt.eu>);
        Thu, 23 Feb 2017 18:03:09 -0500
Received: from mail-qt0-f173.google.com ([209.85.216.173]:34281 "EHLO
        mail-qt0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751242AbdBWXDI (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 23 Feb 2017 18:03:08 -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>
 <1208352f-ab6a-4489-d6b1-2f3e537f5e60@redhat.com>
 <alpine.LSU.2.20.1702232132360.24579@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>, joeyli <jlee@suse.com>,
        Gary Lin <glin@suse.com>
From: Laura Abbott <labbott@redhat.com>
Message-ID: <9ab9be94-fb2b-4804-8de3-cd0d8ab7134b@redhat.com>
Date: Thu, 23 Feb 2017 15:02:58 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <alpine.LSU.2.20.1702232132360.24579@cbobk.fhfr.pm>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On 02/23/2017 12:34 PM, Jiri Kosina wrote:
> On Wed, 1 Feb 2017, Laura Abbott wrote:
> 
>> 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.
> 
> [ adding Joey and Gary to CC ]
> 
> Laura,
> 
> have you by any chance heard back from anyone who's been able to trigger 
> the original problem?
> 
> We're now trying to figure out how widespread the problem might be (and 
> which part of the BIOS is to blame), so any further datapoints would be 
> helpful.
> 
> Thanks,
> 

Apart from the original reporter I have not heard back from anyone
specifically. The original reporter did say the bug was fixed.There
were a bunch of reporters who didn't respond to requests for info.

Thanks,
Laura