From: Laura Abbott <labbott@redhat.com>
To: Jiri Kosina <jikos@kernel.org>
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>
Subject: Re: [REGRESSION] EFI mixed mode patch triggers boot failure
Date: Thu, 23 Feb 2017 15:02:58 -0800 [thread overview]
Message-ID: <9ab9be94-fb2b-4804-8de3-cd0d8ab7134b@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.20.1702232132360.24579@cbobk.fhfr.pm>
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
prev parent reply other threads:[~2017-02-23 23:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 20:04 Laura Abbott
2016-10-19 21:13 ` Laura Abbott
2016-10-20 12:03 ` Matt Fleming
2016-10-24 19:54 ` Laura Abbott
2017-01-27 22:34 ` Matt Fleming
2017-01-28 8:35 ` Laura Abbott
2017-01-30 13:10 ` Jiri Kosina
2017-02-01 17:35 ` Laura Abbott
2017-02-23 20:34 ` Jiri Kosina
2017-02-23 23:02 ` Laura Abbott [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9ab9be94-fb2b-4804-8de3-cd0d8ab7134b@redhat.com \
--to=labbott@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=glin@suse.com \
--cc=jforbes@redhat.com \
--cc=jikos@kernel.org \
--cc=jlee@suse.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®