From: Dario Faggioli <dario.faggioli@citrix.com>
To: Julien Grall <julien.grall@arm.com>,
osstest service owner <osstest-admin@xenproject.org>,
xen-devel@lists.xensource.com
Cc: Stefano Stabellini <stefano@stabellini.net>
Subject: Re: Guest start issue on ARM (maybe related to Credit2) [Was: Re: [xen-unstable test] 113807: regressions - FAIL]
Date: Tue, 26 Sep 2017 09:33:46 +0200 [thread overview]
Message-ID: <1506411226.27663.28.camel@citrix.com> (raw)
In-Reply-To: <f377c003-56eb-af51-3e18-71926c271815@arm.com>
[-- Attachment #1.1: Type: text/plain, Size: 1689 bytes --]
On Mon, 2017-09-25 at 17:23 +0100, Julien Grall wrote:
> On 09/25/2017 03:07 PM, Dario Faggioli wrote:
> > 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-ar
> > mhf-
> > armhf-xl/xen-unstable
> >
> Most of the time guest-start/debian.repeat fails, vCPU 0 is in
> data/prefetch abort state. My guess is a latent cache bug that
> credit2
> appears to expose.
>
So, forgive my ARM ignorance, but how do you tell that the vCPU(s)
is(are) in that particular state?
I'm asking because I now wonder whether this same issue could also be
the cause of these other failures, which we see from time to time:
flight 113816 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/113816/
[...]
Tests which did not succeed, but are not blocking:
test-armhf-armhf-xl-rtds 16 guest-start/debian.repeat fail blocked in 113387
Here's the logs:
http://logs.test-lab.xenproject.org/osstest/logs/113816/test-armhf-armhf-xl-rtds/info.html
Thanks and 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-26 7:33 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 ` Guest start issue on ARM (maybe related to Credit2) [Was: Re: [xen-unstable test] 113807: regressions - FAIL] Dario Faggioli
2017-09-25 16:23 ` Julien Grall
2017-09-25 17:29 ` Dario Faggioli
2017-09-26 7:33 ` Dario Faggioli [this message]
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=1506411226.27663.28.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).