linux-kernel - Re: [SOLVED] CPU too old panic on Centrino proc

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 for Android: free password hash cracker in your pocket

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

Message-ID: <46F02AC0.7090607@rlworkman.net>
Date:	Tue, 18 Sep 2007 14:45:04 -0500
From:	Robby Workman <rw@...orkman.net>
To:	Andi Kleen <andi@...stfloor.org>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [SOLVED] CPU too old panic on Centrino proc - 2.6.22.6

Andi Kleen wrote:
> Robby Workman <rw@...orkman.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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/