From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
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: Fri, 12 Feb 2016 17:04:41 -0500 [thread overview]
Message-ID: <56BE56F9.2030806@windriver.com> (raw)
In-Reply-To: <1455300000.16142.331.camel@linuxfoundation.org>
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.
Bruce
> Merge this for now until we can figure out the full issue. This is
> better than changing the kernel defconfig or reverting to old
> kernel versions.
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>
> diff --git a/scripts/runqemu-internal b/scripts/runqemu-internal
> index ebed2bd..ad854d1 100755
> --- a/scripts/runqemu-internal
> +++ b/scripts/runqemu-internal
> @@ -434,7 +434,7 @@ if [ "$MACHINE" = "qemux86" ]; then
> fi
> # Currently oprofile's event based interrupt mode doesn't work(Bug #828) in
> # qemux86 and qemux86-64. We can use timer interrupt mode for now.
> - KERNCMDLINE="$KERNCMDLINE oprofile.timer=1"
> + KERNCMDLINE="$KERNCMDLINE oprofile.timer=1 nopat"
> fi
>
> if [ "$MACHINE" = "qemux86-64" ]; then
>
>
next prev parent reply other threads:[~2016-02-12 22:04 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 [this message]
2016-02-13 8:10 ` Richard Purdie
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=56BE56F9.2030806@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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