From: Andrew Cooper <andrew.cooper3@citrix.com>
To: <pgnet.dev@gmail.com>, <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] xen 4.13 + kernel 5.4.11 'APIC Error ... FATAL PAGE FAULT' on reboot? non-Xen reboot's ok.
Date: Wed, 15 Jan 2020 17:21:11 +0000 [thread overview]
Message-ID: <bdfd64dd-6fe7-ec75-5c39-9e8d6063eb85@citrix.com> (raw)
In-Reply-To: <74cc009f-2d9d-c466-6735-096a47fca7e8@gmail.com>
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
next prev parent reply other threads:[~2020-01-15 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2020-01-15 17:43 ` PGNet Dev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bdfd64dd-6fe7-ec75-5c39-9e8d6063eb85@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=pgnet.dev@gmail.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.