timekeeping: Cycle offset (32) is larger than allowed by the 'jiffies' clock's max_cycles value (10): time overflow danger
When enabling CONFIG_DEBUG_TIMEKEEPING, I see on kernel 4.8 git head those warnings on the parisc architecture: Linux version 4.8.0-64bit+ (del...@p100.box) (gcc version 4.9.2 20150212 (Red Hat Cross 4.9.2-5) (GCC) ) #516 SMP Wed Oct 12 22:52:58 CEST 2016 ... clocksource: cr16: mask: 0x max_cycles: 0xacf9151134, max_idle_ns: 440795214493 ns WARNING: timekeeping: Cycle offset (32) is larger than allowed by the 'jiffies' clock's max_cycles value (10): time overflow danger timekeeping: Your kernel is sick, but tries to cope by capping time updates WARNING: timekeeping: Cycle offset (42) is larger than allowed by the 'jiffies' clock's max_cycles value (10): time overflow danger timekeeping: Your kernel is sick, but tries to cope by capping time updates ... At this stage the jiffies clocksource was not yet registered (at least not mentioned in the bootlog). This warning happens over and over. Maybe it should be rate-limited too? Comparing to 4.7 where CONFIG_DEBUG_TIMEKEEPING is not enabled I see: root@c8000:~# dmesg | grep clock [0.00] clocksource: cr16: mask: 0x max_cycles: 0xcf914c9718, max_idle_ns: 440795231327 ns [0.873644] clocksource: jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 764504178510 ns [7.968087] clocksource: Switched to clocksource cr16 Am I somehow missing to initialize the max_cycles field of the jiffies clocksource on the parisc architecture ? Helge
timekeeping: Cycle offset (32) is larger than allowed by the 'jiffies' clock's max_cycles value (10): time overflow danger
When enabling CONFIG_DEBUG_TIMEKEEPING, I see on kernel 4.8 git head those warnings on the parisc architecture: Linux version 4.8.0-64bit+ (del...@p100.box) (gcc version 4.9.2 20150212 (Red Hat Cross 4.9.2-5) (GCC) ) #516 SMP Wed Oct 12 22:52:58 CEST 2016 ... clocksource: cr16: mask: 0x max_cycles: 0xacf9151134, max_idle_ns: 440795214493 ns WARNING: timekeeping: Cycle offset (32) is larger than allowed by the 'jiffies' clock's max_cycles value (10): time overflow danger timekeeping: Your kernel is sick, but tries to cope by capping time updates WARNING: timekeeping: Cycle offset (42) is larger than allowed by the 'jiffies' clock's max_cycles value (10): time overflow danger timekeeping: Your kernel is sick, but tries to cope by capping time updates ... At this stage the jiffies clocksource was not yet registered (at least not mentioned in the bootlog). This warning happens over and over. Maybe it should be rate-limited too? Comparing to 4.7 where CONFIG_DEBUG_TIMEKEEPING is not enabled I see: root@c8000:~# dmesg | grep clock [0.00] clocksource: cr16: mask: 0x max_cycles: 0xcf914c9718, max_idle_ns: 440795231327 ns [0.873644] clocksource: jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 764504178510 ns [7.968087] clocksource: Switched to clocksource cr16 Am I somehow missing to initialize the max_cycles field of the jiffies clocksource on the parisc architecture ? Helge
