From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: "Hart, Darren" <darren.hart@intel.com>,
"saul.wold" <saul.wold@intel.com>,
poky@yoctoproject.org,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [poky] [PATCH 1/1] poky: update qemu* to prefer 4.4 kernel
Date: Wed, 09 Mar 2016 21:23:44 +0000 [thread overview]
Message-ID: <1457558624.2804.181.camel@linuxfoundation.org> (raw)
In-Reply-To: <56E07128.2060401@windriver.com>
On Wed, 2016-03-09 at 13:53 -0500, Bruce Ashfield wrote:
> On 2016-03-01 8:41 PM, Paul Gortmaker wrote:
> > [Re: [poky] [PATCH 1/1] poky: update qemu* to prefer 4.4 kernel] On
> > 13/02/2016 (Sat 17:17) Richard Purdie wrote:
> >
> > > I'm moving the discussion to OE-Core and pulling in some kernel
> > > people.
> > > I think I understand what is wrong and how to fix it but I could
> > > use
> > > someone who actually knows this code.
> > >
> > > To summarise the story so far, on qemux86, X doesn't start and
> > > there is
> > > a backtrace in the logs:
> > >
> > > x86/PAT: Xorg:705 map pfn expected mapping type uncached-minus
> > > for [mem 0xfd000000-0xfdffffff], got write-combining
> >
> > So Bruce helped me set up a reproducer locally today since he'd
> > already
> > invested the time on that, and then I boiled that down to divorce
> > it
> > from the slower steps of build-deploy-boot to make the bisect
> > something
> > that mortal humans could tolerate.
> >
> > Amusingly enough that led to:
> >
> > commit 9cd25aac1f44f269de5ecea11f7d927f37f1d01c
> > Author: Borislav Petkov <bp@suse.de>
> > Date: Thu Jun 4 18:55:10 2015 +0200
> >
> > x86/mm/pat: Emulate PAT when it is disabled
> >
> > So while some of us were joking on IRC about the validity of
> > forcibly
> > disabling PAT (via cmdline or Kconfig) as a workaround, the one
> > line
> > shortlog above tells us that it wasn't so off the mark after all.
> >
> > Bruce and I will decide what to do with this tomorrow, but since
> > Richard
> > spent so much time on it, I thought he'd like to know this in the
> > interim. Good times. :-/
>
> As another follow up. The thread can be summarized as "It doesn't
> look like it should have worked before, and qemu's pat emulation
> may be the issue'.
>
> The suggestion is to run with 'nopat', which is what Richard
> originally
> did.
>
> So I'm going to prep a patch that drops the kernel patch, and leaves
> nopat enabled on the qemu command line. That should get us put back
> together in a semi-permanent way.
How sure are we this is a bug in QEMU's pat emulation? If that is the
case we should file a bug against qemu and try and fix it rather than
work around it...
Cheers,
Richard
next prev parent reply other threads:[~2016-03-09 21:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1455203562.git.bruce.ashfield@windriver.com>
[not found] ` <2e6d2b75837731be983d888eaa82a9cfcf660e85.1455203562.git.bruce.ashfield@windriver.com>
[not found] ` <1455287765.16142.321.camel@linuxfoundation.org>
[not found] ` <1455291157.16142.323.camel@linuxfoundation.org>
[not found] ` <1455352317.16142.344.camel@linuxfoundation.org>
2016-02-13 17:17 ` [poky] [PATCH 1/1] poky: update qemu* to prefer 4.4 kernel Richard Purdie
2016-02-13 18:19 ` Bruce Ashfield
2016-02-14 16:29 ` Paul Gortmaker
2016-03-02 1:41 ` Paul Gortmaker
2016-03-09 18:53 ` Bruce Ashfield
2016-03-09 21:23 ` Richard Purdie [this message]
2016-03-10 4:12 ` Bruce Ashfield
2016-03-10 20:59 ` Richard Purdie
2016-03-10 21:55 ` Bruce Ashfield
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=1457558624.2804.181.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@windriver.com \
--cc=darren.hart@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.gortmaker@windriver.com \
--cc=poky@yoctoproject.org \
--cc=saul.wold@intel.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