From: Andrew Cooper <andrew.cooper3@citrix.com>
To: osstest service owner <osstest-admin@xenproject.org>,
xen-devel@lists.xensource.com, Jan Beulich <JBeulich@suse.com>
Subject: Re: [xen-unstable test] 103540: regressions - FAIL
Date: Sun, 18 Dec 2016 10:38:04 +0000 [thread overview]
Message-ID: <982682e7-83a7-38b9-a6fd-a2e02604817e@citrix.com> (raw)
In-Reply-To: <osstest-103540-mainreport@xen.org>
On 18/12/2016 05:21, osstest service owner wrote:
> flight 103540 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/103540/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-amd64-i386-pvgrub 6 xen-boot fail REGR. vs. 103466
> test-xtf-amd64-amd64-3 6 xen-boot fail REGR. vs. 103466
> test-amd64-amd64-xl-qemuu-debianhvm-amd64 6 xen-boot fail REGR. vs. 103466
> test-amd64-amd64-xl-qemuu-win7-amd64 6 xen-boot fail REGR. vs. 103466
> test-armhf-armhf-libvirt-raw 4 host-ping-check-native fail REGR. vs. 103466
> test-xtf-amd64-amd64-5 6 xen-boot fail REGR. vs. 103466
> test-xtf-amd64-amd64-4 6 xen-boot fail REGR. vs. 103466
> test-amd64-i386-xl-qemuu-ovmf-amd64 6 xen-boot fail REGR. vs. 103466
> test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 6 xen-boot fail REGR. vs. 103466
> test-amd64-amd64-qemuu-nested-intel 16 debian-hvm-install/l1/l2 fail REGR. vs. 103466
http://logs.test-lab.xenproject.org/osstest/logs/103540/test-xtf-amd64-amd64-3/serial-merlot0.log
from 22:48:30.821939
(XEN) ----[ Xen-4.9-unstable x86_64 debug=y Not tainted ]----
(XEN) CPU: 0
(XEN) RIP: e008:[<ffff82d080100660>] __bitmap_and+0x24/0x33
(XEN) RFLAGS: 0000000000010202 CONTEXT: hypervisor
(XEN) rax: 0000000000000000 rbx: ffff82d08030fd58 rcx: 0000000000000001
(XEN) rdx: ffff82d0802edda0 rsi: ffff83023ffd1ef0 rdi: 0000000000000000
(XEN) rbp: ffff82d08030fd18 rsp: ffff82d08030fd18 r8: 0000000000000004
(XEN) r9: ffff82d080323a48 r10: 0000000000000000 r11: 00000000ffffffff
(XEN) r12: 0000000000000028 r13: ffff83023ffd1ef0 r14: 0000000000000000
(XEN) r15: ffff82d080343aa0 cr0: 000000008005003b cr4: 00000000000406e0
(XEN) cr3: 00000000bdaff000 cr2: 0000000000000000
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: e008
(XEN) Xen code around <ffff82d080100660> (__bitmap_and+0x24/0x33):
(XEN) 48 8b 0c c2 48 23 0c c6 <48> 89 0c c7 48 83 c0 01 41 39 c0 7f eb
5d c3 55
(XEN) Xen stack trace from rsp=ffff82d08030fd18:
(XEN) ffff82d08030fd48 ffff82d0801719cc ffff83023e203800 ffff83023e384030
(XEN) ffff82d08030fd58 0000000000000000 ffff82d08030fd88 ffff82d080171bbc
(XEN) 0000000000000000 0000000000000000 ffff82d08030fd88 ffff83023e384010
(XEN) ffff82d080329b70 0000000000000038 ffff82d08030fdc8 ffff82d0802afb8b
(XEN) 00000000c0000000 0000000000000000 00000000ffffffed ffff82d08030ffff
(XEN) 0000000000000000 ffff82d080343aa0 ffff82d08030fdd8 ffff82d0802b00d7
(XEN) ffff82d08030fdf8 ffff82d0802ac9cb ffff82d080343aa0 ffff83023fff5fe0
(XEN) ffff82d08030ff08 ffff82d0802c0ff2 0000000000000000 0000000000100000
(XEN) 00000000000001ff 0000000000000001 0000000000000001 0000000000000001
(XEN) 0000000000000001 0000000000000001 0000000000000001 0000000000000001
(XEN) 0000000000000000 00000000011f3000 000000000043efff 0000000000800163
(XEN) fffffffffffff001 000000043ee00000 0000000000000002 ffff83000008dd80
(XEN) ffff83000008def0 ffff83000008dfb0 0000000000000000 0000000000000000
(XEN) 0000000800000000 000000010000006e 0000000000000003 00000000000002f8
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 ffff82d080100073
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) Xen call trace:
(XEN) [<ffff82d080100660>] __bitmap_and+0x24/0x33
(XEN) [<ffff82d0801719cc>] msi_compose_msg+0x7e/0xf5
(XEN) [<ffff82d080171bbc>] __setup_msi_irq+0x2f/0x5c
(XEN) [<ffff82d0802afb8b>] amd_iommu_init+0x460/0x6b7
(XEN) [<ffff82d0802b00d7>] amd_iov_detect+0x69/0xad
(XEN) [<ffff82d0802ac9cb>] iommu_setup+0x61/0x1c1
(XEN) [<ffff82d0802c0ff2>] __start_xen+0x23a8/0x2878
(XEN) [<ffff82d080100073>] __high_start+0x53/0x55
(XEN)
(XEN) Pagetable walk from 0000000000000000:
(XEN) L4[0x000] = 000000023fff3063 ffffffffffffffff
(XEN) L3[0x000] = 000000023fff2063 ffffffffffffffff
(XEN) L2[0x000] = 000000023fff1063 ffffffffffffffff
(XEN) L1[0x000] = 0000000000000000 ffffffffffffffff
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) FATAL PAGE FAULT
(XEN) [error_code=0002]
(XEN) Faulting linear address: 0000000000000000
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...
This will be caused by 7f885a1f49a75c770360b030666a5c1545156e5c or
3b6172645880f6324d0394d0d707f5d76b69ae1f
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-12-18 10:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-18 5:21 [xen-unstable test] 103540: regressions - FAIL osstest service owner
2016-12-18 10:38 ` Andrew Cooper [this message]
2016-12-18 10:47 ` Andrew Cooper
2016-12-19 8:29 ` 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=982682e7-83a7-38b9-a6fd-a2e02604817e@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=osstest-admin@xenproject.org \
--cc=xen-devel@lists.xensource.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).