From: Dario Faggioli <dario.faggioli@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>, osstest-admin@xenproject.org
Subject: Re: [xen-unstable test] 88047: regressions - FAIL
Date: Fri, 1 Apr 2016 16:40:00 +0200 [thread overview]
Message-ID: <1459521600.5082.280.camel@citrix.com> (raw)
In-Reply-To: <56FE974302000078000E213B@prv-mh.provo.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 1591 bytes --]
On Fri, 2016-04-01 at 07:44 -0600, Jan Beulich wrote:
> > On 01.04.16 at 15:36, <Ian.Jackson@eu.citrix.com> wrote:
> > That message is from libvirt. I don't know the exact situation.
> >
> > But we have seen other timeouts with merlot[01]. They seem to
> > sometimes have weird stalls when running under Xen.
> Might it be worth trying whether that's a deep C-state issue (by
> temporarily limiting their use of deep C states)?
>
IIRC, it's the box(es) with the weird NUMA setup... something about
nodes without any memory:
Apr 1 01:03:31.095559 (XEN) SRAT: Node 0 PXM 0 0-a0000
Apr 1 01:03:31.103546 (XEN) SRAT: Node 0 PXM 0 100000-c0000000
Apr 1 01:03:31.103565 (XEN) SRAT: Node 0 PXM 0 100000000-240000000
Apr 1 01:03:31.111600 (XEN) SRAT: Node 2 PXM 2 240000000-43f000000
Apr 1 01:03:31.111619 (XEN) NUMA: Allocated memnodemap from 43ee16000 - 43ee1b000
Apr 1 01:03:31.119615 (XEN) NUMA: Using 8 for the hash shift.
Apr 1 01:03:31.127613 (XEN) SRAT: Node 1 has no memory. BIOS Bug or mis-configured hardware?
Apr 1 01:03:31.135548 (XEN) SRAT: Node 3 has no memory. BIOS Bug or mis-configured hardware?
Not that I see how this could cause the long latencies / timeouts, though... :-/
In any case, I think Jan's C states suggestion is worth a shot.
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: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-01 14:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 6:12 [xen-unstable test] 88047: regressions - FAIL osstest service owner
2016-04-01 9:43 ` Jan Beulich
2016-04-01 13:36 ` Ian Jackson
2016-04-01 13:44 ` Jan Beulich
2016-04-01 14:40 ` Dario Faggioli [this message]
2016-04-01 14:56 ` Ian Jackson
2016-04-01 15:32 ` 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=1459521600.5082.280.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=osstest-admin@xenproject.org \
--cc=xen-devel@lists.xenproject.org \
/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).