From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: xen-devel@lists.xenproject.org
Cc: George Dunlap <george.dunlap@citrix.com>
Subject: Current staging crashes on boot on an AMD EPYC 7251
Date: Fri, 21 Sep 2018 12:45:18 +0300 [thread overview]
Message-ID: <79af1936-5093-d101-d3a5-2abd444551e8@bitdefender.com> (raw)
Hello,
While doing my best to make sure what I understand to be George's
proposed changes for the altp2m series I've tried to boot Xen staging on
an AMD host, but it crashes in an unrelated place (I've tested this by
stashing my changes and booting a "vanilla" staging):
(XEN) Dom0 has maximum 16 VCPUs
(XEN) ELF: phdr 0 at 0xffffffff81000000 -> 0xffffffff81de9000
(XEN) ELF: phdr 1 at 0xffffffff81e00000 -> 0xffffffff81f4a000
(XEN) ELF: phdr 2 at 0xffffffff81f4a000 -> 0xffffffff81f624d8
(XEN) ELF: phdr 3 at 0xffffffff81f63000 -> 0xffffffff820ce000
(XEN) setup 0000:00:00.2 for d0 failed (-19)
(XEN) setup 0000:20:00.2 for d0 failed (-19)
(XEN) setup 0000:40:00.2 for d0 failed (-19)
(XEN) setup 0000:60:00.2 for d0 failed (-19)
(XEN) Assertion 'unreachable' failed at mm.c:468
(XEN) ----[ Xen-4.12-unstable x86_64 debug=y Not tainted ]----
(XEN) CPU: 0
(XEN) RIP: e008:[<ffff82d080289024>] page_get_ram_type+0x9a/0xbb
(XEN) RFLAGS: 0000000000010216 CONTEXT: hypervisor
(XEN) rax: 0000000000000000 rbx: 00000000000dabf2 rcx: 00000000dabf2000
(XEN) rdx: ffff82d0805a3b60 rsi: ffff82d0805a3b60 rdi: 00000000dabf2000
(XEN) rbp: ffff82d080487858 rsp: ffff82d080487858 r8: 00000000dabf3000
(XEN) r9: ffff82d0805a3d90 r10: 00000000dacdf000 r11: ffff82d080391a54
(XEN) r12: 00000000000dabf2 r13: ffff8303fb341000 r14: 0000000000c1f200
(XEN) r15: 000ffffffffff000 cr0: 000000008005003b cr4: 00000000001506e0
(XEN) cr3: 00000000dbe7b000 cr2: 0000000000000000
(XEN) fsb: 0000000000000000 gsb: 0000000000000000 gss: 0000000000000000
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: e008
(XEN) Xen code around <ffff82d080289024> (page_get_ram_type+0x9a/0xbb):
(XEN) 04 eb 07 83 c8 08 eb 02 <0f> 0b 48 03 0e 48 83 c2 14 4c 39 ca 75
a0 85 c0
(XEN) Xen stack trace from rsp=ffff82d080487858:
(XEN) ffff82d080487898 ffff82d08040d57c ffff82d080487898 ffff8300d9bfa000
(XEN) ffff8303fb341000 000000000017e1b8 0000000000177000 ffff8303fb341000
(XEN) ffff82d0804878d8 ffff82d08040753c ffff82d0804878d8 ffff8300d9bfa000
(XEN) 00000000000071b8 000000000017e1b8 0000000000177000 ffff8303fb341000
(XEN) ffff82d080487d68 ffff82d080428c04 ffff82d080487ad8 ffff830000097ed0
(XEN) ffffffff82400000 0000000000000015 0000000000000ff0 0000000000000000
(XEN) 00000003f6241000 ffff8303f6240000 ffffffff8223e000 ffff8303f6241000
(XEN) 0000000000000000 ffff8303f6242ff8 00000003f6253000 00000000000065fe
(XEN) ffff8303f6242000 ffffffff82255000 ffffffff81000000 00000000003f8000
(XEN) ffffffff8223e000 00000003f6254000 ffff8303f6241090 00000000003f4000
(XEN) ffffffff8223e000 00000000000025fe 0000000000002400 ffff830000097ed0
(XEN) 0000008000bb8000 00000000000065fe ffff820040000000 0000008000000000
(XEN) 00000000000065fe 0000000000177000 0000000000000000 00000000000071b9
(XEN) 0000000000004000 ffff82d08045a7c0 ffff8300d9bfa000 00000000025fdbda
(XEN) 0000000000000000 ffff830c1b97be64 ffff830c1b97c068 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000001 ffff82d0803e5471
(XEN) ffffffff81f631f0 0000000000000001 ffff82d0803e52bf ffffffff81001000
(XEN) 0000000000000001 ffff82d0803e5299 ffffffff80000000 0000000000000001
(XEN) ffff82d0803e52b2 0000000000000000 0000000000000002 ffff82d0803e5401
(XEN) ffff830c1b97bea0 0000000000000002 ffff82d0803e525d ffff830c1b97be74
(XEN) Xen call trace:
(XEN) [<ffff82d080289024>] page_get_ram_type+0x9a/0xbb
(XEN) [<ffff82d08040d57c>] arch_iommu_hwdom_init+0x28a/0x2ac
(XEN) [<ffff82d08040753c>] iommu_hwdom_init+0x1d5/0x1e4
(XEN) [<ffff82d080428c04>] dom0_construct_pv+0x280b/0x28d7
(XEN) [<ffff82d08042b9ed>] construct_dom0+0x99/0xae4
(XEN) [<ffff82d08041c358>] __start_xen+0x25ec/0x2723
(XEN) [<ffff82d0802000f3>] __high_start+0x53/0x55
(XEN)
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Assertion 'unreachable' failed at mm.c:468
(XEN) ****************************************
Let me know if I can help further.
Thanks,
Razvan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2018-09-21 9:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 9:45 Razvan Cojocaru [this message]
2018-09-21 10:15 ` Current staging crashes on boot on an AMD EPYC 7251 Roger Pau Monné
2018-09-21 10:41 ` Jan Beulich
2018-09-21 10:48 ` Razvan Cojocaru
2018-09-21 11:00 ` Jan Beulich
2018-09-21 11:05 ` Roger Pau Monné
2018-09-21 11:18 ` Roger Pau Monné
2018-09-21 11:51 ` Razvan Cojocaru
2018-09-21 12:03 ` Jan Beulich
2018-09-21 11:56 ` Jan Beulich
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=79af1936-5093-d101-d3a5-2abd444551e8@bitdefender.com \
--to=rcojocaru@bitdefender.com \
--cc=george.dunlap@citrix.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.