* Loading hardware drivers...piix4_smbus 0000:00:07.3: Host SMBus controller not enabled!clocksource=acpi_pm kernel option: Boot options file=/cdrom/preseed/ubuntu-server.seed initrd=/install/initrd.gz quiet --clocksource=acpi_pm kernel option as follows:Boot options file=/cdrom/preseed/ubuntu-server.seed initrd=/install/initrd.gz quiet clocksource=acpi_pm --clocksource=acpi_pm kernel option: Ubuntu 8.0.4 LTS (7.10) kernel 2.6.22-14-server and press E to start editing.kernel /boot/vmlinuz-2.6.22-14-server root=UUID=...... ro quiet splash line.clocksource=acpi_pm parameter to the end of the line.kernel /boot/vmlinuz-2.6.22-14-server root=UUID=...... ro quiet splash clocksource=acpi_pmtitle Ubuntu 8.04 LTS(7.10), kernel 2.6.22-14-serverroot (hd0,0)kernel /boot/vmlinuz-2.6.22-14-server root=UUID=...... ro quiet splashinitrd /boot/initrd.img-2.6.22-14-serverquietclocksource=acpi_pm kernel option to the end of the following line:kernel /boot/vmlinuz-2.6.22-14 -server root=UUID=...... ro quiet splashStarting with Linux Kernel 2.6.18, the CPU's Time Stamp Counter (TSC) is used to keep time. When booting, sometimes the kernel mis-detects the frequency of this counter. This may result in severe clock drift, which is impossible for ntpd to correct. On some systems it may work well enough to run ntpd, but ntpd gets a slightly different calibration each time on reboot. This may cause a start-up transient when rebooting because the drift file (purpose of the file is to track clock's error rate and automatically adjust ntp overtime) will be off. The transient may vary from few milliseconds to hours at times; however, this is still far too inaccurate for NTP to correct.
The correct solution is to use the old acpi_pm clock, which is used in earlier kernels. For more information, see Kernel 2.6 Mis-Detecting CPU TSC Frequency.
Concerning other available clocksource parameters in the Linux kernel, reference them at the linux.org's website in the Kernel Parameters Document and look for the keyword clocksource.