Could you provide some details about firmware? I would like to
reproduce it on our ThunderX2.
2018-06-25 17:28 GMT+02:00 Andrew Turner :
> I’ve not seen this on the ThunderX2 I have access to with the latest
> firmware. You’ll need to find out why the kernel is trying to access the
> memory,
I’ve not seen this on the ThunderX2 I have access to with the latest firmware.
You’ll need to find out why the kernel is trying to access the memory, and
where it is in the EFI memory map.
Andrew
> On 21 Jun 2018, at 13:41, Patryk Duda wrote:
>
> Hi,
>
> I'm trying to boot kernel on
Any updates?
2018-06-21 14:41 GMT+02:00 Patryk Duda :
> Hi,
>
> I'm trying to boot kernel on ThunderX2 but I've got following error:
>
> panic: efi_init: PA out of range, PA: 0xfafd0018
>
> This error comes from PHYS_TO_DMAP macro.
> I can workaround this issue by disabling EFI Runtime Services
Hi,
I'm trying to boot kernel on ThunderX2 but I've got following error:
panic: efi_init: PA out of range, PA: 0xfafd0018
This error comes from PHYS_TO_DMAP macro.
I can workaround this issue by disabling EFI Runtime Services in
kernel config but it seems to be
a problem with discontignous DMAP
Author: andrew
Date: Tue May 29 13:52:25 2018
New Revision: 334329
URL: https://svnweb.freebsd.org/changeset/base/334329
Log:
On ThunderX2 we need to be careful to only map the memory the firmware
lists in the EFI memory map. As such we need to reduce the mappings to
restrict them to not be
