From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751284AbdFAHt2 (ORCPT ); Thu, 1 Jun 2017 03:49:28 -0400 Received: from mail-yw0-f195.google.com ([209.85.161.195]:36437 "EHLO mail-yw0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751001AbdFAHt0 (ORCPT ); Thu, 1 Jun 2017 03:49:26 -0400 MIME-Version: 1.0 In-Reply-To: <003501d2d9a8$4ee48d20$ecada760$@net> References: <003501d2d9a8$4ee48d20$ecada760$@net> From: Ian W MORRISON Date: Thu, 1 Jun 2017 17:49:25 +1000 Message-ID: Subject: Re: [tip:x86/urgent] x86/PAT: Fix Xorg regression on CPUs that don't support PAT To: Doug Smythies Cc: Bernhard Held , Mikulas Patocka , Andy Lutomirski , Ingo Molnar , linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 31 May 2017 at 10:53, Doug Smythies 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 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