Re: [Xen-devel] UEFI support on Dell boxes (was: Re: Status of 4.13) - Marek Marczykowski-Górecki

From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Roman Shaposhnik <roman@zededa.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] UEFI support on Dell boxes (was: Re: Status of 4.13)
Date: Tue, 26 Nov 2019 04:55:17 +0100	[thread overview]
Message-ID: <20191126035517.GT5763@mail-itl> (raw)
In-Reply-To: <CAMmSBy9gkVR-ua9=kVn9rNSb2VnvvtzaLL=ZM-GXxCdtRGRtvA@mail.gmail.com>

[-- Attachment #1.1: Type: text/plain, Size: 2378 bytes --]

On Mon, Nov 25, 2019 at 07:44:03PM -0800, Roman Shaposhnik wrote:
> On Sun, Nov 24, 2019 at 4:48 PM Marek Marczykowski-Górecki
> <marmarek@invisiblethingslab.com> wrote:
> > Do you have by
> > a chance messages of that crash (without efi=no-rs, but with
> > EFI_SET_VIRTUAL_ADDRESS_MAP enabled)? Or even a photo if no serial output is
> > available?
> 
> With my awesome soldering skills ;-) I managed to rig a serial console.
> 
> Output is attached. Please let me know if you'd like me to run any
> other experiments.

Looks helpful, lets try to do something:

>  Xen 4.13.0-rc
> (XEN) Xen version 4.13.0-rc (@) (gcc (Alpine 6.4.0) 6.4.0) debug=y  Tue Nov 26 03:19:38 UTC 2019
> (XEN) Latest ChangeSet:
> (XEN) build-id: 07aa9f711fe09a91be2588ee7df10d93ebe34c80
> (XEN) Bootloader: GRUB 2.03
> (XEN) Command line: com1=115200,8n1 console=com1 loglvl=all noreboot dom0_mem=640M,max:640M dom0_max_vcpus=1 dom0_vcpus_pin smt=false
(...)
> (XEN) EFI memory map:
(...)
> (XEN)  0000077587000-00000775f4fff type=5 attr=800000000000000f

This is code that crashes - runtime services code, so somewhere with
actual UEFI code.

(...)
> (XEN)  00000ff900000-00000ffffffff type=11 attr=8000000000000000
> (XEN) Unknown cachability for MFNs 0xff900-0xfffff

The faulting address is in this range. And because of unknown
cachability, it isn't mapped. Try adding 'efi=attr=uc' to the Xen
cmdline.

(...)

> (XEN) Xen call trace:
> (XEN)    [<00000000775e0d21>] R 00000000775e0d21
> (XEN)    [<00000000775ddb8e>] S 00000000775ddb8e
> (XEN)    [<0000000000000000>] F 0000000000000000
> (XEN)    [<7fffffff00000000>] F 7fffffff00000000
> (XEN)
> (XEN) Pagetable walk from 00000000ff920020:
> (XEN)  L4[0x000] = 00000000787c0063 ffffffffffffffff
> (XEN)  L3[0x003] = 0000000071298063 ffffffffffffffff
> (XEN)  L2[0x1fc] = 0000000000000000 ffffffffffffffff
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) FATAL PAGE FAULT
> (XEN) [error_code=0000]
> (XEN) Faulting linear address: 00000000ff920020
> (XEN) ****************************************
> (XEN)
> (XEN) Manual reset required ('noreboot' specified)

-- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel