All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 1/1] poky: update qemu* to prefer 4.4 kernel
Date: Sat, 13 Feb 2016 08:31:57 +0000	[thread overview]
Message-ID: <1455352317.16142.344.camel@linuxfoundation.org> (raw)
In-Reply-To: <1455291157.16142.323.camel@linuxfoundation.org>

On Fri, 2016-02-12 at 15:32 +0000, Richard Purdie wrote:
> On Fri, 2016-02-12 at 14:36 +0000, Richard Purdie wrote:
> > A quick look at upstream makes me wonder about:
> > 
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/com
> > mi
> > t/?id=d9fe4fab11976e56b2e992980bf6ce948bdf02ac
> > 
> > which changes the code in this area.
> 
> FWIW this doesn't help, the problem still exists after applying it.
> 
> Setting CONFIG_X86_PAT to is not set in the defconfig did "fix" it,
> unsurprisingly.

Also, in the last set of builds, despite booting with "nopat", we see:

https://autobuilder.yoctoproject.org/main/builders/nightly-x86-lsb/buil
ds/637/steps/Running%20Sanity%20Tests/logs/stdio

Central error: [    9.298049] Failed to add WC MTRR for [fd000000-fdffffff]; performance may suffer.

Why we only see this on the lsb run I don't know but that address looks
like the one causing problems elsewhere with PAT. It could therefore
look like this is related to uvesafb.

Cheers,

Richard


  reply	other threads:[~2016-02-13  8:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-11 15:15 [PATCH 0/1] meta-yocto: bump qemu preferred version to 4.4 Bruce Ashfield
2016-02-11 15:15 ` [PATCH 1/1] poky: update qemu* to prefer 4.4 kernel Bruce Ashfield
2016-02-12 14:36   ` Richard Purdie
2016-02-12 15:32     ` Richard Purdie
2016-02-13  8:31       ` Richard Purdie [this message]
2016-02-13 17:17         ` Richard Purdie
2016-02-13 17:17           ` [poky] " Richard Purdie
2016-02-13 18:19           ` Bruce Ashfield
2016-02-13 18:19             ` [poky] " Bruce Ashfield
2016-02-14 16:29           ` Paul Gortmaker
2016-02-14 16:29             ` [poky] " Paul Gortmaker
2016-03-02  1:41           ` Paul Gortmaker
2016-03-02  1:41             ` [poky] " Paul Gortmaker
2016-03-09 18:53             ` Bruce Ashfield
2016-03-09 18:53               ` [poky] " Bruce Ashfield
2016-03-09 21:23               ` Richard Purdie
2016-03-09 21:23                 ` [poky] " Richard Purdie
2016-03-10  4:12                 ` Bruce Ashfield
2016-03-10  4:12                   ` [poky] " Bruce Ashfield
2016-03-10 20:59                   ` Richard Purdie
2016-03-10 20:59                     ` [poky] " Richard Purdie
2016-03-10 21:55                     ` Bruce Ashfield
2016-03-10 21:55                       ` [poky] " Bruce Ashfield
2016-02-13 18:16         ` 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=1455352317.16142.344.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bruce.ashfield@windriver.com \
    --cc=poky@yoctoproject.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.