linux-kernel - Re: [BISECTED] 3.19-rc1 regression - kernel does not load in GRUB 0.97 (GRUB Legacy)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 28 Dec 2014 12:12:02 +0100
From:	Juergen Gross <jgross@...e.com>
To:	Пламен Петров 
	<plamen@...rovi.no-ip.info>, linux-kernel@...r.kernel.org
CC:	'Thomas Gleixner' <tglx@...utronix.de>
Subject: Re: [BISECTED] 3.19-rc1 regression - kernel does not load in GRUB
 0.97 (GRUB Legacy)

On 12/28/2014 08:20 AM, Пламен Петров wrote:
>> -----Original Message-----
>> From: Juergen Gross [mailto:jgross@...e.com]
>> Sent: Saturday, December 27, 2014 3:48 PM
>> To: Пламен Петров; linux-kernel@...r.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


View attachment "0001-x86-don-t-rely-on-VMWare-emulating-PAT-MSR-correctly.patch" of type "text/x-patch" (1319 bytes)