On 06/08/17 at 03:51pm, Ard Biesheuvel wrote:
> On 8 June 2017 at 05:32, Dave Young wrote:
> > Maniaxx reported kernel boot panic similar to
> > below:
> > (emulated the panic with using same invalid phys addr in a uefi vm)
> > There are also a bug
On 06/08/17 at 03:51pm, Ard Biesheuvel wrote:
> On 8 June 2017 at 05:32, Dave Young wrote:
> > Maniaxx reported kernel boot panic similar to
> > below:
> > (emulated the panic with using same invalid phys addr in a uefi vm)
> > There are also a bug in bugzilla.kernel.org:
> >
On 8 June 2017 at 05:32, Dave Young wrote:
> Maniaxx reported kernel boot panic similar to
> below:
> (emulated the panic with using same invalid phys addr in a uefi vm)
> There are also a bug in bugzilla.kernel.org:
>
On 8 June 2017 at 05:32, Dave Young wrote:
> Maniaxx reported kernel boot panic similar to
> below:
> (emulated the panic with using same invalid phys addr in a uefi vm)
> There are also a bug in bugzilla.kernel.org:
> https://bugzilla.kernel.org/show_bug.cgi?id=195633
>
> This happens after
On 8 June 2017 at 14:24, Ard Biesheuvel wrote:
> On 8 June 2017 at 14:20, Dave Young wrote:
>> On 06/08/17 at 10:02am, Ard Biesheuvel wrote:
>>> On 8 June 2017 at 05:32, Dave Young wrote:
>>> > Maniaxx
On 8 June 2017 at 14:24, Ard Biesheuvel wrote:
> On 8 June 2017 at 14:20, Dave Young wrote:
>> On 06/08/17 at 10:02am, Ard Biesheuvel wrote:
>>> On 8 June 2017 at 05:32, Dave Young wrote:
>>> > Maniaxx reported kernel boot panic similar to
>>> > below:
>>> > (emulated the panic with using
On 8 June 2017 at 14:20, Dave Young wrote:
> On 06/08/17 at 10:02am, Ard Biesheuvel wrote:
>> On 8 June 2017 at 05:32, Dave Young wrote:
>> > Maniaxx reported kernel boot panic similar to
>> > below:
>> > (emulated the panic with
On 8 June 2017 at 14:20, Dave Young wrote:
> On 06/08/17 at 10:02am, Ard Biesheuvel wrote:
>> On 8 June 2017 at 05:32, Dave Young wrote:
>> > Maniaxx reported kernel boot panic similar to
>> > below:
>> > (emulated the panic with using same invalid phys addr in a uefi vm)
>> > There are also a
On 06/08/17 at 10:02am, Ard Biesheuvel wrote:
> On 8 June 2017 at 05:32, Dave Young wrote:
> > Maniaxx reported kernel boot panic similar to
> > below:
> > (emulated the panic with using same invalid phys addr in a uefi vm)
> > There are also a bug
On 06/08/17 at 10:02am, Ard Biesheuvel wrote:
> On 8 June 2017 at 05:32, Dave Young wrote:
> > Maniaxx reported kernel boot panic similar to
> > below:
> > (emulated the panic with using same invalid phys addr in a uefi vm)
> > There are also a bug in bugzilla.kernel.org:
> >
On 08.06.2017 at 07:38 wrote Dave Young:
> Maniaxx, can you verify it on your machine? It passed my test with
> an emulation of your wrong address.
Works. Bails out properly on 4.12.0-rc4-gb29794ec95c6.
[0.00] efi_bgrt: Ignoring BGRT: invalid image address
On 08.06.2017 at 07:38 wrote Dave Young:
> Maniaxx, can you verify it on your machine? It passed my test with
> an emulation of your wrong address.
Works. Bails out properly on 4.12.0-rc4-gb29794ec95c6.
[0.00] efi_bgrt: Ignoring BGRT: invalid image address
On 8 June 2017 at 05:32, Dave Young wrote:
> Maniaxx reported kernel boot panic similar to
> below:
> (emulated the panic with using same invalid phys addr in a uefi vm)
> There are also a bug in bugzilla.kernel.org:
>
On 8 June 2017 at 05:32, Dave Young wrote:
> Maniaxx reported kernel boot panic similar to
> below:
> (emulated the panic with using same invalid phys addr in a uefi vm)
> There are also a bug in bugzilla.kernel.org:
> https://bugzilla.kernel.org/show_bug.cgi?id=195633
>
> This happens after
The subject tag should be efi instead of x86/efi since the code
is in general driver code now. Matt/Ard, if need resend please let me
know. Please help review the patch.
Maniaxx, can you verify it on your machine? It passed my test with
an emulation of your wrong address.
On 06/08/17 at 01:32pm,
The subject tag should be efi instead of x86/efi since the code
is in general driver code now. Matt/Ard, if need resend please let me
know. Please help review the patch.
Maniaxx, can you verify it on your machine? It passed my test with
an emulation of your wrong address.
On 06/08/17 at 01:32pm,
Maniaxx reported kernel boot panic similar to below:
(emulated the panic with using same invalid phys addr in a uefi vm)
There are also a bug in bugzilla.kernel.org:
https://bugzilla.kernel.org/show_bug.cgi?id=195633
This happens after below commit:
7b0a911 efi/x86:
Maniaxx reported kernel boot panic similar to below:
(emulated the panic with using same invalid phys addr in a uefi vm)
There are also a bug in bugzilla.kernel.org:
https://bugzilla.kernel.org/show_bug.cgi?id=195633
This happens after below commit:
7b0a911 efi/x86: Move the EFI BGRT init code
18 matches
Mail list logo