Hi everyone:
Just a follow up on the fast clock issue:
"Can you double-check that 'cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq' outputs the same number as your 'cpuKHZ' setting in your config.ini file?"
There is no cpufreq directory under /sys/devices/system/cpu/cpu0; all I see is "cache" (dir), "crash_notes" (a file) and "topology" (dir). However under /sys/devices/system/clocksource/clocksource0, available_clocksource reads acpi_pm jiffies tsc pit, current_clocksource reads pit. (I put in the line clocksource=pit) in the grub boot up line.
Divider=10 in the bootup line causes the boot up process to hang and a reset has to be performed; removing it and the CentOS boots properly.
I'm currently using 2.6.18-53.1.13.el5, with boot up options are "noapic nolapic quiet clocksource=pit" (took out divider=10). CentOS clock is going at around 2 seconds per every real second.
On Wed, Mar 5, 2008 at 10:16 AM, chanms chanms@gmail.com wrote:
Hi everyone:
Just a follow up on the fast clock issue:
Divider=10 in the bootup line causes the boot up process to hang and a reset has to be performed; removing it and the CentOS boots properly.
This is a known issue:
http://bugs.centos.org/view.php?id=2189 (see note 6636 or so)
But you can use the 100Hz-kernels offered by CentOS without problems. The latest kernels are at:
http://people.centos.org/~tru/kernel-vm/
Akemi
chanms wrote:
Hi everyone:
Just a follow up on the fast clock issue:
"Can you double-check that 'cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq' outputs the same number as your 'cpuKHZ' setting in your config.ini file?"
That location only exists in newer kernels, however you still need the proper setting in the config file for the vm that has the proper max frequency. You also need to disable CPU freq changes on the host OS.
<snip>
-
Akemi Yagi -
chanms -
Johnny Hughes