From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: "Lock, Joshua" <joshua.g.lock@intel.com>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Fix for the APIC hangs in qemux86-64
Date: Wed, 13 Dec 2017 14:05:04 +0000 [thread overview]
Message-ID: <1513173904.16507.1.camel@linuxfoundation.org> (raw)
In-Reply-To: <694b540b-1fc8-0388-5419-01c6e3f100c6@windriver.com>
On Wed, 2017-12-13 at 08:38 -0500, Bruce Ashfield wrote:
> On 12/13/2017 07:34 AM, Richard Purdie wrote:
> >
> > Hi Bruce,
> >
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=12301
> >
> > We've root caused the hangs we're seeing in qemux86-64 on our
> > autobuilder workers. We've identified a commit on 4.15-rc3 which
> > fixes
> > the issue but backporting it to the autobuilder's host kernels will
> > be
> > a pain.
> >
> > As a workaround I'd like to enable x2apic on qemux86-64. Since that
> > works via MSRs it avoids the problem.
> >
> > Would it be a big issue to set CONFIG_X86_X2APIC=y for qemux86-64?
> Nope. No big deal at all. I've used the same config i the past
> when doing work with rt-KVM, so I know it well.
>
> I'll prep a commit, and send it along as part of a rebased set
> of kernel patches.
Thanks, much appreciated.
Did we get to the bottom of the 4.12 selftest failures?
We may also need to backport the defconfig change back to the older
releases so we don't get the hangs in those builds either...
Cheers,
Richard
next prev parent reply other threads:[~2017-12-13 14:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 12:34 Fix for the APIC hangs in qemux86-64 Richard Purdie
2017-12-13 13:38 ` Bruce Ashfield
2017-12-13 14:05 ` Richard Purdie [this message]
2017-12-13 14:07 ` Bruce Ashfield
2017-12-13 14:14 ` Richard Purdie
2017-12-13 14:17 ` Bruce Ashfield
2017-12-13 14:24 ` Burton, Ross
2017-12-13 14:25 ` Bruce Ashfield
2017-12-14 0:01 ` Bruce Ashfield
2017-12-14 0:04 ` Richard Purdie
2017-12-14 0:05 ` Bruce Ashfield
2017-12-14 1:12 ` Bruce Ashfield
2017-12-14 15:00 ` Bruce Ashfield
2017-12-15 12:34 ` Burton, Ross
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=1513173904.16507.1.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@windriver.com \
--cc=joshua.g.lock@intel.com \
--cc=openembedded-core@lists.openembedded.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