i think may be systemd-timesyncd was running.
anyway currently the status is as follows...
$systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service;
enabled; vendor preset: enabled)
I kind of ignored. i was not sure what that meant actually.
On Fri, Apr 27, 2018 at 3:03 AM, John Stultz wrote:
> On Sat, Apr 21, 2018 at 7:47 AM, Jeffrin Thalakkottoor
> wrote:
>> hello,
>>
>> failure of a test in selftest:timers
>>
>> selftests: raw_skew
>>
On Thu, Apr 26, 2018 at 11:28:29PM +0200, Thomas Gleixner wrote:
> On Sat, 21 Apr 2018, Jeffrin Thalakkottoor wrote:
> > selftests: raw_skew
> >
> > WARNING: ADJ_OFFSET in progress, this will cause inaccurate results
> > Estimating clock drift: 17.910(est) 1
On Sat, Apr 21, 2018 at 7:47 AM, Jeffrin Thalakkottoor
wrote:
> hello,
>
> failure of a test in selftest:timers
>
> selftests: raw_skew
>
> WARNING: ADJ_OFFSET in progress, this will cause inaccurate results
> Estimating clock drift: 17.910(est) 16.820(act)
On Sat, 21 Apr 2018, Jeffrin Thalakkottoor wrote:
Cc'ing John and Miroslav
> hello,
>
> failure of a test in selftest:timers
>
> selftests: raw_skew
>
> WARNING: ADJ_OFFSET in progress, this will cause inaccurate results
> Estimating clock drift: 17.910(
hello,
failure of a test in selftest:timers
selftests: raw_skew
WARNING: ADJ_OFFSET in progress, this will cause inaccurate results
Estimating clock drift: 17.910(est) 16.820(act) [FAILED]
Bail out!
Pass 0 Fail 0 Xfail 0 Xpass 0 Skip 0 Error 0
1..0
not ok
6 matches
Mail list logo
