public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: "Пламен Петров" <plamen@petrovi.no-ip.info>,
	linux-kernel@vger.kernel.org
Cc: "'Thomas Gleixner'" <tglx@linutronix.de>
Subject: Re: [BISECTED] 3.19-rc1 regression - kernel does not load in GRUB 0.97 (GRUB Legacy)
Date: Sun, 28 Dec 2014 12:12:02 +0100	[thread overview]
Message-ID: <549FE582.8060108@suse.com> (raw)
In-Reply-To: <000301d0226e$bb275b50$317611f0$@petrovi.no-ip.info>

[-- Attachment #1: Type: text/plain, Size: 1398 bytes --]

On 12/28/2014 08:20 AM, Пламен Петров wrote:
>> -----Original Message-----
>> From: Juergen Gross [mailto:jgross@suse.com]
>> Sent: Saturday, December 27, 2014 3:48 PM
>> To: Пламен Петров; linux-kernel@vger.kernel.org
>> Cc: 'Thomas Gleixner'
>> Subject: Re: [BISECTED] 3.19-rc1 regression - kernel does not load in GRUB
>> 0.97 (GRUB Legacy)
>>
>> On 12/24/2014 01:28 AM, Пламен Петров wrote:
>>> Hello!
>>>
>>> I use GRUB Legacy bootloader (version 0.97) on a couple machines, and
>>> where 3.18.x loads fine, 3.19-rc1 does not.
>>>
>>> While compiling I used the attached .config file accompanied by "make
>>> olddefconfig"
>>
>> Can you tell me something about the hardware (processor model)?
>> You are not booting the system under VMWare by any chance?
>
> As a matter of fact - I am compiling in a VMware Player (6.0.3
> build-1895310) virtual machine, boot testing there, and then if everything
> is OK, I transfer the monolithic kernel produced on 3 virtual machines that
> run on EXSi and 2 actual servers. So along those lines - the failing
> 3.19-rc1 never saw actual hardware - it was all tested (and bisected) inside
> a VM.

Thanks. VMWare having problems with my patch is a known issue. I've
already sent a patch working around that issue (VMWare has a bug
emulating the PAT MSR). You can either use that patch (attached for
your convenience) or use the "nopat" option.


Juergen


[-- Attachment #2: 0001-x86-don-t-rely-on-VMWare-emulating-PAT-MSR-correctly.patch --]
[-- Type: text/x-patch, Size: 1318 bytes --]

>From 4b65fb80338c71673cabfa9fa9b0f80f5a4bc320 Mon Sep 17 00:00:00 2001
From: Juergen Gross <jgross@suse.com>
Date: Tue, 16 Dec 2014 07:43:51 +0100
Subject: [PATCH] x86: don't rely on VMWare emulating PAT MSR correctly

VMWare seems not to emulate the PAT MSR correctly: reaeding
MSR_IA32_CR_PAT returns 0 even after writing another value to it.

Detect this bug and don't use the read value if it is 0.

Commit bd809af16e3ab1f8d55b3e2928c47c67e2a865d2 ("x86: Enable PAT to
use cache mode translation tables") triggers this VMWare bug when the
kernel is booted as a VMWare guest.

Reported-by: Jongman Heo <jongman.heo@samsung.com>
Signed-off-by: Juergen Gross <jgross@suse.com>
Tested-by: Jongman Heo <jongman.heo@samsung.com>
---
 arch/x86/mm/pat.c | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/arch/x86/mm/pat.c b/arch/x86/mm/pat.c
index edf299c..7ac6869 100644
--- a/arch/x86/mm/pat.c
+++ b/arch/x86/mm/pat.c
@@ -234,8 +234,13 @@ void pat_init(void)
 	      PAT(4, WB) | PAT(5, WC) | PAT(6, UC_MINUS) | PAT(7, UC);
 
 	/* Boot CPU check */
-	if (!boot_pat_state)
+	if (!boot_pat_state) {
 		rdmsrl(MSR_IA32_CR_PAT, boot_pat_state);
+		if (!boot_pat_state) {
+			pat_disable("PAT read returns always zero, disabled.");
+			return;
+		}
+	}
 
 	wrmsrl(MSR_IA32_CR_PAT, pat);
 
-- 
2.1.2


  reply	other threads:[~2014-12-28 11:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-24  0:28 [BISECTED] 3.19-rc1 regression - kernel does not load in GRUB 0.97 (GRUB Legacy) Пламен Петров
2014-12-27 13:47 ` Juergen Gross
2014-12-28  7:20   ` Пламен Петров
2014-12-28 11:12     ` Juergen Gross [this message]
2015-01-05 10:26       ` yzhu1
2014-12-28  7:30   ` Пламен Петров

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=549FE582.8060108@suse.com \
    --to=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=plamen@petrovi.no-ip.info \
    --cc=tglx@linutronix.de \
    /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