Time drift issues

[venix1]

This appears to be a known and long running issue. 

https://github.com/torvalds/linux/commit...ff7e1d975c

You can check the Soc with this script by Andre Przywara. For me, 2 of the 7 modules have issues, and the script shows 2 of the 7 have time skew issues.

Will time jump within a couple of days.

Code:

pine64so-cluster2 | CHANGED | rc=0 >>
TAP version 13
# number of cores: 4
ok 1 same timer frequency on all cores
# timer frequency is 24000000 Hz (24 MHz)
# time1: 93dc77ff9, time2: 93dc741ff, diff: -15866
# time1: 93de37dff, time2: 93de37c06, diff: -505
# time1: 93de8dff8, time2: 93de8de00, diff: -504
# time1: 93dee1ff9, time2: 93dee1e00, diff: -505
# time1: 93dfd1ff9, time2: 93dfd1e00, diff: -505
# time1: 93e061ff9, time2: 93e061e00, diff: -505
# time1: 93e09aff9, time2: 93e09ae00, diff: -505
# time1: 93e0fd3f9, time2: 93e0fd200, diff: -505
# time1: 93e116bf9, time2: 93e116a00, diff: -505
# time1: 93e145ff9, time2: 93e145e00, diff: -505
# time1: 93e157ff9, time2: 93e1541ff, diff: -15866
# time1: 93e1f6ff9, time2: 93e1f6e00, diff: -505
# time1: 93e283ff9, time2: 93e2801ff, diff: -15866
# time1: 93e32bff9, time2: 93e3281ff, diff: -15866
# time1: 93e3c1ff9, time2: 93e3c1e00, diff: -505
# time1: 93e3d3ff9, time2: 93e3d01ff, diff: -15866
# too many errors, stopping reports
not ok 2 native counter reads are monotonic # 166 errors
# min: -15866, avg: 6, max: 6307335
# diffs: -660791, -20792, -20750, -660833, -20792, -20750, -20750, -660833, -20792, -20792, -20792, -20792, -20792, -20750, -660833, -20792
# too many errors, stopping reports
not ok 3 Linux counter reads are monotonic # 661 errors
# min: -88042125, avg: 533, max: 661917
# core 0: counter value: 40082686052 => 1670 sec
# core 0: offsets: back-to-back: 8, b-t-b synced: 11, b-t-b w/ delay: 8
# core 1: counter value: 40082687216 => 1670 sec
# core 1: offsets: back-to-back: 10, b-t-b synced: 6, b-t-b w/ delay: 13
# core 2: counter value: 40082688217 => 1670 sec
# core 2: offsets: back-to-back: 8, b-t-b synced: 6, b-t-b w/ delay: 8
# core 3: counter value: 40082689151 => 1670 sec
# core 3: offsets: back-to-back: 8, b-t-b synced: 6, b-t-b w/ delay: 8
1..3

pine64so-cluster3 has never experienced this jump.

Code:

pine64so-cluster3 | CHANGED | rc=0 >>
TAP version 13
# number of cores: 4
ok 1 same timer frequency on all cores
# timer frequency is 24000000 Hz (24 MHz)
ok 2 native counter reads are monotonic # 0 errors
# min: 7, avg: 7, max: 4541
ok 3 Linux counter reads are monotonic # 0 errors
# min: 541, avg: 550, max: 213417
# core 0: counter value: 40118769909 => 1671 sec
# core 0: offsets: back-to-back: 10, b-t-b synced: 13, b-t-b w/ delay: 11
# core 1: counter value: 40118770884 => 1671 sec
# core 1: offsets: back-to-back: 10, b-t-b synced: 9, b-t-b w/ delay: 10
# core 2: counter value: 40118772200 => 1671 sec
# core 2: offsets: back-to-back: 13, b-t-b synced: 8, b-t-b w/ delay: 10
# core 3: counter value: 40118773120 => 1671 sec
# core 3: offsets: back-to-back: 9, b-t-b synced: 8, b-t-b w/ delay: 11
1..3

I haven't been able to find activity related to this since the patch went mainline other than additional reports the issue still isn't resolved.