http://bugzilla.opensuse.org/show_bug.cgi?id=1172978
http://bugzilla.opensuse.org/show_bug.cgi?id=1172978#c3
--- Comment #3 from Michael Ströder ---
It happens sometimes after suspend of my laptop. System time is wrong,
currently in my test VM in the future.
strace -p <pid> -f shows repeately only:
select(8, [5 6 7], NULL, NULL, {tv_sec=0, tv_usec=0}) = 0 (Timeout)
ltrace loops over:
[pid 782] clock_gettime(0, 0x7ffe465a68d0, 0, 0x7fca3ee4e3a3)
= 0
[pid 782] clock_gettime(0, 0x7ffe465a68d0, 0x5ee9edf6, 0x5ee9edf6)
= 0
[pid 782] __fdelt_chk(5, 0, 0x55715675bed0, 0)
= 0
[pid 782] __fdelt_chk(6, 32, 0x55715675bed0, 5)
= 0
[pid 782] __fdelt_chk(7, 64, 0x55715675bed0, 6)
= 0
[pid 782] select(8, 0x7ffe465a69f0, 0, 0)
= 0
[pid 782] __errno_location()
= 0x7fca3ed4c6c0
systemctl start chronyd results in this process list:
root 11326 0.0 4.7 19412 7844 pts/0 S+ 11:50 0:00 systemctl
start chronyd
root 11328 0.0 0.7 3908 1152 ? Ss 11:50 0:00
/usr/sbin/chronyd
root 11329 0.0 0.0 0 0 ? Zs 11:50 0:00 [chronyd]
<defunct>
root 11330 99.8 1.1 4120 1956 ? R 11:50 0:08
/usr/sbin/chronyd
root 11332 0.0 0.3 6088 612 pts/2 S+ 11:50 0:00 grep
--color=auto chrony
--
You are receiving this mail because:
You are on the CC list for the bug.
