From: Dario Faggioli <dario.faggioli@citrix.com>
To: osstest service owner <osstest-admin@xenproject.org>,
xen-devel@lists.xensource.com
Cc: Julien Grall <julien.grall@arm.com>,
Stefano Stabellini <stefano@stabellini.net>
Subject: Guest start issue on ARM (maybe related to Credit2) [Was: Re: [xen-unstable test] 113807: regressions - FAIL]
Date: Mon, 25 Sep 2017 16:07:40 +0200 [thread overview]
Message-ID: <1506348460.27663.3.camel@citrix.com> (raw)
In-Reply-To: <osstest-113807-mainreport@xen.org>
[-- Attachment #1.1: Type: text/plain, Size: 1894 bytes --]
Hey,
On Mon, 2017-09-25 at 09:46 +0000, osstest service owner wrote:
> flight 113807 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/113807/
>
So, triggered by this:
> Tests which are failing intermittently (not blocking):
> test-armhf-armhf-xl-credit2 16 guest-start/debian.repeat fail in
> 113791 pass in 113807
>
I went having a look, and discovered that it's indeed happening that,
from time to time, we fail to create a guest, on ARM, with Credit2.
Looking here:
http://logs.test-lab.xenproject.org/osstest/results/history/test-armhf-armhf-xl-credit2/xen-unstable
It seems to be happening only on the cubietracks, but in a non-linear
and non-deterministic fashion. E.g., 113791 failed on metzinger, which
is fine on 113800; 113611 and 113618 failed on baroque, which is fine
on 113638.
I don't see much in the logs, TBH, but both `xl vcpu-list' and the 'r'
debug key seem to suggest that vCPU 0 is running, while the other vCPUs
have never run... like it was an issue with secondary (v)CPU bringup.
It indeed shows up with Credit2, as it were _specific_ to it, but I'm
not 100% sure. In fact, it indeed seems to never show up here:
http://logs.test-lab.xenproject.org/osstest/results/history/test-armhf-
armhf-xl/xen-unstable
but it looks like it may have shown up in 112460 (but we don't have the
logs any longer):
http://logs.test-lab.xenproject.org/osstest/results/history/test-armhf-
armhf-xl-cubietruck/xen-unstable
So... ARM people? Does this ring any bell? Is this something known, or
easy to explain? What can I do for help?
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
next prev parent reply other threads:[~2017-09-25 14:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 9:46 [xen-unstable test] 113807: regressions - FAIL osstest service owner
2017-09-25 14:07 ` Dario Faggioli [this message]
2017-09-25 16:23 ` Guest start issue on ARM (maybe related to Credit2) [Was: Re: [xen-unstable test] 113807: regressions - FAIL] Julien Grall
2017-09-25 17:29 ` Dario Faggioli
2017-09-26 7:33 ` Dario Faggioli
2017-09-26 17:28 ` Julien Grall
2017-09-26 20:51 ` Dario Faggioli
2017-09-27 23:51 ` Julien Grall
2017-09-27 23:52 ` Julien Grall
2017-09-28 9:38 ` 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=1506348460.27663.3.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=julien.grall@arm.com \
--cc=osstest-admin@xenproject.org \
--cc=stefano@stabellini.net \
--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).