From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Sebastian Faerber <faerber@gmail.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Regression since Linux Kernel 3.12 due to 64bit pvguest NMIs
Date: Fri, 9 May 2014 16:02:08 -0400 [thread overview]
Message-ID: <20140509200208.GA11650@phenom.dumpdata.com> (raw)
In-Reply-To: <CAB4HUd1zE6gedePUpKdNqjiMu4m-gPVU0s1=TkVVQ2HCNUj75A@mail.gmail.com>
On Fri, May 09, 2014 at 09:55:20PM +0200, Sebastian Faerber wrote:
> Hi,
>
> i'm running into problems booting Kernel 3.12 (and newer) as a PV
> guest on a CentOS 5 Xen Hypervisor and dom0.
> I tracked this problem down to the commit
> 6efa20e49b9cb1db1ab66870cc37323474a75a13 (xen: Support 64-bit PV guest
> receiving NMIs)
>
> Host CPU is a Intel Xeon L5630
>
> (XEN) traps.c:405:d12 Unhandled invalid opcode fault/trap [#6] in
> domain 12 on VCPU 0 [ec=0000]
> (XEN) domain_crash_sync called from entry.S
> (XEN) Domain 12 (vcpu#0) crashed on cpu#4:
> (XEN) ----[ Xen-3.1.2-371.8.1.el5 x86_64 debug=n Not tainted ]----
> (XEN) CPU: 4
> (XEN) RIP: e033:[<ffffffff810041fd>]
> (XEN) RFLAGS: 0000000000000282 CONTEXT: guest
> (XEN) rax: ffffffffffffffea rbx: 0000000000000000 rcx: ffffffff81b6f078
> (XEN) rdx: 0000000000000000 rsi: ffffffff81a01ee0 rdi: 0000000000000000
> (XEN) rbp: ffffffff81afd020 rsp: ffffffff81a01ea8 r8: 0000000000000000
> (XEN) r9: ffff880000000000 r10: 0000000000007ff0 r11: 00000000ffffffff
> (XEN) r12: 0000000001000000 r13: ffffffff81a01fa0 r14: 0000000000001000
> (XEN) r15: 0000000000000000 cr0: 0000000080050033 cr4: 00000000000026b0
> (XEN) cr3: 000000095083a000 cr2: 0000000000000000
> (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033
> (XEN) Guest stack trace from rsp=ffffffff81a01ea8:
> (XEN) ffffffff81b6f078 00000000ffffffff ffffffff810041fd 000000010000e030
> (XEN) 0000000000010082 ffffffff81a01ee0 000000000000e02b ffffffff00010004
> (XEN) ffffffff8171df10 ffffffff81a8b634 ffffffff00010001 ffffffff8171f4d0
> (XEN) 0000000000000000 ffffffff81a8dbe0 0000000000000000 ffffffff81713916
> (XEN) ffffffff81a24de0 ffffffff00000010 ffffffff81a01f88 ffffffff81a01f48
> (XEN) ffffffff81b7401a ffffffffffffffff ffffffff81afd020 0000000000000000
> (XEN) 0000000000000000 0000000000000000 0000000000000000 ffffffff81a87b11
> (XEN) ffffffff81b78810 ffffffff819292a8 0000000000000000 ffffffff81087747
> (XEN) 0000000000000000 0000000080000000 0000000000000000 0000000000000000
> (XEN) 0000000000000000 ffffffff81a8ad9a 0000000000000000 0000000100000000
> (XEN) 20200800000206c2 0f89837180982221 0000000000000000 0f00000060c0c748
> (XEN) ccccccccccccc305 cccccccccccccccc cccccccccccccccc cccccccccccccccc
> (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc
> (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc
> (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc
> (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc
> (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc
> (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc
> (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc
> (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc
>
> I admit the Xen Version in CentOS 5 is very old but maybe someone
> could take a look?
Isn't it Xen 3.x based? The Linux pvops kernels I thought only
were 4.0 and further compatible?
But anyhow, I presume the:
ffffffff810041fd
maps to the 'ud2' instruction in 'xen_enable_nmi' ?
If you take the 'BUG()' out does it continue running?
> I'm happy to test patches or try to get more information if needed.
>
> Regards,
>
> Sebastian
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-05-09 20:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 19:55 Regression since Linux Kernel 3.12 due to 64bit pvguest NMIs Sebastian Faerber
2014-05-09 20:02 ` Konrad Rzeszutek Wilk [this message]
2014-05-09 20:28 ` Sebastian Faerber
2014-05-12 14:21 ` Konrad Rzeszutek Wilk
2014-05-13 8:18 ` Sebastian Faerber
2014-05-13 18:45 ` Konrad Rzeszutek Wilk
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=20140509200208.GA11650@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=faerber@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).