From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>
Cc: xen-devel@lists.xensource.com, ian.jackson@eu.citrix.com
Subject: Re: [xen-unstable test] 59160: regressions - FAIL
Date: Wed, 8 Jul 2015 13:47:10 +0100 [thread overview]
Message-ID: <1436359630.23508.37.camel@citrix.com> (raw)
In-Reply-To: <osstest-59160-mainreport@xen.org>
On Wed, 2015-07-08 at 12:42 +0000, osstest service owner wrote:
> flight 59160 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/59160/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-amd64-xl-pvh-amd 6 xen-boot fail REGR. vs. 58965
> test-amd64-amd64-xl-xsm 6 xen-boot fail REGR. vs. 58965
> test-amd64-i386-rumpuserxen-i386 6 xen-boot fail REGR. vs. 58965
> test-amd64-i386-qemut-rhel6hvm-amd 6 xen-boot fail REGR. vs. 58965
> test-amd64-i386-qemuu-rhel6hvm-amd 6 xen-boot fail REGR. vs. 58965
> test-amd64-i386-xl-qemut-win7-amd64 6 xen-boot fail REGR. vs. 58965
> test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 9 debian-hvm-install fail REGR. vs. 58965
> test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 6 xen-boot fail REGR. vs. 58965
> test-amd64-amd64-xl-qemut-debianhvm-amd64 6 xen-boot fail REGR. vs. 58965
> test-amd64-i386-xl-qemut-debianhvm-amd64 6 xen-boot fail REGR. vs. 58965
> test-amd64-amd64-xl-qemuu-ovmf-amd64 17 guest-start.2 fail REGR. vs. 58965
> test-amd64-i386-xl-qemut-winxpsp3-vcpus1 6 xen-boot fail REGR. vs. 58965
> test-amd64-i386-xl-qemut-winxpsp3 6 xen-boot fail REGR. vs. 58965
> test-amd64-amd64-xl-qemuu-winxpsp3 6 xen-boot fail REGR. vs. 58965
Picking one at random I some spew in
http://logs.test-lab.xenproject.org/osstest/logs/59160/test-amd64-amd64-xl-pvh-amd/serial-pinot1.log
I have a feeling this is already being addressed in the CAT thread, but
in case it isn't here we are:
Jul 8 09:37:50.225043 (XEN) If possible, disable SATA Combined mode in BIOS or contact your vendor for BIOS update.
Jul 8 09:37:50.233049 (XEN) AMD-Vi: Error initialization
Jul 8 09:37:50.241018 (XEN) I/O virtualisation disabled
Jul 8 09:37:50.241051 (XEN) ----[ Xen-4.6-unstable x86_64 debug=y Not tainted ]----
Jul 8 09:37:50.249072 (XEN) CPU: 0
Jul 8 09:37:50.257060 (XEN) RIP: e008:[<ffff82d08018ac24>] set_cpu_sibling_map+0x50/0x391
Jul 8 09:37:50.265028 (XEN) RFLAGS: 0000000000010293 CONTEXT: hypervisor
Jul 8 09:37:50.265067 (XEN) rax: 0000000000000000 rbx: ffff82d080331d40 rcx: 0000000000000000
Jul 8 09:37:50.273061 (XEN) rdx: 0000000000000001 rsi: 0000000000000000 rdi: 0000000000000000
Jul 8 09:37:50.281059 (XEN) rbp: ffff82d0802efe28 rsp: ffff82d0802efdd8 r8: ffff83021889ce00
Jul 8 09:37:50.289051 (XEN) r9: 0000000000000000 r10: 0000000000000004 r11: ffff82d0802fc0d0
Jul 8 09:37:50.297059 (XEN) r12: ffff8302188a4fe0 r13: ffff82d080331cc0 r14: 0000000000000000
Jul 8 09:37:50.305124 (XEN) r15: 0000000000000003 cr0: 000000008005003b cr4: 00000000000406e0
Jul 8 09:37:50.313044 (XEN) cr3: 00000000dfc9d000 cr2: 0000000000000000
Jul 8 09:37:50.321038 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: e008
Jul 8 09:37:50.329038 (XEN) Xen stack trace from rsp=ffff82d0802efdd8:
Jul 8 09:37:50.337047 (XEN) ffff82d0802efe28 0000000000000020 ffff8302188a4fe0 ffff82d080331cc0
Jul 8 09:37:50.345041 (XEN) ffff82d080331cc0 ffff82d080331d40 ffff8302188a4fe0 ffff82d080331cc0
Jul 8 09:37:50.353045 (XEN) ffff82d080331cc0 0000000000000003 ffff82d0802efe48 ffff82d0802c459e
Jul 8 09:37:50.361035 (XEN) ffff82d0802e8000 ffff82d0802e8000 ffff82d0802eff08 ffff82d0802c3dd5
Jul 8 09:37:50.369035 (XEN) 0000000200000000 0000000000000000 00000000011e5000 000000000021f000
Jul 8 09:37:50.377080 (XEN) ffff830000089da0 0000000000100001 000000021c894000 0000000000000000
Jul 8 09:37:50.385047 (XEN) 000000130000024d ffff830000089f20 ffff830000089fb0 ffff82d000000003
Jul 8 09:37:50.393035 (XEN) 0000000800000000 000000010000006e 0000000000000003 00000000000002f8
Jul 8 09:37:50.401045 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
Jul 8 09:37:50.409007 (XEN) 0000000000000000 0000000000000000 0000000000000000 ffff82d080100073
Jul 8 09:37:50.417046 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
Jul 8 09:37:50.425116 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
Jul 8 09:37:50.433230 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
Jul 8 09:37:50.441097 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
Jul 8 09:37:50.449124 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
Jul 8 09:37:50.457103 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
Jul 8 09:37:50.465113 (XEN) 0000000000000000 0000000000000000 ffff8300dfafe000 0000000000000000
Jul 8 09:37:50.473053 (XEN) 0000000000000000
Jul 8 09:37:50.481039 (XEN) Xen call trace:
Jul 8 09:37:50.481071 (XEN) [<ffff82d08018ac24>] set_cpu_sibling_map+0x50/0x391
Jul 8 09:37:50.489051 (XEN) [<ffff82d0802c459e>] smp_prepare_cpus+0x12e/0x254
Jul 8 09:37:50.497062 (XEN) [<ffff82d0802c3dd5>] __start_xen+0x209f/0x2647
Jul 8 09:37:50.505041 (XEN) [<ffff82d080100073>] __high_start+0x53/0x58
Jul 8 09:37:50.505079 (XEN)
Jul 8 09:37:50.513196 (XEN) Pagetable walk from 0000000000000000:
Jul 8 09:37:50.513232 (XEN) L4[0x000] = 00000002188a0063 ffffffffffffffff
Jul 8 09:37:50.521044 (XEN) L3[0x000] = 000000021889f063 ffffffffffffffff
Jul 8 09:37:50.529045 (XEN) L2[0x000] = 000000021889e063 ffffffffffffffff
Jul 8 09:37:50.537039 (XEN) L1[0x000] = 0000000000000000 ffffffffffffffff
Jul 8 09:37:50.537076 (XEN)
Jul 8 09:37:50.545035 (XEN) ****************************************
Jul 8 09:37:50.545068 (XEN) Panic on CPU 0:
Jul 8 09:37:50.553111 (XEN) FATAL PAGE FAULT
Jul 8 09:37:50.553142 (XEN) [error_code=0002]
Jul 8 09:37:50.561031 (XEN) Faulting linear address: 0000000000000000
Jul 8 09:37:50.561065 (XEN) ****************************************
next prev parent reply other threads:[~2015-07-08 12:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 12:42 [xen-unstable test] 59160: regressions - FAIL osstest service owner
2015-07-08 12:47 ` Ian Campbell [this message]
2015-07-08 13:59 ` Dario Faggioli
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=1436359630.23508.37.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=ian.jackson@eu.citrix.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.