* [Xen-devel] xen 4.13 + kernel 5.4.11 'APIC Error ... FATAL PAGE FAULT' on reboot? non-Xen reboot's ok.
@ 2020-01-15 16:52 PGNet Dev
2020-01-15 17:10 ` Andrew Cooper
0 siblings, 1 reply; 5+ messages in thread
From: PGNet Dev @ 2020-01-15 16:52 UTC (permalink / raw)
To: xen-devel
dev @distro suggested I post this here ...
I've a recently upgraded Xen & Kernel on
lsb_release -rd
Description: openSUSE Leap 15.1
Release: 15.1
Atm, I'm running
Xen 4.13.0_04
server, on EFI hardware + Intel Xeon E3 CPU, with kernel
5.4.11-24.g2d02eb4-default
It boots as always, with no issue
Welcome to GRUB!
Please press t to show the boot menu on this console
Xen 4.13.0_04-lp151.688 (c/s ) EFI loader
Using configuration file 'xen-4.13.0_04-lp151.688.cfg'
vmlinuz-5.4.11-24.g2d02eb4-default: 0x000000008b7c0000-0x000000008c04efb8
initrd-5.4.11-24.g2d02eb4-default: 0x000000008a4a5000-0x000000008b7bfe28
0x0000:0x00:0x19.0x0: ROM: 0x10000 bytes at 0x928a9018
0x0000:0x04:0x00.0x0: ROM: 0x8000 bytes at 0x928a0018
0x0000:0x10:0x00.0x0: ROM: 0x10800 bytes at 0x92885018
__ __
\ \/ /___ _ __
\ // _ \ '_ \
/ \ __/ | | |
/_/\_\___|_| |_|
_ _ _ _____ ___ ___ _ _ _ _ ____ _ __ ___ ___
| || | / |___ / / _ \ / _ \| || | | |_ __ / | ___|/ | / /_ ( _ ) ( _ )
| || |_ | | |_ \| | | | | | | | || |_ __| | '_ \| |___ \| || '_ \ / _ \ / _ \
|__ _|| |___) | |_| | | |_| |__ _|__| | |_) | |___) | || (_) | (_) | (_) |
|_|(_)_|____(_)___/___\___/ |_| |_| .__/|_|____/|_(_)___/ \___/ \___/
|_____| |_|
(XEN) [00000026c8dc8909] Xen version 4.13.0_04-lp151.688 (abuild@suse.de) (gcc (SUSE Linux) 9.2.1 20200109 [gcc-9-branch revi
sion 280039]) debug=n Wed Jan 8 11:43:04 UTC 2020
(XEN) [00000026cbd609dc] Latest ChangeSet:
(XEN) [00000026cc9505ea] Bootloader: EFI
(XEN) [00000026cd46f20f] Command line: dom0=pvh dom0-iommu=map-reserved dom0_mem=4016M,max:4096M bootscrub=false dom0_max_vcp
us=4 vga=gfx-1920x1080x16 com1=115200,8n1,pci console=com1,vga console_timestamps console_to_ring conring_size=64 sched=credit2 ucode=scan log_buf_len=16M loglvl=warning guest_loglvl=none/warning noreboot=false iommu=verbose sync_console=false
...
on exec of cmdline shutdown from shell,
shutdown -r now
the system DOES reboot, but first throws an APIC error -- only if running Xen, reboot with no-hypervisor has not probs
1st step, here's the current, relevant _log_ trace
...
[ OK ] Reached target Shutdown.
[ 343.932856] watchdog: watchdog0: watchdog did not stop!
[ 346.871303] watchdog: watchdog0: watchdog did not stop!
dracut Warning: Killing all remaining processes
mdadm: stopped /dev/md4
mdadm: stopped /dev/md3
mdadm: stopped /dev/md2
mdadm: stopped /dev/md1
mdadm: stopped /dev/md0
Rebooting.
[ 352.396918] reboot: Restarting system
(XEN) [2020-01-15 15:01:26] Hardware Dom0 shutdown: rebooting machine
(XEN) [2020-01-15 15:01:26] APIC error on CPU0: 40(00)
(XEN) [2020-01-15 15:01:26] ----[ Xen-4.13.0_04-lp151.688 x86_64 debug=n Not tainted ]----
(XEN) [2020-01-15 15:01:26] CPU: 0
(XEN) [2020-01-15 15:01:26] RIP: e008:[<0000000000000000>] 0000000000000000
(XEN) [2020-01-15 15:01:26] RFLAGS: 0000000000010202 CONTEXT: hypervisor
(XEN) [2020-01-15 15:01:26] rax: 0000000000000286 rbx: 0000000000000000 rcx: 0000000000000000
(XEN) [2020-01-15 15:01:26] rdx: 000000009e5ca7a0 rsi: 0000000000000000 rdi: 0000000000000000
(XEN) [2020-01-15 15:01:26] rbp: 0000000000000000 rsp: ffff83008ca2fa48 r8: ffff83008ca2fa90
(XEN) [2020-01-15 15:01:26] r9: ffff83008ca2fa80 r10: 0000000000000000 r11: 0000000000000000
(XEN) [2020-01-15 15:01:26] r12: 0000000000000000 r13: ffff83008ca2fb00 r14: ffff83008ca2ffff
(XEN) [2020-01-15 15:01:26] r15: 0000000000000000 cr0: 0000000080050033 cr4: 00000000001526e0
(XEN) [2020-01-15 15:01:26] cr3: 00000008492ed000 cr2: ffffffffeef3f286
(XEN) [2020-01-15 15:01:26] fsb: 0000000000000000 gsb: 0000000000000000 gss: 0000000000000000
(XEN) [2020-01-15 15:01:26] ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: e008
(XEN) [2020-01-15 15:01:26] Xen code around <0000000000000000> (0000000000000000) [fault on access]:
(XEN) [2020-01-15 15:01:26] -- -- -- -- -- -- -- -- <00> 80 00 f0 f3 ee 00 f0 c3 e2 00 f0 f3 ee 00 f0
(XEN) [2020-01-15 15:01:26] Xen stack trace from rsp=ffff83008ca2fa48:
(XEN) [2020-01-15 15:01:26] 000000009e5ca3c9 ffff82d08036681f ffff82d08036682b 0000000000000000
(XEN) [2020-01-15 15:01:26] 0000000000000000 ffff83008ca2fa88 0000000000000000 00000000001526e0
(XEN) [2020-01-15 15:01:26] ffff82d0802758cd 0000000000000286 0000000000000286 0000000000000000
(XEN) [2020-01-15 15:01:26] 000000009efe42f6 0000000000000000 0000000000000000 ffff83008ca2fb00
(XEN) [2020-01-15 15:01:26] ffff82d08036331b 0000000000152660 ffff82d0803636ae 0000000000000000
(XEN) [2020-01-15 15:01:26] ffff83008ca2fb48 0000000000000000 ffff82d080363688 000000008ca1f000
(XEN) [2020-01-15 15:01:26] ffff82d080937a98 000000fe00000000 ffff82d08029e41a 000000000000e008
(XEN) [2020-01-15 15:01:26] 0000000000000287 ffff830000000000 0000000000000000 0000000000000065
(XEN) [2020-01-15 15:01:26] 0000000000000000 ffff82d08029dd3c 000000008036682b 000082d08036681f
(XEN) [2020-01-15 15:01:26] 0000000000000000 ffff82d08093dd00 0000000000000000 0000000000000000
(XEN) [2020-01-15 15:01:26] 0000000000000000 ffff82d08029de17 ffff82d08023a742 ffff82d0809378c8
(XEN) [2020-01-15 15:01:26] ffff82d08093dd00 ffff82d08027ff48 ffff82d080000000 ffff83008ca2fd98
(XEN) [2020-01-15 15:01:26] ffff82d0000000fb ffff82d08036681f ffff82d08036682b ffff82d08036681f
(XEN) [2020-01-15 15:01:27] ffff82d08036682b ffff82d08036681f ffff82d08036682b 0000000000000000
(XEN) [2020-01-15 15:01:27] 0000000000000000 0000000000000000 0000000000000000 ffff83008ca2ffff
(XEN) [2020-01-15 15:01:27] 0000000000000000 ffff82d080366894 ffff82d08095e860 ffff830849340424
(XEN) [2020-01-15 15:01:27] ffff82d08095e820 ffff83008ca2fd98 ffff82d080823460 0000000000000002
(XEN) [2020-01-15 15:01:27] 0000000000000000 0000000000000000 0000000000000000 ffff83008ca2fd98
(XEN) [2020-01-15 15:01:27] 00000000000000c1 00000000000003f8 00000000000003fa ffff82d080823460
(XEN) [2020-01-15 15:01:27] 0000000000000004 000000fb00000000 ffff82d08024b590 000000000000e008
(XEN) [2020-01-15 15:01:27] Xen call trace:
(XEN) [2020-01-15 15:01:27] [<0000000000000000>] R 0000000000000000
(XEN) [2020-01-15 15:01:27] [<000000009e5ca3c9>] S 000000009e5ca3c9
(XEN) [2020-01-15 15:01:27] [<ffff82d08036681f>] S common_interrupt+0x8f/0x120
(XEN) [2020-01-15 15:01:27] [<ffff82d08036682b>] S common_interrupt+0x9b/0x120
(XEN) [2020-01-15 15:01:27] [<ffff82d0802758cd>] S arch/x86/flushtlb.c#pre_flush+0x3d/0x70
(XEN) [2020-01-15 15:01:27] [<ffff82d08036331b>] S arch/x86/efi/runtime.c#efi_rs_enter.part.0+0xfb/0x130
(XEN) [2020-01-15 15:01:27] [<ffff82d0803636ae>] S efi_reset_system+0x4e/0x90
(XEN) [2020-01-15 15:01:27] [<ffff82d080363688>] S efi_reset_system+0x28/0x90
(XEN) [2020-01-15 15:01:27] [<ffff82d08029e41a>] S smp_send_stop+0xba/0xc0
(XEN) [2020-01-15 15:01:27] [<ffff82d08029dd3c>] S machine_restart+0x1fc/0x2d0
(XEN) [2020-01-15 15:01:27] [<ffff82d08029de17>] S arch/x86/shutdown.c#__machine_restart+0x7/0x10
(XEN) [2020-01-15 15:01:27] [<ffff82d08023a742>] S smp_call_function_interrupt+0x52/0x90
(XEN) [2020-01-15 15:01:27] [<ffff82d08027ff48>] S do_IRQ+0x2d8/0x760
(XEN) [2020-01-15 15:01:27] [<ffff82d08036681f>] S common_interrupt+0x8f/0x120
(XEN) [2020-01-15 15:01:27] [<ffff82d08036682b>] S common_interrupt+0x9b/0x120
(XEN) [2020-01-15 15:01:27] [<ffff82d08036681f>] S common_interrupt+0x8f/0x120
(XEN) [2020-01-15 15:01:27] [<ffff82d08036682b>] S common_interrupt+0x9b/0x120
(XEN) [2020-01-15 15:01:27] [<ffff82d08036681f>] S common_interrupt+0x8f/0x120
(XEN) [2020-01-15 15:01:27] [<ffff82d08036682b>] S common_interrupt+0x9b/0x120
(XEN) [2020-01-15 15:01:27] [<ffff82d080366894>] S common_interrupt+0x104/0x120
(XEN) [2020-01-15 15:01:27] [<ffff82d08024b590>] S drivers/char/ns16550.c#ns16550_interrupt+0xc0/0xe0
(XEN) [2020-01-15 15:01:27] [<ffff82d08036681f>] S common_interrupt+0x8f/0x120
(XEN) [2020-01-15 15:01:27] [<ffff82d080280107>] S do_IRQ+0x497/0x760
(XEN) [2020-01-15 15:01:27] [<ffff82d08036681f>] S common_interrupt+0x8f/0x120
(XEN) [2020-01-15 15:01:27] [<ffff82d08036682b>] S common_interrupt+0x9b/0x120
(XEN) [2020-01-15 15:01:27] [<ffff82d08036681f>] S common_interrupt+0x8f/0x120
(XEN) [2020-01-15 15:01:27] [<ffff82d08036682b>] S common_interrupt+0x9b/0x120
(XEN) [2020-01-15 15:01:27] [<ffff82d080366894>] S common_interrupt+0x104/0x120
(XEN) [2020-01-15 15:01:27] [<ffff82d0802d74dd>] S arch/x86/cpu/mwait-idle.c#mwait_idle+0x25d/0x3c0
(XEN) [2020-01-15 15:01:27] [<ffff82d0802d74d8>] S arch/x86/cpu/mwait-idle.c#mwait_idle+0x258/0x3c0
(XEN) [2020-01-15 15:01:27] [<ffff82d08023cca9>] S common/tasklet.c#tasklet_softirq_action+0x39/0x60
(XEN) [2020-01-15 15:01:27] [<ffff82d0802700ec>] S arch/x86/domain.c#idle_loop+0x8c/0xa0
(XEN) [2020-01-15 15:01:27]
(XEN) [2020-01-15 15:01:27] Pagetable walk from ffffffffeef3f286:
(XEN) [2020-01-15 15:01:27] L4[0x1ff] = 0000000000000000 ffffffffffffffff
(XEN) [2020-01-15 15:01:27]
(XEN) [2020-01-15 15:01:27] ****************************************
(XEN) [2020-01-15 15:01:27] Panic on CPU 0:
(XEN) [2020-01-15 15:01:27] FATAL PAGE FAULT
(XEN) [2020-01-15 15:01:27] [error_code=0002]
(XEN) [2020-01-15 15:01:27] Faulting linear address: ffffffffeef3f286
(XEN) [2020-01-15 15:01:27] ****************************************
(XEN) [2020-01-15 15:01:27]
(XEN) [2020-01-15 15:01:27] Reboot in five seconds...
...
Is this a known/fixable issue?
If more, specific info is needed here, pls let me know what to provide.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Xen-devel] xen 4.13 + kernel 5.4.11 'APIC Error ... FATAL PAGE FAULT' on reboot? non-Xen reboot's ok.
2020-01-15 16:52 [Xen-devel] xen 4.13 + kernel 5.4.11 'APIC Error ... FATAL PAGE FAULT' on reboot? non-Xen reboot's ok PGNet Dev
@ 2020-01-15 17:10 ` Andrew Cooper
2020-01-15 17:19 ` PGNet Dev
0 siblings, 1 reply; 5+ messages in thread
From: Andrew Cooper @ 2020-01-15 17:10 UTC (permalink / raw)
To: pgnet.dev, xen-devel
On 15/01/2020 16:52, PGNet Dev wrote:
> dev @distro suggested I post this here ...
>
> I've a recently upgraded Xen & Kernel on
>
> lsb_release -rd
> Description: openSUSE Leap 15.1
> Release: 15.1
>
> Atm, I'm running
>
> Xen 4.13.0_04
>
> server, on EFI hardware + Intel Xeon E3 CPU, with kernel
>
> 5.4.11-24.g2d02eb4-default
>
> It boots as always, with no issue
>
> Welcome to GRUB!
>
> Please press t to show the boot menu on this console
> Xen 4.13.0_04-lp151.688 (c/s ) EFI loader
> Using configuration file 'xen-4.13.0_04-lp151.688.cfg'
> vmlinuz-5.4.11-24.g2d02eb4-default: 0x000000008b7c0000-0x000000008c04efb8
> initrd-5.4.11-24.g2d02eb4-default: 0x000000008a4a5000-0x000000008b7bfe28
> 0x0000:0x00:0x19.0x0: ROM: 0x10000 bytes at 0x928a9018
> 0x0000:0x04:0x00.0x0: ROM: 0x8000 bytes at 0x928a0018
> 0x0000:0x10:0x00.0x0: ROM: 0x10800 bytes at 0x92885018
> __ __
> \ \/ /___ _ __
> \ // _ \ '_ \
> / \ __/ | | |
> /_/\_\___|_| |_|
>
> _ _ _ _____ ___ ___ _ _ _ _ ____ _ __ ___ ___
> | || | / |___ / / _ \ / _ \| || | | |_ __ / | ___|/ | / /_ ( _ ) ( _ )
> | || |_ | | |_ \| | | | | | | | || |_ __| | '_ \| |___ \| || '_ \ / _ \ / _ \
> |__ _|| |___) | |_| | | |_| |__ _|__| | |_) | |___) | || (_) | (_) | (_) |
> |_|(_)_|____(_)___/___\___/ |_| |_| .__/|_|____/|_(_)___/ \___/ \___/
> |_____| |_|
> (XEN) [00000026c8dc8909] Xen version 4.13.0_04-lp151.688 (abuild@suse.de) (gcc (SUSE Linux) 9.2.1 20200109 [gcc-9-branch revi
> sion 280039]) debug=n Wed Jan 8 11:43:04 UTC 2020
> (XEN) [00000026cbd609dc] Latest ChangeSet:
> (XEN) [00000026cc9505ea] Bootloader: EFI
> (XEN) [00000026cd46f20f] Command line: dom0=pvh dom0-iommu=map-reserved dom0_mem=4016M,max:4096M bootscrub=false dom0_max_vcp
> us=4 vga=gfx-1920x1080x16 com1=115200,8n1,pci console=com1,vga console_timestamps console_to_ring conring_size=64 sched=credit2 ucode=scan log_buf_len=16M loglvl=warning guest_loglvl=none/warning noreboot=false iommu=verbose sync_console=false
> ...
>
> on exec of cmdline shutdown from shell,
>
> shutdown -r now
>
> the system DOES reboot, but first throws an APIC error -- only if running Xen, reboot with no-hypervisor has not probs
>
> 1st step, here's the current, relevant _log_ trace
>
> ...
> [ OK ] Reached target Shutdown.
> [ 343.932856] watchdog: watchdog0: watchdog did not stop!
> [ 346.871303] watchdog: watchdog0: watchdog did not stop!
> dracut Warning: Killing all remaining processes
> mdadm: stopped /dev/md4
> mdadm: stopped /dev/md3
> mdadm: stopped /dev/md2
> mdadm: stopped /dev/md1
> mdadm: stopped /dev/md0
> Rebooting.
> [ 352.396918] reboot: Restarting system
> (XEN) [2020-01-15 15:01:26] Hardware Dom0 shutdown: rebooting machine
> (XEN) [2020-01-15 15:01:26] APIC error on CPU0: 40(00)
> (XEN) [2020-01-15 15:01:26] ----[ Xen-4.13.0_04-lp151.688 x86_64 debug=n Not tainted ]----
> (XEN) [2020-01-15 15:01:26] CPU: 0
> (XEN) [2020-01-15 15:01:26] RIP: e008:[<0000000000000000>] 0000000000000000
> (XEN) [2020-01-15 15:01:26] RFLAGS: 0000000000010202 CONTEXT: hypervisor
> (XEN) [2020-01-15 15:01:26] rax: 0000000000000286 rbx: 0000000000000000 rcx: 0000000000000000
> (XEN) [2020-01-15 15:01:26] rdx: 000000009e5ca7a0 rsi: 0000000000000000 rdi: 0000000000000000
> (XEN) [2020-01-15 15:01:26] rbp: 0000000000000000 rsp: ffff83008ca2fa48 r8: ffff83008ca2fa90
> (XEN) [2020-01-15 15:01:26] r9: ffff83008ca2fa80 r10: 0000000000000000 r11: 0000000000000000
> (XEN) [2020-01-15 15:01:26] r12: 0000000000000000 r13: ffff83008ca2fb00 r14: ffff83008ca2ffff
> (XEN) [2020-01-15 15:01:26] r15: 0000000000000000 cr0: 0000000080050033 cr4: 00000000001526e0
> (XEN) [2020-01-15 15:01:26] cr3: 00000008492ed000 cr2: ffffffffeef3f286
> (XEN) [2020-01-15 15:01:26] fsb: 0000000000000000 gsb: 0000000000000000 gss: 0000000000000000
> (XEN) [2020-01-15 15:01:26] ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: e008
> (XEN) [2020-01-15 15:01:26] Xen code around <0000000000000000> (0000000000000000) [fault on access]:
> (XEN) [2020-01-15 15:01:26] -- -- -- -- -- -- -- -- <00> 80 00 f0 f3 ee 00 f0 c3 e2 00 f0 f3 ee 00 f0
> (XEN) [2020-01-15 15:01:26] Xen stack trace from rsp=ffff83008ca2fa48:
> (XEN) [2020-01-15 15:01:26] 000000009e5ca3c9 ffff82d08036681f ffff82d08036682b 0000000000000000
> (XEN) [2020-01-15 15:01:26] 0000000000000000 ffff83008ca2fa88 0000000000000000 00000000001526e0
> (XEN) [2020-01-15 15:01:26] ffff82d0802758cd 0000000000000286 0000000000000286 0000000000000000
> (XEN) [2020-01-15 15:01:26] 000000009efe42f6 0000000000000000 0000000000000000 ffff83008ca2fb00
> (XEN) [2020-01-15 15:01:26] ffff82d08036331b 0000000000152660 ffff82d0803636ae 0000000000000000
> (XEN) [2020-01-15 15:01:26] ffff83008ca2fb48 0000000000000000 ffff82d080363688 000000008ca1f000
> (XEN) [2020-01-15 15:01:26] ffff82d080937a98 000000fe00000000 ffff82d08029e41a 000000000000e008
> (XEN) [2020-01-15 15:01:26] 0000000000000287 ffff830000000000 0000000000000000 0000000000000065
> (XEN) [2020-01-15 15:01:26] 0000000000000000 ffff82d08029dd3c 000000008036682b 000082d08036681f
> (XEN) [2020-01-15 15:01:26] 0000000000000000 ffff82d08093dd00 0000000000000000 0000000000000000
> (XEN) [2020-01-15 15:01:26] 0000000000000000 ffff82d08029de17 ffff82d08023a742 ffff82d0809378c8
> (XEN) [2020-01-15 15:01:26] ffff82d08093dd00 ffff82d08027ff48 ffff82d080000000 ffff83008ca2fd98
> (XEN) [2020-01-15 15:01:26] ffff82d0000000fb ffff82d08036681f ffff82d08036682b ffff82d08036681f
> (XEN) [2020-01-15 15:01:27] ffff82d08036682b ffff82d08036681f ffff82d08036682b 0000000000000000
> (XEN) [2020-01-15 15:01:27] 0000000000000000 0000000000000000 0000000000000000 ffff83008ca2ffff
> (XEN) [2020-01-15 15:01:27] 0000000000000000 ffff82d080366894 ffff82d08095e860 ffff830849340424
> (XEN) [2020-01-15 15:01:27] ffff82d08095e820 ffff83008ca2fd98 ffff82d080823460 0000000000000002
> (XEN) [2020-01-15 15:01:27] 0000000000000000 0000000000000000 0000000000000000 ffff83008ca2fd98
> (XEN) [2020-01-15 15:01:27] 00000000000000c1 00000000000003f8 00000000000003fa ffff82d080823460
> (XEN) [2020-01-15 15:01:27] 0000000000000004 000000fb00000000 ffff82d08024b590 000000000000e008
> (XEN) [2020-01-15 15:01:27] Xen call trace:
> (XEN) [2020-01-15 15:01:27] [<0000000000000000>] R 0000000000000000
> (XEN) [2020-01-15 15:01:27] [<000000009e5ca3c9>] S 000000009e5ca3c9
> (XEN) [2020-01-15 15:01:27] [<ffff82d08036681f>] S common_interrupt+0x8f/0x120
> (XEN) [2020-01-15 15:01:27] [<ffff82d08036682b>] S common_interrupt+0x9b/0x120
> (XEN) [2020-01-15 15:01:27] [<ffff82d0802758cd>] S arch/x86/flushtlb.c#pre_flush+0x3d/0x70
> (XEN) [2020-01-15 15:01:27] [<ffff82d08036331b>] S arch/x86/efi/runtime.c#efi_rs_enter.part.0+0xfb/0x130
> (XEN) [2020-01-15 15:01:27] [<ffff82d0803636ae>] S efi_reset_system+0x4e/0x90
> (XEN) [2020-01-15 15:01:27] [<ffff82d080363688>] S efi_reset_system+0x28/0x90
> (XEN) [2020-01-15 15:01:27] [<ffff82d08029e41a>] S smp_send_stop+0xba/0xc0
> (XEN) [2020-01-15 15:01:27] [<ffff82d08029dd3c>] S machine_restart+0x1fc/0x2d0
> (XEN) [2020-01-15 15:01:27] [<ffff82d08029de17>] S arch/x86/shutdown.c#__machine_restart+0x7/0x10
> (XEN) [2020-01-15 15:01:27] [<ffff82d08023a742>] S smp_call_function_interrupt+0x52/0x90
> (XEN) [2020-01-15 15:01:27] [<ffff82d08027ff48>] S do_IRQ+0x2d8/0x760
> (XEN) [2020-01-15 15:01:27] [<ffff82d08036681f>] S common_interrupt+0x8f/0x120
> (XEN) [2020-01-15 15:01:27] [<ffff82d08036682b>] S common_interrupt+0x9b/0x120
> (XEN) [2020-01-15 15:01:27] [<ffff82d08036681f>] S common_interrupt+0x8f/0x120
> (XEN) [2020-01-15 15:01:27] [<ffff82d08036682b>] S common_interrupt+0x9b/0x120
> (XEN) [2020-01-15 15:01:27] [<ffff82d08036681f>] S common_interrupt+0x8f/0x120
> (XEN) [2020-01-15 15:01:27] [<ffff82d08036682b>] S common_interrupt+0x9b/0x120
> (XEN) [2020-01-15 15:01:27] [<ffff82d080366894>] S common_interrupt+0x104/0x120
> (XEN) [2020-01-15 15:01:27] [<ffff82d08024b590>] S drivers/char/ns16550.c#ns16550_interrupt+0xc0/0xe0
> (XEN) [2020-01-15 15:01:27] [<ffff82d08036681f>] S common_interrupt+0x8f/0x120
> (XEN) [2020-01-15 15:01:27] [<ffff82d080280107>] S do_IRQ+0x497/0x760
> (XEN) [2020-01-15 15:01:27] [<ffff82d08036681f>] S common_interrupt+0x8f/0x120
> (XEN) [2020-01-15 15:01:27] [<ffff82d08036682b>] S common_interrupt+0x9b/0x120
> (XEN) [2020-01-15 15:01:27] [<ffff82d08036681f>] S common_interrupt+0x8f/0x120
> (XEN) [2020-01-15 15:01:27] [<ffff82d08036682b>] S common_interrupt+0x9b/0x120
> (XEN) [2020-01-15 15:01:27] [<ffff82d080366894>] S common_interrupt+0x104/0x120
> (XEN) [2020-01-15 15:01:27] [<ffff82d0802d74dd>] S arch/x86/cpu/mwait-idle.c#mwait_idle+0x25d/0x3c0
> (XEN) [2020-01-15 15:01:27] [<ffff82d0802d74d8>] S arch/x86/cpu/mwait-idle.c#mwait_idle+0x258/0x3c0
> (XEN) [2020-01-15 15:01:27] [<ffff82d08023cca9>] S common/tasklet.c#tasklet_softirq_action+0x39/0x60
> (XEN) [2020-01-15 15:01:27] [<ffff82d0802700ec>] S arch/x86/domain.c#idle_loop+0x8c/0xa0
> (XEN) [2020-01-15 15:01:27]
> (XEN) [2020-01-15 15:01:27] Pagetable walk from ffffffffeef3f286:
> (XEN) [2020-01-15 15:01:27] L4[0x1ff] = 0000000000000000 ffffffffffffffff
> (XEN) [2020-01-15 15:01:27]
> (XEN) [2020-01-15 15:01:27] ****************************************
> (XEN) [2020-01-15 15:01:27] Panic on CPU 0:
> (XEN) [2020-01-15 15:01:27] FATAL PAGE FAULT
> (XEN) [2020-01-15 15:01:27] [error_code=0002]
> (XEN) [2020-01-15 15:01:27] Faulting linear address: ffffffffeef3f286
> (XEN) [2020-01-15 15:01:27] ****************************************
> (XEN) [2020-01-15 15:01:27]
> (XEN) [2020-01-15 15:01:27] Reboot in five seconds...
> ...
>
>
> Is this a known/fixable issue?
The APIC errors aren't fatal. They need looking into and addressing in
due course.
The real crash is EFI firmware falling over a NULL pointer which is
wildly known issue. Fixing it requires following the Linux approach
which is to not use EFI reboot unless absolutely necessary.
You can work around it with reboot=a on the command line, but actually
fixing this in Xen is probably never going to happen because I've lost
interest in trying to arguing that default behaviour like the above is a
bad thing which we should code around.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Xen-devel] xen 4.13 + kernel 5.4.11 'APIC Error ... FATAL PAGE FAULT' on reboot? non-Xen reboot's ok.
2020-01-15 17:10 ` Andrew Cooper
@ 2020-01-15 17:19 ` PGNet Dev
2020-01-15 17:21 ` Andrew Cooper
0 siblings, 1 reply; 5+ messages in thread
From: PGNet Dev @ 2020-01-15 17:19 UTC (permalink / raw)
To: Andrew Cooper, xen-devel
hi
On 1/15/20 9:10 AM, Andrew Cooper wrote:
>> Is this a known/fixable issue?
>
> The APIC errors aren't fatal. They need looking into and addressing in
> due course.
>
> The real crash is EFI firmware falling over a NULL pointer which is
> wildly known issue. Fixing it requires following the Linux approach
> which is to not use EFI reboot unless absolutely necessary.
>
> You can work around it with reboot=a on the command line, but actually
> fixing this in Xen is probably never going to happen because I've lost
> interest in trying to arguing that default behaviour like the above is a
> bad thing which we should code around.
currently, here,
cat /proc/cmdline
root=/dev/mapper/VG0-ROOT softlevel=xen rd.shell mds=full l1tf=flush rd.debug=0 rd.udev.log_priority=debug rd.auto=1 dolvm lvmwait=/dev/mapper/VG0-ROOT root=/dev/mapper/VG0-ROOT rootfstype=ext4 rootflags=journal_checksum noresume nomodeset nouveau.modeset=1 video=vesa:off video=efifb:1024x768 xencons=xvc console=tty0 console=hvc0 pcie_aspm=off mce=off fsck.mode=skip fsck.repair=preen reboot=acpi clocksource=xen intel_iommu=on apparmor=0 plymouth.enable=0 scsi_mod.use_blk_mq=1 elevator=mq-deadline cpuidle cpufreq=xen:ondemand net.ifnames=1 biosdevname=0 showopts noquiet log_buf_len=10M print_fatal_signals=1 systemd.log_level=info systemd.log_target=kmsg earlyprintk=xen,keep audit=0
note the
reboot=acpi
already there.
something else I'm missing, perhaps?
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Xen-devel] xen 4.13 + kernel 5.4.11 'APIC Error ... FATAL PAGE FAULT' on reboot? non-Xen reboot's ok.
2020-01-15 17:19 ` PGNet Dev
@ 2020-01-15 17:21 ` Andrew Cooper
2020-01-15 17:43 ` PGNet Dev
0 siblings, 1 reply; 5+ messages in thread
From: Andrew Cooper @ 2020-01-15 17:21 UTC (permalink / raw)
To: pgnet.dev, xen-devel
On 15/01/2020 17:19, PGNet Dev wrote:
> hi
>
> On 1/15/20 9:10 AM, Andrew Cooper wrote:
>>> Is this a known/fixable issue?
>> The APIC errors aren't fatal. They need looking into and addressing in
>> due course.
>>
>> The real crash is EFI firmware falling over a NULL pointer which is
>> wildly known issue. Fixing it requires following the Linux approach
>> which is to not use EFI reboot unless absolutely necessary.
>>
>> You can work around it with reboot=a on the command line, but actually
>> fixing this in Xen is probably never going to happen because I've lost
>> interest in trying to arguing that default behaviour like the above is a
>> bad thing which we should code around.
> currently, here,
>
> cat /proc/cmdline
> root=/dev/mapper/VG0-ROOT softlevel=xen rd.shell mds=full l1tf=flush rd.debug=0 rd.udev.log_priority=debug rd.auto=1 dolvm lvmwait=/dev/mapper/VG0-ROOT root=/dev/mapper/VG0-ROOT rootfstype=ext4 rootflags=journal_checksum noresume nomodeset nouveau.modeset=1 video=vesa:off video=efifb:1024x768 xencons=xvc console=tty0 console=hvc0 pcie_aspm=off mce=off fsck.mode=skip fsck.repair=preen reboot=acpi clocksource=xen intel_iommu=on apparmor=0 plymouth.enable=0 scsi_mod.use_blk_mq=1 elevator=mq-deadline cpuidle cpufreq=xen:ondemand net.ifnames=1 biosdevname=0 showopts noquiet log_buf_len=10M print_fatal_signals=1 systemd.log_level=info systemd.log_target=kmsg earlyprintk=xen,keep audit=0
>
> note the
>
> reboot=acpi
>
> already there.
>
> something else I'm missing, perhaps?
That is the command line for dom0 which is a VM. You need the Xen
hypervisor command line.
You'll need to edit xen-4.13.0_04-lp151.688.cfg which will be somewhere
on the ESP (wherever that is mounted in an openSUSE system).
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Xen-devel] xen 4.13 + kernel 5.4.11 'APIC Error ... FATAL PAGE FAULT' on reboot? non-Xen reboot's ok.
2020-01-15 17:21 ` Andrew Cooper
@ 2020-01-15 17:43 ` PGNet Dev
0 siblings, 0 replies; 5+ messages in thread
From: PGNet Dev @ 2020-01-15 17:43 UTC (permalink / raw)
To: Andrew Cooper, xen-devel
On 1/15/20 9:21 AM, Andrew Cooper wrote:
> That is the command line for dom0 which is a VM. You need the Xen
> hypervisor command line.
thx. done.
> You'll need to edit xen-4.13.0_04-lp151.688.cfg which will be somewhere
> on the ESP (wherever that is mounted in an openSUSE system).
verifying,
cat /boot/efi/EFI/opensuse/xen-4.13.0_04-lp151.688.cfg
[global]
[config.1]
options=dom0=pvh ... reboot=a
kernel=...
now, on restart,
...
[ OK ] Reached target Shutdown.
[ 137.682171] watchdog: watchdog0: watchdog did not stop!
[ 139.373683] watchdog: watchdog0: watchdog did not stop!
dracut Warning: Killing all remaining processes
mdadm: stopped /dev/md4
mdadm: stopped /dev/md3
mdadm: stopped /dev/md2
mdadm: stopped /dev/md1
mdadm: stopped /dev/md0
Rebooting.
[ 144.908520] reboot: Restarting system
(XEN) [2020-01-15 17:38:25] Hardware Dom0 shutdown: rebooting machine
(XEN) [2020-01-15 17:38:25] APIC error on CPU0: 40(00)
(XEN) [2020-01-15 17:38:25] Resetting with ACPI MEMORY or I/O RESET_REG.
and reboot proceeds ...
the error's still there, but without the trace/noise
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2020-01-15 17:44 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-01-15 16:52 [Xen-devel] xen 4.13 + kernel 5.4.11 'APIC Error ... FATAL PAGE FAULT' on reboot? non-Xen reboot's ok PGNet Dev
2020-01-15 17:10 ` Andrew Cooper
2020-01-15 17:19 ` PGNet Dev
2020-01-15 17:21 ` Andrew Cooper
2020-01-15 17:43 ` PGNet Dev
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.