nosmp/maxcpus=0 or 1 -> TSC unstable
From: dean gaudet
Date: Sat Jan 12 2008 - 14:48:44 EST
if i boot an x86 64-bit 2.6.24-rc7 kernel with nosmp, maxcpus=0 or 1 it
still disables TSC :)
Marking TSC unstable due to TSCs unsynchronized
this is an opteron 2xx box which does have two cpus and no clock-divide in
halt or cpufreq enabled so TSC should be fine with only one cpu.
pretty sure this is the culprit is that num_possible_cpus() > 1, which
would mean cpu_possible_map contains the second cpu... but i'm not quite
sure what the right fix is... or perhaps this is all intended.
-dean
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/