Comment # 3 on bug 1220119 from Petr Vorel

(In reply to Jiri Wiesner from comment #2)
...
> I'd be interested to see the kernel log from that test. While logged in, I
> can see a failed ltp_net_tcp_cmds/host test but I don't know how to display
> the kernel log.

https://openqa.opensuse.org/tests/3947323/file/serial0.txt
This is on most machines: Logs & Assets tab => serial0.txt.
I'll attach it. Also test sporadically fails on aarch64 on o3 (attach dmesg as
well), but there is nothing strange with clocksource. IMHO the test failure is
unrelated to the clocksource problem. 

Also, dmesg before reboot (on some machines serial0.txt contains just firmware
before log):
https://openqa.opensuse.org/tests/3947323/logfile?filename=shutdown_ltp-dmesg.txt

> 
> > Others found that systemd-networkd test on Tumbleweed on x86_64
> > (https://openqa.opensuse.org/group_overview/1):
> > [  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
> 
> The interval, as reported by kvm-clock, is much longer than 500 milliseconds
> indicating a delayed expiration of the timer, which could be a consequence
> of the system being under high load.
> 
> > Is it a problem of openQA setup? There are other bugs.
> 
> There is almost certainly something wrong with the tsc clocksource (not
> kvm-clock). Perhaps, the TSC counter is somehow virtualized (or
> para-virtualized by Qemu, I don't know) and the virtualized TSC misbehaves
> under certain conditions.

Interesting.