From: Ian W MORRISON <ianwmorrison@gmail.com>
To: Doug Smythies <dsmythies@telus.net>
Cc: Bernhard Held <berny156@gmx.de>,
Mikulas Patocka <mpatocka@redhat.com>,
Andy Lutomirski <luto@kernel.org>, Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [tip:x86/urgent] x86/PAT: Fix Xorg regression on CPUs that don't support PAT
Date: Thu, 1 Jun 2017 17:49:25 +1000 [thread overview]
Message-ID: <CAFXWsS-1zkE8Q0BX06g5LYwPqGR+gQbR9D6=EO2r_B1-nn-HeQ@mail.gmail.com> (raw)
In-Reply-To: <003501d2d9a8$4ee48d20$ecada760$@net>
On 31 May 2017 at 10:53, Doug Smythies <dsmythies@telus.net> wrote:
> Note Before:
> I might not have the address list correct, as I have re-created this
> e-mail from the web page archive, having found the thread after bisecting the
> kernel.
>
> On 2017.05.29 18:50:57 -0400 (EDT) Mikulas Patocka wrote:
>> On Sun, 28 May 2017, Andy Lutomirski wrote:
>>> On Sun, May 28, 2017 at 11:18 AM, Bernhard Held <berny156@gmx.de> wrote:
>>>> Hi,
>>>>
>>>> this patch breaks the boot of my kernel. The last message is "Booting
>>>> the kernel.".
>
> It breaks my kernel boot also, and I know of at least two others with
> the same, or similar, problem as of kernel 4.12-rc3.
>
Just to add that I cannot boot v4.12-rc3 kernel with any Intel Atom
(BYT and CHT) Intel Compute Sticks. Adding 'earlyprintk=efi' confirms
kernel panic with
[ 0.000000] Kernel panic - not syncing: x86/PAT: PAT enabled, but not
supported by secondary CPU
<snip>
next prev parent reply other threads:[~2017-06-01 7:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 0:53 [tip:x86/urgent] x86/PAT: Fix Xorg regression on CPUs that don't support PAT Doug Smythies
2017-06-01 7:49 ` Ian W MORRISON [this message]
2017-06-01 14:48 ` Ian W MORRISON
-- strict thread matches above, loose matches on Subject: below --
2017-06-02 6:32 Ian W MORRISON
2017-04-18 19:07 [PATCH] X86: don't report PAT on CPUs that don't support it Mikulas Patocka
2017-05-24 10:21 ` [tip:x86/urgent] x86/PAT: Fix Xorg regression on CPUs that don't support PAT tip-bot for Mikulas Patocka
2017-05-28 18:18 ` Bernhard Held
2017-05-28 18:43 ` Andy Lutomirski
2017-05-29 22:50 ` Mikulas Patocka
2017-05-30 17:14 ` Dominik Brodowski
2017-05-30 17:59 ` Mikulas Patocka
2017-05-30 18:47 ` Dominik Brodowski
2017-05-30 19:30 ` Bernhard Held
2017-05-31 9:39 ` Junichi Nomura
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='CAFXWsS-1zkE8Q0BX06g5LYwPqGR+gQbR9D6=EO2r_B1-nn-HeQ@mail.gmail.com' \
--to=ianwmorrison@gmail.com \
--cc=berny156@gmx.de \
--cc=dsmythies@telus.net \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=mpatocka@redhat.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 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.