All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Andrew Cooper <Andrew.Cooper3@citrix.com>,
	ian.jackson@eu.citrix.com, Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [xen-unstable test] 57852: regressions - FAIL
Date: Mon, 8 Jun 2015 15:02:22 +0100	[thread overview]
Message-ID: <1433772142.7108.506.camel@citrix.com> (raw)
In-Reply-To: <20150608135058.GC15682@l.oracle.com>

On Mon, 2015-06-08 at 09:50 -0400, Konrad Rzeszutek Wilk wrote:
> On Mon, Jun 08, 2015 at 10:27:32AM +0100, Ian Campbell wrote:
> > On Mon, 2015-06-08 at 10:15 +0100, Jan Beulich wrote:
> > > >>> On 08.06.15 at 10:53, <ian.campbell@citrix.com> wrote:
> > > > That's 6/14 (43%) failure rate on fiano0 and 2/10 (20%) on fiano1. Which
> > > > differs form the apparent xen-unstable failure rate. But I wouldn't take
> > > > this as evidence that the two systems differ significantly, despite how
> > > > the unstable results looked at first glance.
> > > 
> > > So we can basically rule out just one of the hosts being the culprit;
> > > it's either both or our software. Considering that (again at the
> > > example of the recent 4.2 flight) the guest is apparently waiting for
> > > a timer (or other) interrupt (on a HLT instruction), this is very likely
> > > interrupt delivery related, yet (as said before, albeit wrongly for
> > > 4.3) 4.2 doesn't have APICV support yet (4.3 only lack the option
> > > to disable it), so it can't be that (alone).
> > > 
> > > Looking at the hardware - are fiano[01], in terms of CPU and
> > > chipset, perhaps the newest or oldest in the pool? (I'm trying to
> > > make myself a picture of what debugging options we have.)
> > 
> > I don't know much about the hardware in the pool other than what can be
> > gathered from the serial and dmesg logs.
> > 
> > http://logs.test-lab.xenproject.org/osstest/logs/58028/test-amd64-amd64-xl-qemuu-win7-amd64/info.html
> > 
> > >From the serial log and this:
> > 
> > Jun  6 12:09:27.089020 (XEN) VMX: Supported advanced features:
> > Jun  6 12:09:27.089052 (XEN)  - APIC MMIO access virtualisation
> > Jun  6 12:09:27.097051 (XEN)  - APIC TPR shadow
> > Jun  6 12:09:27.097088 (XEN)  - Extended Page Tables (EPT)
> > Jun  6 12:09:27.097118 (XEN)  - Virtual-Processor Identifiers (VPID)
> > Jun  6 12:09:27.105066 (XEN)  - Virtual NMI
> > Jun  6 12:09:27.105100 (XEN)  - MSR direct-access bitmap
> > Jun  6 12:09:27.105130 (XEN)  - Unrestricted Guest
> > Jun  6 12:09:27.113269 (XEN)  - APIC Register Virtualization
> > Jun  6 12:09:27.113290 (XEN)  - Virtual Interrupt Delivery
> > Jun  6 12:09:27.113328 (XEN)  - Posted Interrupt Processing
> > Jun  6 12:09:27.121180 (XEN) HVM: ASIDs enabled.
> > Jun  6 12:09:27.121235 (XEN) HVM: VMX enabled
> > Jun  6 12:09:27.121267 (XEN) HVM: Hardware Assisted Paging (HAP) detected
> > Jun  6 12:09:27.129069 (XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB
> > 
> > I guess they are pretty new?
> 
> Could it be an missing microcode update? I don't know if the OSSTest does
> the ucode=scan or updates the microcode later?

I rather suspect it doesn't do microcode updates at all. (It probably
should)

Is there some reason to expect APICV (or something else) would cause
these failures if microcode wasn't up to date?

Ian.

  reply	other threads:[~2015-06-08 14:02 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04 12:01 [xen-unstable test] 57852: regressions - FAIL osstest service user
2015-06-05  8:45 ` Ian Campbell
2015-06-05  9:00   ` Jan Beulich
2015-06-05  9:07     ` Ian Campbell
2015-06-05  9:18       ` Jan Beulich
2015-06-05 10:48         ` Ian Campbell
2015-06-05 16:46           ` Ian Campbell
2015-06-08  8:07           ` Jan Beulich
2015-06-08  8:53             ` Ian Campbell
2015-06-08  9:15               ` Jan Beulich
2015-06-08  9:27                 ` Ian Campbell
2015-06-08 10:17                   ` Jan Beulich
2015-06-08 14:43                     ` Ian Jackson
2015-06-08 12:16                   ` Ian Campbell
2015-06-08 12:19                     ` Andrew Cooper
2015-06-08 12:24                     ` Jan Beulich
2015-06-09  8:26                     ` Ian Campbell
2015-06-09  9:29                       ` Jan Beulich
2015-06-10  8:50                         ` Ian Campbell
2015-06-10  9:36                           ` Jan Beulich
2015-06-10 11:01                             ` Ian Campbell
2015-06-10 11:48                               ` Jan Beulich
2015-06-10 12:56                                 ` Ian Campbell
2015-06-10 13:23                                   ` Jan Beulich
2015-06-10 13:45                                   ` Jan Beulich
2015-06-10 14:08                                     ` Ian Campbell
2015-06-11  7:02                                       ` Jan Beulich
2015-06-11  8:45                                         ` Ian Campbell
2015-06-15  8:57                                           ` Ian Campbell
2015-06-15  9:03                                             ` Jan Beulich
2015-06-10 14:34                                   ` Ian Campbell
2015-06-10 15:59                                     ` Jan Beulich
2015-06-10 16:18                                       ` Don Slutz
2015-06-10 18:00                                       ` Ian Campbell
2015-06-08 13:50                   ` Konrad Rzeszutek Wilk
2015-06-08 14:02                     ` Ian Campbell [this message]
2015-06-08 14:47                     ` Ian Jackson
2015-06-08 15:21                       ` Konrad Rzeszutek Wilk
2015-06-08 15:29                         ` Ian Campbell
2015-06-08 10:10                 ` Ian Campbell

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=1433772142.7108.506.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=konrad.wilk@oracle.com \
    --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 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.