lkml.org 
[lkml]   [2015]   [Feb]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH v9 00/21] Introduce ACPI for ARM64 based on ACPI 5.1
    > > I'm still debugging it, but v9 on the 4.0-rc1 kernel crashes after calling
    > > the UEFI boot time services exit function. That is, this line:
    > >
    > > status = sys_table->boottime->exit_boot_services(handle, mmap_key);
    > >
    > > in allocate_new_fdt_and_exit_boot() gets called, and then soon after it
    > > returns, the kernel crashes. It's really early because the UEFI exception
    > > handler is called.
    > >
    > > I did not have this problem with v8 patchset on 3.19.
    > >
    >
    > Are you not seeing this on v4.0-rc1 without the patchset applied?
    >
    > Could the crash be inside the subsequent call to
    > SetVirtualAddressMap() instead of inside ExitBootServices()?
    >
    > If so, you have a firmware bug: Mark Rutland spotted a similar bug in
    > the AMD Seattle firmware, which has been fixed in the mean time.
    > It has to do with the firmware dereferencing the virtual mapping as it
    > is being installed, which violates the UEFI spec.

    A simple way to test is to change EFI_RT_VIRTUAL_BASE to point to the
    (unmapped) high half of the address space (e.g. set it to
    0xffff000000000000). If EFI is using pointers erroneously then something
    should fault within SetVirtualAddressMap(), and you can catch this with
    your favourite debugger.

    Otherwise it's possible that the virtual address space chosen will cover
    memory and/or devices in the existing idmap, and any erroneous accesses
    will corrupt memory and/or cause devices to explode.

    Thanks,
    Mark


    \
     
     \ /
      Last update: 2015-02-27 12:01    [W:2.316 / U:0.020 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site