[Bug 1047765] New: Virtualization/xen: Bug new Xen 4.9.0_08 / kernel 4.12.0 Dom0 crash @ domain_crash_sync called from entry.S ...
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765 Bug ID: 1047765 Summary: Virtualization/xen: Bug new Xen 4.9.0_08 / kernel 4.12.0 Dom0 crash @ domain_crash_sync called from entry.S ... Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: openSUSE 42.2 Status: NEW Severity: Critical Priority: P5 - None Component: 3rd party software Assignee: carnold@suse.com Reporter: pgnet.dev@gmail.com QA Contact: opensuse-communityscreening@forge.provo.novell.com Found By: --- Blocker: --- fyi/placeholder until kernel updates propagate, or patches backported to Opensuse Kernel:Stable with kernel 4.12 (from Kernel:Stable), Xen 4.9.0 (from Virtualization) Dom0 crashes on boot. Info's already posted @ [Xen-devel] OOPS new Xen 4.9.0_08 / kernel 4.12.0 Dom0 crash @ domain_crash_sync called from entry.S: fault at ffff82d080342328 entry.o#create_bounce_frame+0x135/0x14d https://lists.xen.org/archives/html/xen-devel/2017-07/msg00421.html per https://lists.xen.org/archives/html/xen-devel/2017-07/msg00587.html fixes appear upstream 6c64447 (x86/xen/efi: Initialize only the EFI struct membersused by Xen) https://patchwork.kernel.org/patch/9806659/ & 457ea3f (efi: Process the MEMATTR table only if EFI_MEMMAP isenabled) https://patchwork.kernel.org/patch/9806657/ -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765
pgnd _
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765 boo35 boo35 <9b3e05a5@opayq.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |9b3e05a5@opayq.com, | |kernel-maintainers@forge.pr | |ovo.novell.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765 boo35 boo35 <9b3e05a5@opayq.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|9b3e05a5@opayq.com | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765
pgnd _
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765
pgnd _
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765
pgnd _
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765
pgnd _
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765
pgnd _
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765
pgnd _
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765
pgnd _
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765
pgnd _
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765
Charles Arnold
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765#c1
--- Comment #1 from pgnd _
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765#c2
--- Comment #2 from Jürgen Groß
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765#c3
--- Comment #3 from pgnd _
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765#c4
--- Comment #4 from Jürgen Groß
Thanks. That will be helpful.
I saw they were in upstream, obviously.
Where'd you see the backport commit? I'm apparently not looking in the right place.
I didn't see a backport commit. My comment was based on the fact the patches had "Cc: stable@vger.kernel.org" specified. Meanwhile they are in review for 4.12 (just received the related mails from Greg). So I expect them to be included in 4.12.3 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765#c5
--- Comment #5 from pgnd _
I didn't see a backport commit. My comment was based on the fact the patches had "Cc: stable@vger.kernel.org" specified.
Noted, thx.
Meanwhile they are in review for 4.12 (just received the related mails from Greg). So I expect them to be included in 4.12.3
Sounds about right. NOT in today's kernel-default-4.12.2-4.1.g8db850a in any case. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765#c6
pgnd _
So I expect them to be included in 4.12.3
Booting with new 4.12.3 kernel-default-4.12.3-2.1.g409edbf.x86_64 still causes the reported Xen crash ... (XEN) [2017-07-22 19:30:16] d0v0 Unhandled invalid opcode fault/trap [#6, ec=ffffffff] (XEN) [2017-07-22 19:30:16] domain_crash_sync called from entry.S: fault at ffff82d080342328 entry.o#create_bounce_frame+0x135/0x14d (XEN) [2017-07-22 19:30:16] Domain 0 (vcpu#0) crashed on cpu#0: (XEN) [2017-07-22 19:30:16] ----[ Xen-4.9.0_08-516 x86_64 debug=n Tainted: C ]---- (XEN) [2017-07-22 19:30:16] CPU: 0 (XEN) [2017-07-22 19:30:16] RIP: e033:[<ffffffff822bae60>] ... I don't see mention in the latest pkg changelog, but that's usually no guarantee. Do they need to be manually pulled into OBS sources? I'll take a closer look myself a bit later, and if needed, report back to upstream ML. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765
pgnd _
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765#c7
Jürgen Groß
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765#c8
pgnd _
Could you try the kernel from Linus tree? It has all fixes for known UEFI dom0 issues.
I've built & installed Kernel/HEAD rev g40a8696 packages from OBS on the Xen box. Now, booting, ... Xen 4.9.0_08-517 (c/s ) EFI loader Using configuration file 'xen-4.9.0_08-517.cfg' vmlinuz-4.13.0-rc1-4.g40a8696-default: 0x000000008b905000-0x000000008c0a2d60 initrd-4.13.0-rc1-4.g40a8696-default: 0x000000008a8f7000-0x000000008b904194 ... (XEN) [2017-07-24 18:39:45] d1v0 Over-allocation for domain 1: 524545 > 524544 (XEN) [2017-07-24 18:39:45] d1v0 Over-allocation for domain 1: 524545 > 524544 ( ... constant stream of these ... ) ... the Dom0's up uname -rm 4.13.0-rc1-4.g40a8696-default x86_64 as is a test DomU xl list Name ID Mem VCPUs State Time(s) Domain-0 0 4090 4 r----- 69.4 test 1 2049 1 -b---- 19.6 So it seems that kernel HEAD's fixed the problem. Once 4.13 release lands as stable, I frankly won't bother with 4.12 anymore. That said, it's troubling that a kernel 4.12 *stable* release broke a Xen 4.9 release boot, and that upstream didn't bother to accept patches, supposedly addressing the breakage. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765#c9
--- Comment #9 from Jürgen Groß
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765
http://bugzilla.opensuse.org/show_bug.cgi?id=1047765#c10
pgnd _
participants (1)
-
bugzilla_noreply@novell.com