From: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Kevin Tian <kevin.tian@intel.com>, Quan Xu <xuquan8@huawei.com>,
osstest service owner <osstest-admin@xenproject.org>,
Jan Beulich <JBeulich@suse.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Chao Gao <chao.gao@intel.com>
Subject: Re: [xen-unstable test] 104131: regressions - FAIL
Date: Thu, 12 Jan 2017 09:14:07 +0000 [thread overview]
Message-ID: <a91a6ecc-2a4f-01db-3bb2-d6faa2501f94@citrix.com> (raw)
In-Reply-To: <osstest-104131-mainreport@xen.org>
On 12/01/2017 06:46, osstest service owner wrote:
> flight 104131 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/104131/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-i386-xl-qemuu-debianhvm-amd64 16 guest-stop fail REGR. vs. 104119
Jan 12 01:25:17.397607 (XEN) Assertion 'intack.vector >= pt_vector' failed at intr.c:321
Jan 12 01:25:37.133596 (XEN) ----[ Xen-4.9-unstable x86_64 debug=y Not tainted ]----
Jan 12 01:25:37.141577 (XEN) CPU: 14
Jan 12 01:25:37.141607 (XEN) RIP: e008:[<ffff82d0801ef7fc>] vmx_intr_assist+0x35e/0x51d
Jan 12 01:25:37.149617 (XEN) RFLAGS: 0000000000010202 CONTEXT: hypervisor (d15v0)
Jan 12 01:25:37.149655 (XEN) rax: 0000000000000038 rbx: ffff830079e1e000 rcx: 0000000000000030
Jan 12 01:25:37.157582 (XEN) rdx: 0000000000000000 rsi: 0000000000000030 rdi: ffff830079e1e000
Jan 12 01:25:37.165584 (XEN) rbp: ffff83047de2ff08 rsp: ffff83047de2fea8 r8: ffff82c00022f000
Jan 12 01:25:37.173579 (XEN) r9: ffff8301b63ede80 r10: ffff830176386560 r11: 000001955ee79bd0
Jan 12 01:25:37.181582 (XEN) r12: 0000000000003002 r13: 0000000000003002 r14: 0000000000000030
Jan 12 01:25:37.189584 (XEN) r15: ffff83023fec2000 cr0: 0000000080050033 cr4: 00000000003526e0
Jan 12 01:25:37.197572 (XEN) cr3: 0000000232edb000 cr2: 0000000002487034
Jan 12 01:25:37.205569 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: e008
Jan 12 01:25:37.205606 (XEN) Xen code around <ffff82d0801ef7fc> (vmx_intr_assist+0x35e/0x51d):
Jan 12 01:25:37.213575 (XEN) 41 0f b6 f6 39 f0 7e 02 <0f> 0b 48 89 df e8 51 20 00 00 b8 10 08 00 00 0f
Jan 12 01:25:37.221561 (XEN) Xen stack trace from rsp=ffff83047de2fea8:
Jan 12 01:25:37.229600 (XEN) ffff82d08031aa80 00000038ffffffff ffff83047de2ffff ffff83023fec2000
Jan 12 01:25:37.237594 (XEN) ffff83047de2fef8 ffff82d080130cb6 ffff830079e1e000 ffff830079e1e000
Jan 12 01:25:37.245588 (XEN) ffff83007bae2000 000000000000000e ffff830233117000 ffff83023fec2000
Jan 12 01:25:37.253594 (XEN) ffff83047de2fdc0 ffff82d0801fdeb1 0000000000000004 00000000000000c2
Jan 12 01:25:37.261584 (XEN) 0000000000000020 0000000000000007 ffff8800e8d28000 ffffffff81add0a0
Jan 12 01:25:37.269607 (XEN) 0000000000000246 0000000000000000 ffff880142400008 0000000000000004
Jan 12 01:25:37.277580 (XEN) 0000000000000036 0000000000000000 00000000000003f8 00000000000003f8
Jan 12 01:25:37.285584 (XEN) ffffffff81add0a0 0000beef0000beef ffffffff813899a4 000000bf0000beef
Jan 12 01:25:37.293567 (XEN) 0000000000000002 ffff880147c03e08 000000000000beef 1cec835356e5beef
Jan 12 01:25:37.293606 (XEN) 085d8b002674beef 01dcb38b000cbeef 8914458d3174beef 2444c7100000000e
Jan 12 01:25:37.301586 (XEN) ffff830079e1e000 00000031bfc37600 00000000003526e0
Jan 12 01:25:37.309607 (XEN) Xen call trace:
Jan 12 01:25:37.309639 (XEN) [<ffff82d0801ef7fc>] vmx_intr_assist+0x35e/0x51d
Jan 12 01:25:37.317591 (XEN) [<ffff82d0801fdeb1>] vmx_asm_vmexit_handler+0x41/0x120
Jan 12 01:25:37.325598 (XEN)
Jan 12 01:25:37.325624 (XEN)
Jan 12 01:25:37.325647 (XEN) ****************************************
Jan 12 01:25:37.333653 (XEN) Panic on CPU 14:
Jan 12 01:25:37.333684 (XEN) Assertion 'intack.vector >= pt_vector' failed at intr.c:321
Jan 12 01:25:37.341571 (XEN) ****************************************
Jan 12 01:25:37.341603 (XEN)
Jan 12 01:25:37.341626 (XEN) Reboot in five seconds...
Jan 12 01:25:37.349566 (XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
This is caused by "x86/apicv: fix RTC periodic timer and apicv issue". It is not a deterministic issue, as it appears to have survived a week of testing already, but there is clearly something still problematic with the code.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-01-12 9:14 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 6:46 [xen-unstable test] 104131: regressions - FAIL osstest service owner
2017-01-12 9:14 ` Andrew Cooper [this message]
2017-01-12 12:07 ` Xuquan (Quan Xu)
2017-01-12 9:04 ` Chao Gao
2017-01-12 12:15 ` Andrew Cooper
2017-01-12 12:25 ` Jan Beulich
2017-01-16 5:25 ` Tian, Kevin
2017-01-16 6:27 ` Xuquan (Quan Xu)
2017-01-16 0:06 ` Chao Gao
2017-01-16 11:00 ` Jan Beulich
2017-01-18 4:57 ` Tian, Kevin
2017-01-18 9:38 ` Jan Beulich
2017-01-18 10:23 ` Tian, Kevin
2017-01-20 11:48 ` Jan Beulich
2017-01-22 4:35 ` Tian, Kevin
2017-01-23 10:33 ` Jan Beulich
2017-01-20 8:47 ` Xuquan (Quan Xu)
2017-01-20 8:56 ` Jan Beulich
2017-01-20 9:08 ` Xuquan (Quan Xu)
2017-01-23 10:56 ` Xuquan (Quan Xu)
2017-02-08 6:51 ` Tian, Kevin
2017-02-08 8:27 ` Xuquan (Quan Xu)
2017-02-08 8:52 ` Jan Beulich
2017-02-08 10:15 ` Xuquan (Quan Xu)
2017-02-08 8:22 ` Chao Gao
2017-02-09 8:51 ` Xuquan (Quan Xu)
2017-02-09 3:41 ` Chao Gao
2017-02-13 8:21 ` Tian, Kevin
2017-02-20 12:04 ` Xuquan (Quan Xu)
2017-02-21 3:17 ` Tian, Kevin
2017-02-13 8:23 ` Tian, Kevin
2017-02-14 1:22 ` Xuquan (Quan Xu)
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=a91a6ecc-2a4f-01db-3bb2-d6faa2501f94@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=chao.gao@intel.com \
--cc=kevin.tian@intel.com \
--cc=osstest-admin@xenproject.org \
--cc=xen-devel@lists.xen.org \
--cc=xuquan8@huawei.com \
/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).