From: Andrew Cooper <andrew.cooper3@citrix.com>
To: pgnet.dev@gmail.com, xen-devel@lists.xen.org
Subject: Re: 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
Date: Tue, 4 Jul 2017 20:54:01 +0100 [thread overview]
Message-ID: <3ab4ec50-bc89-dd2e-f56e-6277ae3ba3d4@citrix.com> (raw)
In-Reply-To: <0a9c6243-55fb-b44f-0af7-d357121983d8@gmail.com>
On 04/07/17 20:48, PGNet Dev wrote:
> [ 0.000000] NX (Execute Disable) protection: active
> [ 0.000000] efi: EFI v2.31 by American Megatrends
> [ 0.000000] efi: ESRT=0x9ef8d998 ACPI 2.0=0x9e819000 ACPI=0x9e819000 SMBIOS=0xf04c0 MPS=0xfd490
> (XEN) [2017-07-04 19:08:39] d0v0 Unhandled invalid opcode fault/trap [#6, ec=ffffffff]
> (XEN) [2017-07-04 19:08:39] domain_crash_sync called from entry.S: fault at ffff82d080342328 entry.o#create_bounce_frame+0x135/0x14d
> (XEN) [2017-07-04 19:08:39] Domain 0 (vcpu#0) crashed on cpu#0:
> (XEN) [2017-07-04 19:08:39] ----[ Xen-4.9.0_08-512 x86_64 debug=n Tainted: C ]----
> (XEN) [2017-07-04 19:08:39] CPU: 0
> (XEN) [2017-07-04 19:08:39] RIP: e033:[<ffffffff822b8e5b>]
Please look up 0xffffffff822b8e5b in your dom0 kernel debug symbols.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-07-04 19:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 19:48 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 PGNet Dev
2017-07-04 19:54 ` Andrew Cooper [this message]
2017-07-05 0:14 ` PGNet Dev
2017-07-05 7:58 ` Jan Beulich
2017-07-05 17:27 ` PGNet Dev
2017-07-05 22:02 ` Daniel Kiper
2017-07-05 22:12 ` PGNet Dev
2017-07-06 6:42 ` 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=3ab4ec50-bc89-dd2e-f56e-6277ae3ba3d4@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=pgnet.dev@gmail.com \
--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).