xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: linux@eikelenboom.it, xen-devel@lists.xen.org
Cc: Paul Durrant <Paul.Durrant@citrix.com>
Subject: Re: xen-unstabel + linux 4.2: MMIO emulation failed: d23v0 64bit @ 0010:ffffffff814e2b1c -> 66 89 02 48 8d 55 c0 48 89 5d c0 44 89 65 c8 e8
Date: Mon, 27 Jul 2015 15:07:39 +0100	[thread overview]
Message-ID: <55B63B2B.8070508@citrix.com> (raw)
In-Reply-To: <34b88d3d0f41027630a7fdc85675601e@eikelenboom.it>

On 24/07/15 19:56, linux@eikelenboom.it wrote:
> Hi All,
>
> On my AMD system running xen-unstable (last commit: ),
>  after a few restarts of a HVM guest with pci-passthrough i got these
> on shutdown of the guest:
> (never seen this before, so it should be something triggered by a
> recent commit)
>
> -- 
> Sander
>
>
> .... (probably lost before but that's lost)
>
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.

Paul: this is very likely an issue your emulation series.

66 89 02 is mov %ax,(%rdx), but has ended up in handle_pio() which seems
wrong.

Sander: Please can you rerun with the following debug

diff --git a/xen/arch/x86/hvm/io.c b/xen/arch/x86/hvm/io.c
index d3b9cae..7560d08 100644
--- a/xen/arch/x86/hvm/io.c
+++ b/xen/arch/x86/hvm/io.c
@@ -163,7 +163,9 @@ int handle_pio(uint16_t port, unsigned int size, int
dir)
         break;
     default:
         gdprintk(XENLOG_ERR, "Weird HVM ioemulation status %d.\n", rc);
-        domain_crash(curr->domain);
+        show_execution_state(curr);
+        dump_execution_state();
+        domain_crash_synchronous(curr->domain);
         break;
     }

~Andrew

  parent reply	other threads:[~2015-07-27 14:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-24 18:56 xen-unstabel + linux 4.2: MMIO emulation failed: d23v0 64bit @ 0010:ffffffff814e2b1c -> 66 89 02 48 8d 55 c0 48 89 5d c0 44 89 65 c8 e8 linux
2015-07-24 19:27 ` Sander Eikelenboom
2015-07-27 14:07 ` Andrew Cooper [this message]
2015-07-27 14:22   ` Paul Durrant
2015-07-27 14:44   ` Sander Eikelenboom
2015-07-28 21:16   ` linux
2015-07-29  9:06     ` Paul Durrant
2015-07-29 11:11       ` Sander Eikelenboom

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=55B63B2B.8070508@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Paul.Durrant@citrix.com \
    --cc=linux@eikelenboom.it \
    --cc=xen-devel@lists.xen.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).