From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>,
openembedded-core <openembedded-core@lists.openembedded.org>
Cc: "saul.wold" <saul.wold@intel.com>
Subject: Re: [PATCH] scripts/runqemu-internal: Work around qemux86 PAT bugs in linux 4.4.1
Date: Sat, 13 Feb 2016 08:10:31 +0000 [thread overview]
Message-ID: <1455351031.16142.338.camel@linuxfoundation.org> (raw)
In-Reply-To: <56BE56F9.2030806@windriver.com>
On Fri, 2016-02-12 at 17:04 -0500, Bruce Ashfield wrote:
> On 2016-02-12 1:00 PM, Richard Purdie wrote:
> > Since the upgrade of qemux86 to 4.4.1 we're seeing PAT issues when
> > starting the X server. We need to fix the problem but the failing
> > sanity tests mask out other issues and we need a workaround.
> >
>
> I was out of the day and didn't notice if any logs were available
> for the issue ? Is there a pointer to the failing logs ?
>
> Obviously I didn't notice this in any of my runs. I'll check 4.4.x
> for anything that looks suspicious, and can bisect if needed.
Your inbox should have details of it under "poky: update qemu* to
prefer 4.4 kernel", the logs are in there. There was a promising
looking patch upstream but it didn't help.
It reproduced easily with a "MACHINE=qemux86 bitbake core-image-sato;
runqemu qemux86" and then watch X fail to start.
It also looks like we have a new perf race:
https://autobuilder.yoctoproject.org/main/builders/nightly-x86-64/build
s/657/steps/BuildImages/logs/stdio
Cheers,
Richard
prev parent reply other threads:[~2016-02-13 8:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 18:00 [PATCH] scripts/runqemu-internal: Work around qemux86 PAT bugs in linux 4.4.1 Richard Purdie
2016-02-12 22:04 ` Bruce Ashfield
2016-02-13 8:10 ` Richard Purdie [this message]
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=1455351031.16142.338.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.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