From: Jiri Kosina <jikos@kernel.org>
To: Laura Abbott <labbott@redhat.com>
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>
Subject: Re: [REGRESSION] EFI mixed mode patch triggers boot failure
Date: Mon, 30 Jan 2017 14:10:37 +0100 (CET) [thread overview]
Message-ID: <alpine.LSU.2.20.1701301409270.25515@cbobk.fhfr.pm> (raw)
In-Reply-To: <f7d8f786-6000-cbbe-feb2-c97c0378b6e9@redhat.com>
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
next prev parent reply other threads:[~2017-01-30 13:13 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 [this message]
2017-02-01 17:35 ` Laura Abbott
2017-02-23 20:34 ` Jiri Kosina
2017-02-23 23:02 ` Laura Abbott
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=alpine.LSU.2.20.1701301409270.25515@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=ard.biesheuvel@linaro.org \
--cc=jforbes@redhat.com \
--cc=labbott@redhat.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®