Hello,
In /var/log/syslog I noticed this;
Code:
May 9 19:50:36 slack kernel: clocksource: timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the skew is too large:
May 9 19:50:36 slack kernel: clocksource: 'hpet' wd_nsec: 499463060 wd_now: 1da4296 wd_last: 16d236c mask: ffffffff
May 9 19:50:36 slack kernel: clocksource: 'tsc' cs_nsec: 495995182 cs_now: 1d1e43f813 cs_last: 1caa294cc9 mask: ffffffffffffffff
May 9 19:50:36 slack kernel: clocksource: 'tsc' is current clocksource.
May 9 19:50:36 slack kernel: TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'.
May 9 19:50:36 slack kernel: clocksource: Checking clocksource tsc synchronization from CPU 8 to CPUs 0,6.
Then I went online surfing around and found this mentioned online;
Code:
In short, on modern systems, the TSC sucks for measuring time accurately. And that's what the message is telling you. On your system, the TSC is not a stable time source.
So is that the reality, nothing is wrong, other than TSC is not measuring time accurately, and not a stable time source?
So nothing is really broke/wrong with the BIOS?
I use grub, so I'm assuming I should put on the
GRUB_CMDLINE_LINUX_DEFAULT=tsc=unstable?
THANKS
P.S. After posting this I added to grub;
GRUB_CMDLINE_LINUX_DEFAULT=tsc=unstable
When I rebooted, I know have this in the logs;
Code:
May 9 20:19:50 slack kernel: Unstable clock detected, switching default tracing clock to "global"
May 9 20:19:50 slack kernel: If you want to keep using the local clock, then add:
May 9 20:19:50 slack kernel: "trace_clock=local"
So I'm assuming I should now also add to the GRUB_CMDLINE_LINUX_DEFAULT=
trace_clock=local?
