Re: [Xen-devel] xen 4.13 + kernel 5.4.11 'APIC Error ... FATAL PAGE FAULT' on reboot? non-Xen reboot's ok.
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
Re: [Xen-devel] xen 4.13 + kernel 5.4.11 'APIC Error ... FATAL PAGE FAULT' on reboot? non-Xen reboot's ok.
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
Re: [Xen-devel] xen 4.13 + kernel 5.4.11 'APIC Error ... FATAL PAGE FAULT' on reboot? non-Xen reboot's ok.
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
Re: [Xen-devel] xen 4.13 + kernel 5.4.11 'APIC Error ... FATAL PAGE FAULT' on reboot? non-Xen reboot's ok.
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: > 0x8b7c-0x8c04efb8 > initrd-5.4.11-24.g2d02eb4-default: 0x8a4a5000-0x8b7bfe28 > 0x:0x00:0x19.0x0: ROM: 0x1 bytes at 0x928a9018 > 0x:0x04:0x00.0x0: ROM: 0x8000 bytes at 0x928a0018 > 0x:0x10:0x00.0x0: ROM: 0x10800 bytes at 0x92885018 >__ __ >\ \/ /___ _ __ > \ // _ \ '_ \ > / \ __/ | | | >/_/\_\___|_| |_| > >_ __ _ ___ ___ _ _ _ _ _ _____ > ___ > | || | / |___ / / _ \ / _ \| || || |_ __ / | ___|/ | / /_ ( _ ) > ( _ ) > | || |_ | | |_ \| | | | | | | | || |_ __| | '_ \| |___ \| || '_ \ / _ \ > / _ \ > |__ _|| |___) | |_| | | |_| |__ _|__| | |_) | |___) | || (_) | (_) > | (_) | > |_|(_)_|(_)___/___\___/ |_||_| .__/|_|/|_(_)___/ \___/ > \___/ > |_| |_| > > (XEN) [0026c8dc8909] Xen version 4.13.0_04-lp151.688 > (abu...@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) [0026cbd609dc] Latest ChangeSet: > (XEN) [0026cc9505ea] Bootloader: EFI > (XEN) [0026cd46f20f] 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:[<>] > > (XEN) [2020-01-15 15:01:26] RFLAGS: 00010202 CONTEXT: > hypervisor > (XEN) [2020-01-15 15:01:26] rax: 0286 rbx: > rcx: > (XEN) [2020-01-15 15:01:26] rdx: 9e5ca7a0 rsi: > rdi: > (XEN) [2020-01-15 15:01:26] rbp: rsp: > 83008ca2fa48 r8: 83008ca2fa90 > (XEN) [2020-01-15 15:01:26] r9: 83008ca2fa80 r10: > r11: > (XEN) [2020-01-15 15:01:26] r12: r13: > 83008ca2fb00 r14: 83008ca2 > (XEN) [2020-01-15 15:01:26] r15: cr0: > 80050033 cr4: 001526e0 > (XEN) [2020-01-15 15:01:26] cr3: 0008492ed000 cr2: > eef3f286 > (XEN) [2020-01-15 15:01:26] fsb: gsb: > gss: > (XEN) [2020-01-15 15:01:26] ds: es: fs: gs: > ss: cs: e008 > (XEN) [2020-01-15 15:01:26] Xen code around <> > () [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=83008ca2fa48: > (XEN) [2020-01-15 15:01:26]9e5ca3c9 82d08036681f > 82d08036682b > (XEN) [2020-01-15 15:01:26]
