linux-kernel - 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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Tue, 18 Sep 2007 10:40:35 -0500
From:	Robby Workman <rw@...orkman.net>
To:	linux-kernel@...r.kernel.org
Subject: CPU too old panic on Centrino proc - 2.6.22.6

Please CC any replies; not subscribed to list

I found this thread: http://lkml.org/lkml/2007/5/16/499
but it doesn't seem to apply here (bear in mind that I'm probably
not qualified to determine that though :))

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?

(Please CC me on replies)

Thanks,
-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/