Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1568769 > unrolled thread
| Started by | Matt Fleming <matt@codeblueprint.co.uk> |
|---|---|
| First post | 2017-01-27 23:50 +0100 |
| Last post | 2017-02-01 18:40 +0100 |
| Articles | 4 — 3 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [REGRESSION] EFI mixed mode patch triggers boot failure Matt Fleming <matt@codeblueprint.co.uk> - 2017-01-27 23:50 +0100
Re: [REGRESSION] EFI mixed mode patch triggers boot failure Laura Abbott <labbott@redhat.com> - 2017-01-28 09:40 +0100
Re: [REGRESSION] EFI mixed mode patch triggers boot failure Jiri Kosina <jikos@kernel.org> - 2017-01-30 14:20 +0100
Re: [REGRESSION] EFI mixed mode patch triggers boot failure Laura Abbott <labbott@redhat.com> - 2017-02-01 18:40 +0100
| From | Matt Fleming <matt@codeblueprint.co.uk> |
|---|---|
| Date | 2017-01-27 23:50 +0100 |
| Subject | Re: [REGRESSION] EFI mixed mode patch triggers boot failure |
| Message-ID | <t4nvb-1BT-5@gated-at.bofh.it> |
On Mon, 24 Oct, at 12:54:11PM, 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
[toc] | [next] | [standalone]
| From | Laura Abbott <labbott@redhat.com> |
|---|---|
| Date | 2017-01-28 09:40 +0100 |
| Message-ID | <t4wI9-7pN-11@gated-at.bofh.it> |
| In reply to | #1568769 |
On 01/27/2017 11:34 PM, Matt Fleming wrote: > On Mon, 24 Oct, at 12:54:11PM, 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. Thanks, Laura
[toc] | [prev] | [next] | [standalone]
| From | Jiri Kosina <jikos@kernel.org> |
|---|---|
| Date | 2017-01-30 14:20 +0100 |
| Message-ID | <t5k2e-4rq-23@gated-at.bofh.it> |
| In reply to | #1568849 |
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
[toc] | [prev] | [next] | [standalone]
| From | Laura Abbott <labbott@redhat.com> |
|---|---|
| Date | 2017-02-01 18:40 +0100 |
| Message-ID | <t672Y-pD-59@gated-at.bofh.it> |
| In reply to | #1569732 |
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
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web