From: Robby Workman <rw@rlworkman.net>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [SOLVED] CPU too old panic on Centrino proc - 2.6.22.6
Date: Tue, 18 Sep 2007 14:45:04 -0500 [thread overview]
Message-ID: <46F02AC0.7090607@rlworkman.net> (raw)
In-Reply-To: <p73sl5bx2an.fsf@bingen.suse.de>
Andi Kleen wrote:
> Robby Workman <rw@rlworkman.net> writes:
>
>> On booting a 2.6.22.6 kernel with SMP support, I get a panic
>> immediately:
>> PANIC: CPU too old for this kernel
>> This panic does not occur on a non-SMP kernel having almost
>> identical configuration.
>>
>> This is on a Thinkpad T41:
>> /proc/cpuinfo --> http://rlworkman.net/cpuinfo
>> dmesg --> http://rlworkman.net/dmesg
>> kernel config --> http://rlworkman.net/config-2.6.22.6
>>
>> The 2.6.21.5 SMP kernels from Slackware 12.0 all boot properly, and
>> the config for this 2.6.22.6 SMP kernel is based on the one from 12.0.
>>
>> I'm basically reaching for clues at this point -- is this a PEBKAC on
>> my part? What other information would be useful?
>
> Most likely you enabled CONFIG_HIGHMEM64G. Banias didn't support
> PAE.
Thanks, Andi - that was indeed the problem. Of course, things like
this are never solved until asked about on a mailing list :)
HIGHMEM4G rather than HIGHMEM64G (not sure why I had that marked),
no PAE, and I was using the 64-bit memory/IO (EXPERIMENTAL). Now it's
off. A side effect was CONFIG_X86_CMPXCHG64 disappearing from the
.config, which I thought might have also been part of the problem
based on that other thread.
Either way, thanks for the response!
-RW
prev parent reply other threads:[~2007-09-18 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 15:40 CPU too old panic on Centrino proc - 2.6.22.6 Robby Workman
2007-09-18 18:21 ` Andi Kleen
2007-09-18 19:45 ` Robby Workman [this message]
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=46F02AC0.7090607@rlworkman.net \
--to=rw@rlworkman.net \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.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 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.