xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Michael Young <m.a.young@durham.ac.uk>
To: Adi Pircalabu <adi@ddns.com.au>
Cc: xen-devel@lists.xenproject.org
Subject: Re: kernel-ml-4.15.0-1.el7.elrepo.x86_64 doesn't boot as	Xen PV domU
Date: Wed, 31 Jan 2018 22:13:05 +0000 (GMT)	[thread overview]
Message-ID: <alpine.LFD.2.21.1801312150210.2821@austen3.home> (raw)
In-Reply-To: <b4129ec6500da5abe6c461c9ad8b975b@ddns.com.au>

On Wed, 31 Jan 2018, Adi Pircalabu wrote:

> (XEN) d8v0: unhandled page fault (ec=0000)
> (XEN) Pagetable walk from 0000000000000028:
> (XEN) L4[0x000] = 0000000000000000 ffffffffffffffff
> (XEN) domain_crash_sync called from entry.S: fault at ffff82d08022a472 
> create_bounce_frame+0x12b/0x13a
> (XEN) Domain 8 (vcpu#0) crashed on cpu#6:
> (XEN) ----[ Xen-4.6.6-9.el7 x86_64 debug=n Not tainted ]----
> (XEN) CPU: 6
> (XEN) RIP: e033:[<ffffffff8103f261>]
> (XEN) RFLAGS: 0000000000000292 EM: 1 CONTEXT: pv guest (d8v0)
> (XEN) rax: 0000000000000000 rbx: ffffffff81e05720 rcx: 0000000000000000
> (XEN) rdx: 0000000000000030 rsi: ffffffff82203efc rdi: ffffffff8241d460
> (XEN) rbp: ffffffff82203ec8 rsp: ffffffff82203e10 r8: 0000000000000000
> (XEN) r9: ffffffff82203f00 r10: 00000000ffffffff r11: ffffffff82203f04
> (XEN) r12: ffffffff82203e78 r13: ffffffff82203e7c r14: ffffffff82203e80
> (XEN) r15: ffffffff82203e84 cr0: 000000008005003b cr4: 00000000003526e0
> (XEN) cr3: 0000000426314000 cr2: 0000000000000028
> (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033
> (XEN) Guest stack trace from rsp=ffffffff82203e10:
> (XEN) 0000000000000000 ffffffff82203f04 0000000000000000 ffffffff8103f261
> (XEN) 000000010000e030 0000000000010092 ffffffff82203e58 000000000000e02b
> (XEN) 0000000000000000 ffffffff8241d460 0000000000000000 0000000000000000
> (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN) 0000000000000000 0000000000000000 ffffffff8241d460 ffffffff82203f04
> (XEN) ffffffff82203f00 ffffffff82203efc ffffffff82203ef8 ffffffff82203f40
> (XEN) ffffffff8103fce6 ffffffff82203f14 ffffffff82203f10 ffffffff82203f0c
> (XEN) ffffffff82203f08 0000000000003027 0000000000000000 0000000080000008
> (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN) 0000000000000000 0000000000000000 ffffffff82203ff8 ffffffff8246c490
> (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN) 0000000000000000 0000000000000000 0f00000060c0c748 ccccccccccccc305
> (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc
> (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc
> (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc
> (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc

I an getting a similar crash with a PV guest running Fedora rawhide

(XEN) d26v0 Unhandled page fault fault/trap [#14, ec=0000]
(XEN) Pagetable walk from 0000000000000028:
(XEN)  L4[0x000] = 0000000000000000 ffffffffffffffff
(XEN) domain_crash_sync called from entry.S: fault at ffff82d080348a68 entry.o#create_bounce_frame+0x135/0x14d
(XEN) Domain 26 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-4.9.1  x86_64  debug=n   Not tainted ]----
(XEN) CPU:    0
(XEN) RIP:    e033:[<ffffffff81036a89>]
(XEN) RFLAGS: 0000000000000292   EM: 1   CONTEXT: pv guest (d26v0)
(XEN) rax: 0000000000000000   rbx: ffffffff81e03fa0   rcx: 0000000000000000
(XEN) rdx: 0000000000000000   rsi: ffffffff82203f04   rdi: ffffffff823777e0
(XEN) rbp: ffffffff82203f08   rsp: ffffffff82203e20   r8:  ffffffff82203f08
(XEN) r9:  00000000ffffffff   r10: ffffffff82203f0c   r11: 0000000000000000
(XEN) r12: ffffffff82203f0c   r13: ffffffff82203e88   r14: ffffffff82203f00
(XEN) r15: ffffffff82203e98   cr0: 000000008005003b   cr4: 00000000001526e0
(XEN) cr3: 000000021709a000   cr2: 0000000000000028
(XEN) fsb: 0000000000000000   gsb: 0000000000000000   gss: 0000000000000000
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs: e033
(XEN) Guest stack trace from rsp=ffffffff82203e20:
(XEN)    0000000000000000 0000000000000000 0000000000000000 ffffffff81036a89
(XEN)    000000010000e030 0000000000010092 ffffffff82203e68 000000000000e02b
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000

This example is when booting 4.15.0-1.fc28.x86_64, the last kernel I 
successfully booted on this guest was 4.15.0-0.rc4.git3.1.fc28.x86_64

In this build of xen the code at create_bounce_frame+0x135 (ie. 309) is
    0xffff82d080348a61 <create_bounce_frame+302>:	mov    0x8(%rdx),%rax
    0xffff82d080348a65 <create_bounce_frame+306>:	test   %rax,%rax
    0xffff82d080348a68 <create_bounce_frame+309>:
     je     0xffff82d080349e60 <arch/x86/x86_64/entry.o.unlikely+116>
    0xffff82d080348a6e <create_bounce_frame+315>:	mov    %rax,0x88(%rsp)
    0xffff82d080348a76 <create_bounce_frame+323>:	retq
    0xffff82d080348a77 <create_bounce_frame+324>:	nopw   0x0(%rax,%rax,1)

ie. at
         movq  TRAPBOUNCE_eip(%rdx),%rax
         testq %rax,%rax
UNLIKELY_START(z, create_bounce_frame_bad_bounce_ip)
         lea   UNLIKELY_DISPATCH_LABEL(create_bounce_frame_bad_bounce_ip)(%rip), %rdi
         jmp   asm_domain_crash_synchronous  /* Does not return */
__UNLIKELY_END(create_bounce_frame_bad_bounce_ip)
         movq  %rax,UREGS_rip+8(%rsp)
         ret
in xen/arch/x86/x86_64/entry.S

 	Michael Young

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-01-31 22:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-31  0:18 kernel-ml-4.15.0-1.el7.elrepo.x86_64 doesn't boot as Xen PV domU Adi Pircalabu
2018-01-31 22:13 ` Michael Young [this message]
2018-02-01  0:17   ` Michael Young
2018-02-01  7:25     ` Juergen Gross

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=alpine.LFD.2.21.1801312150210.2821@austen3.home \
    --to=m.a.young@durham.ac.uk \
    --cc=adi@ddns.com.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).