From: "H. Peter Anvin" <hpa@zytor.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>,
Chris Bainbridge <chris.bainbridge@gmail.com>
Cc: davej@redhat.com, x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: set Pentium M as PAE capable
Date: Wed, 26 Feb 2014 08:45:41 -0800 [thread overview]
Message-ID: <530E1A35.40506@zytor.com> (raw)
In-Reply-To: <20140226164433.GA19341@srcf.ucam.org>
On 02/26/2014 08:44 AM, Matthew Garrett wrote:
> On Wed, Feb 26, 2014 at 07:12:59PM +0700, Chris Bainbridge wrote:
>
>> The basic findings of the bug discussion is that people are successfully
>> running PAE kernels on Pentium M (for some unknown reason Grub skips the
>> validate_cpu code in the kernel, so existing PAE kernels will run
>> unmodified, although they do fail when booted with syslinux), and people
>> are using a user-space hack to add "pae" to /proc/cpuinfo.
>
> grub is jumping to the 32-bit entry point and skipping the entire real
> mode setup code. Bad grub.
>
Yes. Grub can be made to behave sanely by using "linux16" and
"initrd16", but of course none of the distros do it that way.
There are much worse problems with that.
-hpa
next prev parent reply other threads:[~2014-02-26 16:46 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 6:01 [PATCH] x86: set Pentium M as PAE capable Chris Bainbridge
2014-02-25 10:45 ` H. Peter Anvin
2014-02-25 11:35 ` Borislav Petkov
2014-02-25 12:06 ` Peter Hurley
2014-02-25 12:07 ` One Thousand Gnomes
2014-02-25 16:26 ` Dave Jones
2014-02-25 17:16 ` H. Peter Anvin
2014-02-26 12:12 ` Chris Bainbridge
2014-02-26 13:18 ` Borislav Petkov
2014-02-26 15:49 ` Dave Jones
2014-02-26 17:18 ` Borislav Petkov
2014-02-26 17:20 ` Dave Jones
2014-02-26 17:28 ` Borislav Petkov
2014-02-28 7:30 ` Chris Bainbridge
[not found] ` <CAKKYfmFgVjYwvThpB0FBB+ggOwULWKLpz7ADT1eojno_KtD9yw@mail.gmail.com>
2014-02-28 14:00 ` Chris Bainbridge
2014-03-02 20:56 ` Andreas Mohr
2014-03-02 20:59 ` H. Peter Anvin
2014-03-02 21:02 ` Dave Jones
2014-03-02 21:04 ` Borislav Petkov
2014-03-02 21:13 ` Andreas Mohr
2014-03-02 21:42 ` Gene Heskett
2014-03-03 12:31 ` One Thousand Gnomes
2014-03-03 8:04 ` Chris Bainbridge
2014-03-03 19:29 ` Borislav Petkov
2014-03-04 5:01 ` Chris Bainbridge
2014-03-04 5:04 ` H. Peter Anvin
2014-03-04 6:06 ` Chris Bainbridge
2014-03-04 10:44 ` Borislav Petkov
2014-03-05 4:17 ` Chris Bainbridge
2014-03-07 11:40 ` [PATCH] x86: Add forcepae parameter for booting PAE kernels on PAE-disabled Pentium M Chris Bainbridge
2014-03-10 10:25 ` Borislav Petkov
2014-03-20 23:30 ` [tip:x86/cpu] x86, cpu: " tip-bot for Chris Bainbridge
2014-03-20 23:33 ` tip-bot for Chris Bainbridge
2014-03-20 23:30 ` [tip:x86/cpu] Rename TAINT_UNSAFE_SMP to TAINT_CPU_OUT_OF_SPEC tip-bot for Dave Jones
2014-02-26 16:46 ` [PATCH] x86: set Pentium M as PAE capable H. Peter Anvin
2014-02-26 16:44 ` Matthew Garrett
2014-02-26 16:45 ` H. Peter Anvin [this message]
2014-02-26 17:10 ` Matthew Garrett
2014-02-26 17:57 ` H. Peter Anvin
2014-03-03 0:11 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2014-03-02 19:05 Roland Kletzing
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=530E1A35.40506@zytor.com \
--to=hpa@zytor.com \
--cc=chris.bainbridge@gmail.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=x86@kernel.org \
/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