Re: [Xen-devel] (XEN) APIC error on CPU0: 40(00)
On 04/11/2015 17:13, Jan Beulich wrote: On 04.11.15 at 16:15, wrote: >> Hi, >> i just build the latest 4.3.0 kernel and ran it on qubes-os with xen >> 4.4.3. I get this error just before the reboot: >> >> [(XEN) APIC error on CPU0: 40(00) > > And this appeared with the switch to kernel 4.3? No other variable > (e.g. all config options new in 4.3 turned off)? I ask because the > APIC is driven by Xen, not the kernel, and hence the kernel should > have no (direct) influence on APIC behavior. This started with 4.3.0, with 4.3.0-rc7 the system was booting properly (except for the xsave=0 workaround, without that i also get a crash dump right before the APIC error). > >> (XEN) Resetting with ACPI MEMORY or I/O RESET_REG. >> >> I can also see some weird acpi-related messages on the log i attached, like: >> (XEN) ACPI: Invalid sleep control/status register data: 0:0x8:0x3 0:0x8:0x3 >> (XEN) ERST table was not found >> [3.608404] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup >> failure, AE_NOT_FOUND (20150818/dswload-210) >> [3.608410] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog >> (20150818/psobject-227) >> [3.608439] ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while >> loading table (20150818/tbxfload-193) >> [3.619914] ACPI Error: 1 table load failures, 5 successful >> (20150818/tbxfload-214) >> [3.679113] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored >> [3.688942] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep >> State [\_S1_] (20150818/hwxface-580) >> [3.688948] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep >> State [\_S2_] (20150818/hwxface-580) >> [3.756027] PM-Timer failed consistency check (0xff) - aborting. >> >> With older kernels (like 3.12 or 4.2.1) i always see those messages but >> i'm able to boot without the acpi error. > > I guess those latter messages are unrelated - not the difference > between ACPI and APIC. Also I'm unsure about you saying "boot" > here but "reboot" above? The APIC error prevents me from booting the machine, causing a forced reboot, the above messages won't. They are present even when the system starts correctly with older kernels. > >> My machine runs on skylake cpu with z170 chipset and the latest bios. >> Any ideas on how to fix this? > > Not without first figuring out what bad vector is being received > by the APIC, which likely will involved quite a bit of debugging > and code instrumentation. Do you think that this could be caused by some sort of hardware/firmware issue? Thanks, J. > > Jan > ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
[Xen-devel] (XEN) APIC error on CPU0: 40(00)
Hi, i just build the latest 4.3.0 kernel and ran it on qubes-os with xen 4.4.3. I get this error just before the reboot: [(XEN) APIC error on CPU0: 40(00) (XEN) Resetting with ACPI MEMORY or I/O RESET_REG. I can also see some weird acpi-related messages on the log i attached, like: (XEN) ACPI: Invalid sleep control/status register data: 0:0x8:0x3 0:0x8:0x3 (XEN) ERST table was not found [3.608404] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150818/dswload-210) [3.608410] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20150818/psobject-227) [3.608439] ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while loading table (20150818/tbxfload-193) [3.619914] ACPI Error: 1 table load failures, 5 successful (20150818/tbxfload-214) [3.679113] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored [3.688942] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20150818/hwxface-580) [3.688948] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20150818/hwxface-580) [3.756027] PM-Timer failed consistency check (0xff) - aborting. With older kernels (like 3.12 or 4.2.1) i always see those messages but i'm able to boot without the acpi error. My machine runs on skylake cpu with z170 chipset and the latest bios. Any ideas on how to fix this? Thanks, John. Loading Xen 4.4.3 ... Loading Linux 4.3-0.pvops.qubes.x86_64 ... Xen 4.4.3-7.fc20 (XEN) Xen version 4.4.3 (user@) (gcc (GCC) 4.8.3 20140911 (Red Hat 4.8.3-7)) debug=n Mon Oct 19 16:28:51 UTC 2015 (XEN) Latest ChangeSet: (XEN) Bootloader: GRUB 2.00 (XEN) Command line: placeholder console=ttyS0 com1=115200,8n1 console=com1 dom0_mem=min:1024Mi loglvl=all apic_verbosity=debug e820-verbose=true xsave=0 iommu=verbose (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Initial Xen-e820 RAM map: (XEN) - 0009c800 (usable) (XEN) 0009c800 - 000a (reserved) (XEN) 000e - 0010 (reserved) (XEN) 0010 - 61984000 (usable) (XEN) 61984000 - 61985000 (ACPI NVS) (XEN) 61985000 - 619cf000 (reserved) (XEN) 619cf000 - 61a22000 (usable) (XEN) 61a22000 - 62127000 (reserved) (XEN) 62127000 - 66b96000 (usable) (XEN) 66b96000 - 677ab000 (reserved) (XEN) 677ab000 - 67f9a000 (ACPI NVS) (XEN) 67f9a000 - 67fff000 (ACPI data) (XEN) 67fff000 - 6800 (usable) (XEN) 0001 - 00089200 (usable) (XEN) 6800 - 6810 (reserved) (XEN) e000 - f000 (reserved) (XEN) fe00 - fe011000 (reserved) (XEN) fec0 - fec01000 (reserved) (XEN) fee0 - fee01000 (reserved) (XEN) ff00 - 0001 (reserved) (XEN) Checking MTRR ranges... (XEN) MTRR cap: 1d0a type: c06 (XEN) Xen-e820 RAM map: (XEN) - 0009c800 (usable) (XEN) 0009c800 - 000a (reserved) (XEN) 000e - 0010 (reserved) (XEN) 0010 - 61984000 (usable) (XEN) 61984000 - 61985000 (ACPI NVS) (XEN) 61985000 - 619cf000 (reserved) (XEN) 619cf000 - 61a22000 (usable) (XEN) 61a22000 - 62127000 (reserved) (XEN) 62127000 - 66b96000 (usable) (XEN) 66b96000 - 677ab000 (reserved) (XEN) 677ab000 - 67f9a000 (ACPI NVS) (XEN) 67f9a000 - 67fff000 (ACPI data) (XEN) 67fff000 - 6800 (usable) (XEN) 6800 - 6810 (reserved) (XEN) e000 - f000 (reserved) (XEN) fe00 - fe011000 (reserved) (XEN) fec0 - fec01000 (reserved) (XEN) fee0 - fee01000 (reserved) (XEN) ff00 - 0001 (reserved) (XEN) 0001 - 00089200 (usable) (XEN) ACPI: RSDP 000F05B0, 0024 (r2 ALASKA) (XEN) ACPI: XSDT 67A1F098, 00B4 (r1 ALASKA A M I 1072009 AMI 10013) (XEN) ACPI: FACP 67A41B30, 010C (r5 ALASKA A M I 1072009 AMI 10013) (XEN) ACPI: DSDT 67A1F1E8, 22943 (r2 ALASKA A M I 1072009 INTL 20120913) (XEN) ACPI: FACS 67F99F80, 0040 (XEN) ACPI: APIC 67A41C40, 00BC (r3 ALASKA A M I 1072009 AMI 10013) (XEN) ACPI: FPDT 67A41D00, 0044 (r1 ALASKA A M I 1072009 AMI 10013) (XEN) ACPI: FIDT 67A41D48, 009C (r1 ALASKA A M I 1072009 AMI 10013) (XEN) ACPI: MCFG 67A41DE8, 003C (r1 ALASKAA M I 1072009 MSFT 97) (XEN) ACPI: HPET 67A41E28, 0038 (r1 ALASKA
Re: [Xen-devel] (XEN) Fatal machine check
On 26/10/2015 13:04, John Doe wrote: > Hi, i'm getting this problem with linux 4.3.0-rcX branch. > Full log is attached. My hardware is based on intel skylake i7-6700k on > z170 chipset and it is working properly. It does boot correctly with > older kernels (3.12). > With mce=off on xen parameters it does boot unti during pci detection > where it hangs (see attached log). > > I tried with both xen 4.4.2 and 4.6.0 with the same effect > > [2.957615] VFS: Disk quotas d(XEN) Fatal machine check: MCE: Fatal > error happened on CPUs ff > (XEN) > (XEN) > (XEN) > (XEN)The processor has reported a hardware error which cannot > (XEN)be recovered from. Xen will now reboot the machine. > (XEN) mce.c:1533: Begin dump mc_info > (XEN) CPU0: Machine Check Exception:5 > (XEN) Bank 4: ba0011000402[ 0] > (XEN) CPU0: Machine Check Exception:5 > (XEN) Bank 4: ba0011000402[ 0] > (XEN) CPU1: Machine Check Exception:5 > (XEN) Bank 4: ba0011000402[ 0] > (XEN) CPU1: Machine Check Exception:5 > (XEN) Bank 4: ba0011000402[ 0] > (XEN) CPU2: Machine Check Exception:5 > (XEN) Bank 4: ba0011000402[ 0] > (XEN) CPU2: Machine Check Exception:5 > (XEN) Bank 4: ba0011000402[ 0] > (XEN) CPU3: Machine Check Exception:5 > (XEN) Bank 4: ba0011000402[ 0] > (XEN) CPU3: Machine Check Exception:5 > (XEN) Bank 4: ba0011000402[ 0] > (XEN) mce.c:1536: End dump mc_info, 8 mcinfo dumped > (XEN) > (XEN) > (XEN) Panic on CPU 0: > (XEN) HARDWARE ERROR > (XEN) > (XEN) > (XEN) Reboot in five seconds... > > Any help? > > Thanks, > John. > This looks to be related to intel HD Graphics 530, if I disable the integrated GPU the machine boots properly. J. Loading Xen 4.4.2 ... Loading Linux 4.3.0-1.pvops.qubes.x86_64 ... Loading initial ramdisk ... Xen 4.4.2-7.fc21 (XEN) Xen version 4.4.2 (user@) (gcc (GCC) 4.9.2 20150212 (Red Hat 4.9.2-6)) debug=n Tue Oct 20 14:48:15 CEST 2015 (XEN) Latest ChangeSet: (XEN) Bootloader: GRUB 2.00 (XEN) Command line: placeholder iommu=pt iommu=1 unrestricted_guest=1 msi=1 swiotlb=force console=ttyS0 com1=115200,8n1 console=com1 dom0_mem=min:1024Mi loglvl=all apic_verbosity=debug e820t (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Initial Xen-e820 RAM map: (XEN) - 0009c800 (usable) (XEN) 0009c800 - 000a (reserved) (XEN) 000e - 0010 (reserved) (XEN) 0010 - 63911000 (usable) (XEN) 63911000 - 63912000 (ACPI NVS) (XEN) 63912000 - 6395c000 (reserved) (XEN) 6395c000 - 639af000 (usable) (XEN) 639af000 - 640b4000 (reserved) (XEN) 640b4000 - 66b99000 (usable) (XEN) 66b99000 - 677ab000 (reserved) (XEN) 677ab000 - 67f9a000 (ACPI NVS) (XEN) 67f9a000 - 67fff000 (ACPI data) (XEN) 67fff000 - 6800 (usable) (XEN) 0001 - 00089200 (usable) (XEN) 6800 - 6810 (reserved) (XEN) e000 - f000 (reserved) (XEN) fe00 - fe011000 (reserved) (XEN) fec0 - fec01000 (reserved) (XEN) fee0 - fee01000 (reserved) (XEN) ff00 - 0001 (reserved) (XEN) Checking MTRR ranges... (XEN) MTRR cap: 1d0a type: c06 (XEN) Xen-e820 RAM map: (XEN) - 0009c800 (usable) (XEN) 0009c800 - 000a (reserved) (XEN) 000e - 0010 (reserved) (XEN) 0010 - 63911000 (usable) (XEN) 63911000 - 63912000 (ACPI NVS) (XEN) 63912000 - 6395c000 (reserved) (XEN) 6395c000 - 639af000 (usable) (XEN) 639af000 - 640b4000 (reserved) (XEN) 640b4000 - 66b99000 (usable) (XEN) 66b99000 - 677ab000 (reserved) (XEN) 677ab000 - 67f9a000 (ACPI NVS) (XEN) 67f9a000 - 67fff000 (ACPI data) (XEN) 67fff000 - 6800 (usable) (XEN) 6800 - 6810 (reserved) (XEN) e000 - f000 (reserved) (XEN) fe00 - fe011000 (reserved) (XEN) fec0 - fec01000 (reserved) (XEN) fee0
[Xen-devel] (XEN) Fatal machine check
Hi, i'm getting this problem with linux 4.3.0-rcX branch. Full log is attached. My hardware is based on intel skylake i7-6700k on z170 chipset and it is working properly. It does boot correctly with older kernels (3.12). With mce=off on xen parameters it does boot unti during pci detection where it hangs (see attached log). I tried with both xen 4.4.2 and 4.6.0 with the same effect [2.957615] VFS: Disk quotas d(XEN) Fatal machine check: MCE: Fatal error happened on CPUs ff (XEN) (XEN) (XEN) (XEN)The processor has reported a hardware error which cannot (XEN)be recovered from. Xen will now reboot the machine. (XEN) mce.c:1533: Begin dump mc_info (XEN) CPU0: Machine Check Exception:5 (XEN) Bank 4: ba0011000402[ 0] (XEN) CPU0: Machine Check Exception:5 (XEN) Bank 4: ba0011000402[ 0] (XEN) CPU1: Machine Check Exception:5 (XEN) Bank 4: ba0011000402[ 0] (XEN) CPU1: Machine Check Exception:5 (XEN) Bank 4: ba0011000402[ 0] (XEN) CPU2: Machine Check Exception:5 (XEN) Bank 4: ba0011000402[ 0] (XEN) CPU2: Machine Check Exception:5 (XEN) Bank 4: ba0011000402[ 0] (XEN) CPU3: Machine Check Exception:5 (XEN) Bank 4: ba0011000402[ 0] (XEN) CPU3: Machine Check Exception:5 (XEN) Bank 4: ba0011000402[ 0] (XEN) mce.c:1536: End dump mc_info, 8 mcinfo dumped (XEN) (XEN) (XEN) Panic on CPU 0: (XEN) HARDWARE ERROR (XEN) (XEN) (XEN) Reboot in five seconds... Any help? Thanks, John. Loading Xen 4.4.2 ... Loading Linux 4.3.0-1.pvops.qubes.x86_64 ... Loading initial ramdisk ... Xen 4.4.2-7.fc21 (XEN) Xen version 4.4.2 (user@) (gcc (GCC) 4.9.2 20150212 (Red Hat 4.9.2-6)) debug=n Tue Oct 20 14:48:15 CEST 2015 (XEN) Latest ChangeSet: (XEN) Bootloader: GRUB 2.00 (XEN) Command line: placeholder iommu=pt iommu=1 unrestricted_guest=1 msi=1 swiotlb=force console=ttyS0 com1=115200,8n1 console=com1 dom0_mem=min:1024Mi loglvl=all apic_verbosity=debug e820t (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Initial Xen-e820 RAM map: (XEN) - 0009c800 (usable) (XEN) 0009c800 - 000a (reserved) (XEN) 000e - 0010 (reserved) (XEN) 0010 - 63911000 (usable) (XEN) 63911000 - 63912000 (ACPI NVS) (XEN) 63912000 - 6395c000 (reserved) (XEN) 6395c000 - 639af000 (usable) (XEN) 639af000 - 640b4000 (reserved) (XEN) 640b4000 - 66b99000 (usable) (XEN) 66b99000 - 677ab000 (reserved) (XEN) 677ab000 - 67f9a000 (ACPI NVS) (XEN) 67f9a000 - 67fff000 (ACPI data) (XEN) 67fff000 - 6800 (usable) (XEN) 0001 - 00089200 (usable) (XEN) 6800 - 6810 (reserved) (XEN) e000 - f000 (reserved) (XEN) fe00 - fe011000 (reserved) (XEN) fec0 - fec01000 (reserved) (XEN) fee0 - fee01000 (reserved) (XEN) ff00 - 0001 (reserved) (XEN) Checking MTRR ranges... (XEN) MTRR cap: 1d0a type: c06 (XEN) Xen-e820 RAM map: (XEN) - 0009c800 (usable) (XEN) 0009c800 - 000a (reserved) (XEN) 000e - 0010 (reserved) (XEN) 0010 - 63911000 (usable) (XEN) 63911000 - 63912000 (ACPI NVS) (XEN) 63912000 - 6395c000 (reserved) (XEN) 6395c000 - 639af000 (usable) (XEN) 639af000 - 640b4000 (reserved) (XEN) 640b4000 - 66b99000 (usable) (XEN) 66b99000 - 677ab000 (reserved) (XEN) 677ab000 - 67f9a000 (ACPI NVS) (XEN) 67f9a000 - 67fff000 (ACPI data) (XEN) 67fff000 - 6800 (usable) (XEN) 6800 - 6810 (reserved) (XEN) e000 - f000 (reserved) (XEN) fe00 - fe011000 (reserved) (XEN) fec0 - fec01000 (reserved) (XEN) fee0 - fee01000 (reserved) (XEN) ff00 - 0001 (reserved) (XEN) 0001 - 00089200 (usable) (XEN) ACPI: RSDP 000F05B0, 0024 (r2 ALASKA) (XEN) ACPI: XSDT 67F59098, 00AC (r1 ALASKA A M I 1072009 AMI 10013) (XEN) ACPI: FACP 67F7BB20, 010C (r5 ALASKA A M I 1072009 AMI 10013) (XEN) ACPI: DSDT 67F591D8, 22943 (r2 ALASKA A M I 1072009 IN
Re: [Xen-devel] PROBLEM: kernel panic xsave_init
On 20/10/2015 16:27, Boris Ostrovsky wrote: > On 10/20/2015 09:43 AM, Jan Beulich wrote: > On 20.10.15 at 15:22, wrote: >>> The reason I think its this commit is that RAX, RDX and RCX look very >>> much like arguments to xsetbv (which xstate_enable_boot_cpu() executes) >>> and RAX value is 0x1f, which has two new bits that this commit defined. >> That would be the two MPX related bits, yet us (luckily) white listing >> leaf 7 in pv_cpuid(), it is quite easy to validate that we don't expose >> this feature to PV(H) guests. > > Oh, so something like > > cpuid=['0x7:ebx=x0xx'] > > (bit 14 as zero) for John to try then. > > > -boris > >> Sadly the story is different for HVM >> guests (where the leaf handling uses black listing), but the register >> dump here clearly points to a PV guest (or Dom0). >> >> Jan >> > Jan the dump is taken from serial connection to Dom0, it does crash during boot. I just tried with xen 4.6.0 and it booted properly without xsave=0. Running gdb against /proc/kcore, with a x/10x 0x81d58fad i just get null bytes, with both xen4.4.3 (xsave=0) and 4.6.0. Tomorrow i will send you the gdb output and i will try to run it during the boot process. J. ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Re: [Xen-devel] PROBLEM: kernel panic xsave_init
On 20/10/2015 11:51, Jan Beulich wrote:
>>>> On 19.10.15 at 18:25, wrote:
>> On 10/19/2015 06:16 AM, John Doe wrote:
>>>>> [0.00] general protection fault: [#1] SMP
>>>>> [0.00] Modules linked in:
>>>>> [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted
>> 4.1.9-6.pvops.qubes.x86_64 #1
>>>>> [0.00] Hardware name: To Be Filled By O.E.M. To Be Filled By
>> O.E.M./Z170 Extreme4, BIOS P1.80 09/18/2015
>>>>> [0.00] task: 81c154c0 ti: 81c0 task.ti:
>> 81c0
>>>>> [0.00] RIP: e030:[] []
>> xstate_enable_boot_cpu+0xde/0x288
>>>>> [0.00] RSP: e02b:81c03de8 EFLAGS: 00010046
>>>>> [0.00] RAX: 001f RBX: 0008 RCX:
>>
>>>>> [0.00] RDX: RSI: 001f RDI:
>> 00042660
>>
>>
>> It would be good to see what's at 81d58fad. My guess would be
>> that it's xsetbv.
>>
>> If it is then you probably want to make sure you are running hypervisor
>> that has commit e8121c54 ("x86/xsave: enable support for new ISA
>> extensions"). Looks like the first version that has it is 4.5 and you
>> seem to be running 4.4.2.
>>
>> Copying Jan to see if there are plans to backport this (probably not
>> since it's a new feature).
>
> Hmm, if there are features getting exposed that lead to crashes like
> this, then while we wouldn't normally backport enhancements, we
> may need to consider adding a one-off patch to hide respective
> features to that stable branch. But first we of course need to
> understand what is going on here.
>
> Jan
>
I will try with 4.6.0 asap, unfortunately the 4.4.2 image i have is not
built with debug enabled and i'm unable to run gdb at boot, i'm building
a new one right now.
If you need anything else please be very step-specific since i'm not
very practical at this.
Thank you,
John.
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
Re: [Xen-devel] PROBLEM: kernel panic xsave_init
On 19/10/2015 09:56, Ingo Molnar wrote: > > Please Cc: the Xen maintainers as this appears to be Xen specific. Also, > please > Cc: linux-ker...@vger.kernel.org. > > Thanks, > > Ingo > > * John Doe wrote: > >> Hello, >> I get a kernel panic on QubesOS 3.0 during boot with kernels newer than >> 3.12.40-2, i tried several versions until the latest 4.3.0-rc5. It does >> boot properly with xsave=0 parameter. >> I attached the full console log with the stack trace. >> >> My machine runs a new i7-6700k skylake CPU on z170 chipset. >> >> I hope it can help. >> >> John. >> >> >> > >> about to get started... >> [0.00] PAT configuration [0-7]: WB WT UC- UC WC WP UC UC >> [0.00] Initializing cgroup subsys cpuset >> [0.00] Initializing cgroup subsys cpu >> [0.00] Initializing cgroup subsys cpuacct >> [0.00] Linux version 4.1.9-6.pvops.qubes.x86_64 (user@release) (gcc >> version 4.8.3 20140911 (Red Hat 4.8.3-7) (GCC) ) #1 SMP Sat Oct 3 02:28:05 >> UTC 2015 >> [0.00] Command line: placeholder root=/dev/mapper/qubes_dom0-root ro >> console=tty0 console=ttyS0,115200n8 rd.lvm.lv=qubes_dom0/root >> rd.luks.uuid=luks-nope >> [0.00] Released 0 page(s) >> [0.00] e820: BIOS-provided physical RAM map: >> [0.00] Xen: [mem 0x-0x0009bfff] usable >> [0.00] Xen: [mem 0x0009c800-0x000f] reserved >> [0.00] Xen: [mem 0x0010-0x59f9afff] usable >> [0.00] Xen: [mem 0x59f9b000-0x59f9bfff] ACPI NVS >> [0.00] Xen: [mem 0x59f9c000-0x59fe5fff] reserved >> [0.00] Xen: [mem 0x59fe6000-0x5a038fff] usable >> [0.00] Xen: [mem 0x5a039000-0x5a75afff] reserved >> [0.00] Xen: [mem 0x5a75b000-0x66b92fff] usable >> [0.00] Xen: [mem 0x66b93000-0x677aafff] reserved >> [0.00] Xen: [mem 0x677ab000-0x67f99fff] ACPI NVS >> [0.00] Xen: [mem 0x67f9a000-0x67ffefff] ACPI data >> [0.00] Xen: [mem 0x67fff000-0x67ff] usable >> [0.00] Xen: [mem 0x6800-0x680f] reserved >> [0.00] Xen: [mem 0xe000-0xefff] reserved >> [0.00] Xen: [mem 0xfe00-0xfe010fff] reserved >> [0.00] Xen: [mem 0xfec0-0xfec00fff] reserved >> [0.00] Xen: [mem 0xfed9-0xfed91fff] reserved >> [0.00] Xen: [mem 0xfee0-0xfeef] reserved >> [0.00] Xen: [mem 0xff00-0x] reserved >> [0.00] Xen: [mem 0x0001-0x000891ff] usable >> [0.00] bootconsole [xenboot0] enabled >> [0.00] NX (Execute Disable) protection: active >> [0.00] SMBIOS 2.8 present. >> [0.00] Hypervisor detected: Xen >> [0.00] e820: last_pfn = 0x892000 max_arch_pfn = 0x4 >> [0.00] e820: last_pfn = 0x68000 max_arch_pfn = 0x4 >> [0.00] init_memory_mapping: [mem 0x-0x000f] >> [0.00] init_memory_mapping: [mem 0x7d520-0x7d53f] >> [0.00] init_memory_mapping: [mem 0x7c000-0x7d51f] >> [0.00] init_memory_mapping: [mem 0x7a000-0x7bfff] >> [0.00] init_memory_mapping: [mem 0x0010-0x59f9afff] >> [0.00] init_memory_mapping: [mem 0x59fe6000-0x5a038fff] >> [0.00] init_memory_mapping: [mem 0x5a75b000-0x66b92fff] >> [0.00] init_memory_mapping: [mem 0x67fff000-0x67ff] >> [0.00] init_memory_mapping: [mem 0x1-0x79fff] >> [0.00] init_memory_mapping: [mem 0x7d540-0x891ff] >> [0.00] RAMDISK: [mem 0x0800-0x0a815fff] >> [0.00] ACPI: Early table checksum verification disabled >> [0.00] ACPI: RSDP 0x000F05B0 24 (v02 ALASKA) >> [0.00] ACPI: XSDT 0x67A1F098 B4 (v01 ALASKA A M I >> 01072009 AMI 00010013) >> [0.00] ACPI: FACP 0x67A41B30 00010C (v05 ALASKA A M I >> 01072009 AMI 00010013) >> [0.00] ACPI BIOS Warning (bug): Incorrect checksum in table [FACP] - >> 0x15, should be 0x49 (20150410/tbprint-211) >> [0.00] ACPI: DSDT 0x67A1F1E8 022943 (v02 ALASKA A M I >> 01072009 INTL 20120913) >> [0.00] ACPI: FACS 0x67F99F80 40 >> [0.00
