On Thu, 8 May 2008, Martin Knoblauch wrote:
quoted text
> on two different systems running 2.6.25.2:
> 
> ibm x3650(2xDualCore)
> -------------------------------------
> [root@lpsdm60 ~]# cat /sys/devices/system/clocksource/clocksource0/available_clocksource
> tsc hpet acpi_pm jiffies
> [root@lpsdm60 ~]# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
> tsc
> 
> HP Proliant DL-380G4 (2xSingleCore)
> ------------------------------------------------------------
> [root@lpsdm52 ~]# cat /sys/devices/system/clocksource/clocksource0/available_clocksource
> tsc hpet acpi_pm jiffies
> [root@lpsdm52 ~]# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
> tsc
> 
> and on the DL380G4 running 2.6.24:
> ---------------------------------------------------------
> [root@lpsdm52 ~]# cat /sys/devices/system/clocksource/clocksource0/available_clocksource
> hpet acpi_pm jiffies tsc
> [root@lpsdm52 ~]# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
> hpet

So on 2.6.24 the TSC is declared unstable at some point and 2.6.25
thinks it works fine. Is this the same kernel config (aside of the 24/25 fuzz) ?

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