linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
	Bandan Das <bsd@redhat.com>
Subject: Re: Linux 5.3-rc7
Date: Sat, 07 Sep 2019 15:41:19 +0100	[thread overview]
Message-ID: <156786727951.13300.15226856788926071603@skylake-alporthouse-com> (raw)
In-Reply-To: <alpine.DEB.2.21.1909071628420.1902@nanos.tec.linutronix.de>

Quoting Thomas Gleixner (2019-09-07 15:29:19)
> On Sat, 7 Sep 2019, Chris Wilson wrote:
> > Quoting Linus Torvalds (2019-09-02 18:28:26)
> > > Bandan Das:
> > >       x86/apic: Include the LDR when clearing out APIC registers
> > 
> > Apologies if this is known already, I'm way behind on email.
> > 
> > I've bisected
> > 
> > [   18.693846] smpboot: CPU 0 is now offline
> > [   19.707737] smpboot: Booting Node 0 Processor 0 APIC 0x0
> > [   29.707602] smpboot: do_boot_cpu failed(-1) to wakeup CPU#0
> > 
> > https://intel-gfx-ci.01.org/tree/drm-tip/igt@perf_pmu@cpu-hotplug.html
> > 
> > to 558682b52919. (Reverts cleanly and fixes the problem.)
> > 
> > I'm guessing that this is also behind the suspend failures, missing
> > /dev/cpu/0/msr, and random perf_event_open() failures we have observed
> > in our CI since -rc7 across all generations of Intel cpus.
> 
> So is this on bare metal or in a VM?

Our single virtualised piece of kit doesn't support cpu hotplug, so this
test is not being run. We have failures on
icl (2019), glk (2017), kbl (2017), bxt (2016), skl (2015),
bsw (2016), hsw (2013), byt (2013), snb (2011), elk (2008),
bwr (2006), blb (2007)
-Chris

  reply	other threads:[~2019-09-07 14:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-02 17:28 Linux 5.3-rc7 Linus Torvalds
2019-09-07 10:10 ` Chris Wilson
2019-09-07 14:29   ` Thomas Gleixner
2019-09-07 14:41     ` Chris Wilson [this message]
2019-09-07 15:00       ` Thomas Gleixner
2019-09-07 15:24         ` Chris Wilson
2019-09-07 20:12           ` Thomas Gleixner
2019-09-07 19:17         ` Linus Torvalds
2019-09-07 19:27           ` Linus Torvalds
2019-09-09 13:54             ` Bandan Das
2019-09-07 20:44           ` Thomas Gleixner
2019-09-07 21:13             ` Linus Torvalds
2019-09-08 11:02               ` Sasha Levin

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=156786727951.13300.15226856788926071603@skylake-alporthouse-com \
    --to=chris@chris-wilson.co.uk \
    --cc=bsd@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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).