• Peter Zijlstra's avatar
    sched/clock: Print a warning recommending 'tsc=unstable' · 7708d5f0
    Peter Zijlstra authored
    With our switch to stable delayed until late_initcall(), the most
    likely cause of hitting mark_tsc_unstable() is the watchdog. The
    watchdog typically only triggers when creative BIOS'es fiddle with the
    TSC to hide SMI latency.
    
    Since the watchdog can only detect TSC fiddling after the fact all TSC
    clocks (including userspace GTOD) can already have reported funny
    values.
    
    The only way to fully avoid this, is manually marking the TSC unstable
    at boot. Suggest people do this on their broken systems.
    Signed-off-by: default avatarPeter Zijlstra (Intel) <peterz@infradead.org>
    Cc: Linus Torvalds <torvalds@linux-foundation.org>
    Cc: Mike Galbraith <efault@gmx.de>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: linux-kernel@vger.kernel.org
    Signed-off-by: default avatarIngo Molnar <mingo@kernel.org>
    7708d5f0
clock.c 11.4 KB