Bug ID 1220119
Summary Some tests on o3 triggers dmesg "clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large:"
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Kernel
Assignee kernel-bugs@opensuse.org
Reporter petr.vorel@suse.com
QA Contact qa-bugs@suse.de
CC jwiesner@suse.com
Target Milestone ---
Found By ---
Blocker ---

Some tests running on o3 (openQA instance on https://openqa.opensuse.org/)
triggers in dmesg. All tests run in VM via qemu.

This is on x86_64 on my private openQA worker by ltp_net_tcp_cmds, triggered
for 2 tests: arp and host (both tests did not fail):

OpenQA::run_ltp.pm: Starting ipneigh01_arp
[  410.818828][    C0] clocksource: timekeeping watchdog on CPU0: Marking
clocksource 'tsc' as unstable because the skew is too large:
[  410.820365][    C0] clocksource:                       'kvm-clock' wd_nsec:
506724586 wd_now: 610448443a wd_last: 60e6144350 mask: ffffffffffffffff
[  410.821824][    C0] clocksource:                       'tsc' cs_nsec:
49302930542 cs_now: 17c1364ba0a cs_last: 153fdc32526 mask: ffffffffffffffff
[  410.823293][    C0] clocksource:                       Clocksource 'tsc'
skewed 48796205956 ns (48796 ms) over watchdog 'kvm-clock' interval of
506724586 ns (506 ms)
[  410.824843][    C0] clocksource:                       'kvm-clock' (not
'tsc') is current clocksource.
[  410.825707][    C0] tsc: Marking TSC unstable due to clocksource watchdog
[  411.109710][T28135] Initializing XFRM netlink socket
OpenQA::run_ltp.pm: Starting ipneigh01_ip
OpenQA::run_ltp.pm: Starting arping01
OpenQA::run_ltp.pm: Starting clockdiff01
OpenQA::run_ltp.pm: Starting ftp
OpenQA::run_ltp.pm: Starting host
[  410.818845][    C0] clocksource: timekeeping watchdog on CPU0: Marking
clocksource 'tsc' as unstable because the skew is too large:
[  410.820687][    C0] clocksource:                       'kvm-clock' wd_nsec:
506741379 wd_now: 61044885d3 wd_last: 60e6144350 mask: ffffffffffffffff
[  410.821794][    C0] clocksource:                       'tsc' cs_nsec:
804834172 cs_now: 154a546a082 cs_last: 153fdc32526 mask: ffffffffffffffff
[  410.822919][    C0] clocksource:                       Clocksource 'tsc'
skewed 298092793 ns (298 ms) over watchdog 'kvm-clock' interval of 506741379 ns
(506 ms)
[  410.824088][    C0] clocksource:                       'kvm-clock' (not
'tsc') is current clocksource.
[  410.824768][    C0] tsc: Marking TSC unstable due to clocksource watchdog
[  411.126759][T28138] Initializing XFRM netlink socket

Also, originally I noted this on ltp_net_tcp_cmds running on ppc64le on o3
(kernel tests in https://openqa.opensuse.org/group_overview/32), where host
test keeps failing (but arp test is working), I don't see it on
ltp_net_tcp_cmds on x86_64 on o3.

I was not able to trigger this on VM on my laptop (x86_64).

Others found that systemd-networkd test on Tumbleweed on x86_64
(https://openqa.opensuse.org/group_overview/1):

[  570.754611][    C0] Showing busy workqueues and worker pools:
[  570.755654][    C0] workqueue events: flags=0x0
[  570.756580][    C0]   pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256
refcnt=2
[  570.756586][    C0]     pending: drm_fb_helper_damage_work
[  570.759551][    C0] sysrq: Show Blocked State
zDBFr-0-
[  311.682306][    C0] clocksource: timekeeping watchdog on CPU0: Marking
clocksource 'tsc' as unstable because the skew is too large:
[  311.684482][    C0] clocksource:                       'kvm-clock' wd_nsec:
621509306 wd_now: 49d9caac63 wd_last: 49b4bf31a9 mask: ffffffffffffffff
[  311.686513][    C0] clocksource:                       'tsc' cs_nsec:
952336665 cs_now: a3a422af12 cs_last: a327415f8e mask: ffffffffffffffff
[  311.688559][    C0] clocksource:                       Clocksource 'tsc'
skewed 330827359 ns (330 ms) over watchdog 'kvm-clock' interval of 621509306 ns
(621 ms)
[  311.690452][    C0] clocksource:                       'kvm-clock' (not
'tsc') is current clocksource.
[  311.691559][    C0] tsc: Marking TSC unstable due to clocksource watchdog

Test runs also on aarch64, but error is not there.

Is it a problem of openQA setup? There are other bugs.


You are receiving this mail because: