Bug#914951: 4.19.5 fails to boot as Xen dom0
On 11/30/18 10:46 PM, Hans van Kranenburg wrote: > On 11/29/18 2:38 AM, Hans van Kranenburg wrote: >> On 11/29/18 1:20 AM, Hans van Kranenburg wrote: >>> Package: src:linux >>> Version: 4.19.5-1~exp1 >>> Severity: normal >>> >>> Hi, >>> >>> Latest 4.19 upload fails to boot as Xen dom0. >> >> Copy at >> https://lists.xenproject.org/archives/html/xen-devel/2018-11/msg03313.html >> >> [...] > > A fix has been written and tested: > > https://lists.xenproject.org/archives/html/xen-devel/2018-11/msg03570.html > > I tested it on top of 4.19.5-1~exp1. > > I expect the first of those two patches (the actual fix) to show up in a > later 4.19. Since next upload seems to be targeted at unstable, we should have this fix already: https://salsa.debian.org/kernel-team/linux/merge_requests/82 Hans
Bug#914951: 4.19.5 fails to boot as Xen dom0
On 11/29/18 2:38 AM, Hans van Kranenburg wrote: > On 11/29/18 1:20 AM, Hans van Kranenburg wrote: >> Package: src:linux >> Version: 4.19.5-1~exp1 >> Severity: normal >> >> Hi, >> >> Latest 4.19 upload fails to boot as Xen dom0. > > Copy at > https://lists.xenproject.org/archives/html/xen-devel/2018-11/msg03313.html > > [...] A fix has been written and tested: https://lists.xenproject.org/archives/html/xen-devel/2018-11/msg03570.html I tested it on top of 4.19.5-1~exp1. I expect the first of those two patches (the actual fix) to show up in a later 4.19. Hans
Bug#914951: 4.19.5 fails to boot as Xen dom0
On 11/29/18 1:20 AM, Hans van Kranenburg wrote: > Package: src:linux > Version: 4.19.5-1~exp1 > Severity: normal > > Hi, > > Latest 4.19 upload fails to boot as Xen dom0. Copy at https://lists.xenproject.org/archives/html/xen-devel/2018-11/msg03313.html But at least if someone else would also report or search for it, we have this one to point to. :) > Attached are two serial console output logs. One is starting with Xen > 4.11 (from debian unstable) as dom0, and the other one without Xen. > > [2.085543] BUG: unable to handle kernel paging request at > 888d9fffc000 > [2.085610] PGD 200c067 P4D 200c067 PUD 0 > [2.085674] Oops: [#1] SMP NOPTI > [2.085736] CPU: 1 PID: 1 Comm: swapper/0 Not tainted > 4.19.0-trunk-amd64 #1 Debian 4.19.5-1~exp1+pvh1 Ehm, paste fail for this snippet, this is from my 4.19.5-1~exp1+pvh1 with extra Xen (domU) PVH patches. However, the full attached log is from 4.19.5-1~exp1 which fails in exactly the same way. > [2.085823] Hardware name: HP ProLiant DL360 G7, BIOS P68 05/21/2018 > [2.085895] RIP: e030:ptdump_walk_pgd_level_core+0x1fd/0x490 > [...] > > The pti=off setting on the PV dom0 kernel is left behind from the time > when 4.9 failed to boot as Xen dom0 because of the bug handling that. -- Hans van Kranenburg
Bug#914951: 4.19.5 fails to boot as Xen dom0
Package: src:linux Version: 4.19.5-1~exp1 Severity: normal Hi, Latest 4.19 upload fails to boot as Xen dom0. Attached are two serial console output logs. One is starting with Xen 4.11 (from debian unstable) as dom0, and the other one without Xen. [2.085543] BUG: unable to handle kernel paging request at 888d9fffc000 [2.085610] PGD 200c067 P4D 200c067 PUD 0 [2.085674] Oops: [#1] SMP NOPTI [2.085736] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.19.0-trunk-amd64 #1 Debian 4.19.5-1~exp1+pvh1 [2.085823] Hardware name: HP ProLiant DL360 G7, BIOS P68 05/21/2018 [2.085895] RIP: e030:ptdump_walk_pgd_level_core+0x1fd/0x490 [...] The pti=off setting on the PV dom0 kernel is left behind from the time when 4.9 failed to boot as Xen dom0 because of the bug handling that. -- Hans van Kranenburg Loading Linux 4.19.0-trunk-amd64 ...L oading initial ramdisk ... Loading initial ramdisk ...L [0.00] Linux version 4.19.0-trunk-amd64 (debian-ker...@lists.debian.org) (gcc version 8.2.0 (Debian 8.2.0-10)) #1 SMP Debian 4.19.5-1~exp1 (2018-11-27) [ 0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-trunk-amd64 root=UUID=f6c5313c-c1b7-4491-b017-e1512d716979 ro console=ttyS1 pti=off [0.00] x86/fpu: x87 FPU will use FXSAVE [0.00] BIOS-provided physical RAM map: [ 0.00] BIOS-e820: [mem 0x-0x0009f3ff] usable [0.00] BIOS-e820: [mem 0x0009f400-0x0009] reserved [0.00] BIOS-e820: [mem 0x000f-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0xdf62efff] usable [0.00] BIOS-e820: [mem 0xdf62f000-0xdf63bfff] ACPI data [0.00] BIOS-e820: [mem 0xdf63c000-0xdf63cfff] usable [0.00] BIOS-e820: [mem 0xdf63d000-0xe3ff] reserved [0.00] BIOS-e820: [mem 0xfec0-0xfee0] reserved [0.00] BIOS-e820: [mem 0xff80-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x001b1fffefff] usable [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.7 present. [0.00] DMI: HP ProLiant DL360 G7, BIOS P68 05/21/2018 [0.00] tsc: Fast TSC calibration using PIT [0.00] tsc: Detected 2666.735 MHz processor [0.002284] last_pfn = 0x1b1 max_arch_pfn = 0x4 [0.003585] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [0.003975] last_pfn = 0xdf63d max_arch_pfn = 0x4 [0.008526] found SMP MP-table at [mem 0x000f4f80-0x000f4f8f] mapped at [(ptrval)] [0.008604] Kernel/User page tables isolation: disabled on command line. [0.008605] Using GB pages for direct mapping [0.008850] RAMDISK: [mem 0x349d5000-0x364e1fff] [0.008855] ACPI: Early table checksum verification disabled [0.008922] ACPI: RSDP 0x000F4F00 024 (v02 HP) [0.008925] ACPI: XSDT 0xDF630140 B4 (v01 HP ProLiant 0002 �? 162E) [0.008931] ACPI: FACP 0xDF630240 F4 (v03 HP ProLiant 0002 �? 162E) [0.008935] ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aControlBlock: 32, using default 16 (20180810/tbfadt-674) [0.008938] ACPI BIOS Warning (bug): Invalid length for FADT/Pm2ControlBlock: 32, using default 8 (20180810/tbfadt-674) [0.008941] ACPI: DSDT 0xDF630340 0020BD (v01 HP DSDT 0001 INTL 20030228) [0.008945] ACPI: FACS 0xDF62F100 40 [0.008948] ACPI: FACS 0xDF62F100 40 [0.008951] ACPI: SPCR 0xDF62F140 50 (v01 HP SPCRRBSU 0001 �? 162E) [0.008954] ACPI: MCFG 0xDF62F1C0 3C (v01 HP ProLiant 0001 ) [0.008958] ACPI: HPET 0xDF62F200 38 (v01 HP ProLiant 0002 �? 162E) [0.008961] ACPI:
