From: Dario Faggioli <dario.faggioli@citrix.com>
To: osstest service owner <osstest-admin@xenproject.org>,
xen-devel@lists.xensource.com
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [xen-unstable test] 100518: regressions - FAIL
Date: Thu, 18 Aug 2016 15:32:27 +0200 [thread overview]
Message-ID: <1471527147.6806.96.camel@citrix.com> (raw)
In-Reply-To: <osstest-100518-mainreport@xen.org>
[-- Attachment #1.1: Type: text/plain, Size: 6037 bytes --]
On Wed, 2016-08-17 at 13:04 +0000, osstest service owner wrote:
> flight 100518 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/100518/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-amd64-xl-qemut-winxpsp3 17 guest-start/win.repeat fail
> REGR. vs. 100488
>
So, FTR, Jan pointed out to me and George that this has failed like
this:
Aug 17 04:51:03.173959 (XEN) ----[ Xen-4.8-unstable x86_64 debug=y Not tainted ]----
Aug 17 04:51:23.770049 (XEN) CPU: 0
Aug 17 04:51:23.770111 (XEN) RIP: e008:[<ffff82d080124d71>] sched_credit.c#_csched_cpu_pick+0x1be/0x62a
Aug 17 04:51:23.778034 (XEN) RFLAGS: 0000000000010287 CONTEXT: hypervisor (d0v0)
Aug 17 04:51:23.786025 (XEN) rax: 0200200200200200 rbx: 0000000000000003 rcx: ffff82d08032e280
Aug 17 04:51:23.794013 (XEN) rdx: 00000031dd4d8200 rsi: ffff82d0802ecd20 rdi: ffff83009550fca8
Aug 17 04:51:23.801996 (XEN) rbp: ffff83009550fd18 rsp: ffff83009550fc28 r8: 0000000000000004
Aug 17 04:51:23.810025 (XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 00000000ffffffff
Aug 17 04:51:23.817966 (XEN) r12: 0000000000000003 r13: ffff8300952f9000 r14: ffff83024e88cf50
Aug 17 04:51:23.825975 (XEN) r15: ffff82d080344ec0 cr0: 0000000080050033 cr4: 00000000001526e0
Aug 17 04:51:23.833993 (XEN) cr3: 0000000240f83000 cr2: 00007f0d36e51b0d
Aug 17 04:51:23.834030 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e010 cs: e008
Aug 17 04:51:23.841976 (XEN) Xen code around <ffff82d080124d71> (sched_credit.c#_csched_cpu_pick+0x1be/0x62a):
Aug 17 04:51:23.849972 (XEN) 18 48 8b 00 48 8b 40 28 <48> 8b 40 10 66 81 38 ff 7f 75 0f 44 3b 25 7d 12
Aug 17 04:51:23.857973 (XEN) Xen stack trace from rsp=ffff83009550fc28:
Aug 17 04:51:23.865960 (XEN) ffff83025d853700 000000020000001f ffff82d080344ec8 ffff82d080344ec0
Aug 17 04:51:23.873956 (XEN) ffff82d0802e96c0 ffff830257af5570 0000000100000001 0000000000000000
Aug 17 04:51:23.881954 (XEN) 0000000000000297 ffff83009550fc88 ffff82d080130a3e 0000000000000000
Aug 17 04:51:23.889950 (XEN) 0000000000000206 ffff83009550fca8 ffff82d080130a3e ffff83025d844000
Aug 17 04:51:23.897962 (XEN) 0000000000000006 0000000000000000 0000000000000000 0000000000000000
Aug 17 04:51:23.906002 (XEN) 000000000000000f 0000000000000000 0000000000000000 0000000000000000
Aug 17 04:51:23.913973 (XEN) ffff83009550fd38 ffff8300952f9000 ffff830247c96000 0000000000000000
Aug 17 04:51:23.914015 (XEN) ffff83024e88cf50 0000000000000000 ffff83009550fd28 ffff82d0801251f8
Aug 17 04:51:23.921976 (XEN) ffff83009550fd78 ffff82d080125227 ffff83009550fd58 ffff82d08013c7a9
Aug 17 04:51:23.929974 (XEN) 0000000000000003 ffff8300952f9000 ffff830247c96000 0000000000000000
Aug 17 04:51:23.937961 (XEN) 0000000000000003 0000000000000000 ffff83009550fd98 ffff82d08012d3ba
Aug 17 04:51:23.945951 (XEN) ffff8300952f9000 ffff830247c96000 ffff83009550fdd8 ffff82d080105d70
Aug 17 04:51:23.953969 (XEN) ffff830257af5570 0000000000000000 ffff830247c96000 00007f0d38354004
Aug 17 04:51:23.961962 (XEN) ffff830257af5570 0000000000000002 ffff83009550fef8 ffff82d0801039df
Aug 17 04:51:23.969963 (XEN) ffff83009550fe18 ffff82d000000000 0000000000000000 0000000000000003
Aug 17 04:51:23.977950 (XEN) 0000000000000000 0000000242214025 ffff830000000001 ffff83009550fea8
Aug 17 04:51:23.985962 (XEN) ffff83009550fea4 ffff82e004818900 0000000c0000000f 00007f0d38140013
Aug 17 04:51:23.993958 (XEN) 0000000000000002 0000000000000000 00007ffe23e9a7c0 00007f0d36e456c8
Aug 17 04:51:24.001946 (XEN) 0000000000000000 00007ffe23e9a7f0 0000000000407f60 00007f0d3814b2e5
Aug 17 04:51:24.009952 (XEN) 0000000000a399f0 0000000000000013 0000000000000002 0000000000000013
Aug 17 04:51:24.017959 (XEN) Xen call trace:
Aug 17 04:51:24.017992 (XEN) [<ffff82d080124d71>] sched_credit.c#_csched_cpu_pick+0x1be/0x62a
Aug 17 04:51:24.025957 (XEN) [<ffff82d0801251f8>] sched_credit.c#csched_cpu_pick+0x1b/0x1d
Aug 17 04:51:24.033963 (XEN) [<ffff82d080125227>] sched_credit.c#csched_vcpu_insert+0x2d/0x157
Aug 17 04:51:24.041949 (XEN) [<ffff82d08012d3ba>] sched_init_vcpu+0x1b8/0x1fe
Aug 17 04:51:24.041984 (XEN) [<ffff82d080105d70>] alloc_vcpu+0x1c8/0x2c7
Aug 17 04:51:24.049995 (XEN) [<ffff82d0801039df>] do_domctl+0x7ea/0x1b24
Aug 17 04:51:24.057972 (XEN) [<ffff82d080242a6d>] lstar_enter+0xdd/0x137
Aug 17 04:51:24.058011 (XEN)
Aug 17 04:51:24.065961 (XEN)
Aug 17 04:51:24.065989 (XEN) ****************************************
Aug 17 04:51:24.066018 (XEN) Panic on CPU 0:
Aug 17 04:51:24.073936 (XEN) GENERAL PROTECTION FAULT
Aug 17 04:51:24.073967 (XEN) [error_code=0000]
Aug 17 04:51:24.073994 (XEN) ****************************************
This looks to me the same thing reported by Andrew a couple of days
ago, and then covered in the following emails/threads:
https://lists.xen.org/archives/html/xen-devel/2016-08/msg01677.html
https://lists.xen.org/archives/html/xen-devel/2016-08/msg01679.html
https://lists.xen.org/archives/html/xen-devel/2016-08/msg01752.html
The fact that, AFAICT, subsequent flights passed (i.e., 100533) is also
consistent with that, as it's basically a race, and hence it is indeed
supposed to manifests itself intermittently.
Patch 1 of this series is my fix:
https://lists.xen.org/archives/html/xen-devel/2016-08/msg02253.html
https://lists.xen.org/archives/html/xen-devel/2016-08/msg02254.html
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-08-18 13:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 13:04 [xen-unstable test] 100518: regressions - FAIL osstest service owner
2016-08-18 13:32 ` Dario Faggioli [this message]
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=1471527147.6806.96.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=george.dunlap@eu.citrix.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 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.