[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALAqxLWphJvPe=v2T2ksjHnQP1Vu7+gZernEgFVXcx5kB+efsQ@mail.gmail.com>
Date: Thu, 26 Apr 2018 14:33:11 -0700
From: John Stultz <john.stultz@...aro.org>
To: Jeffrin Thalakkottoor <jeffrin@...agiritech.edu.in>
Cc: Shuah Khan <shuah@...nel.org>, Kees Cook <keescook@...omium.org>,
Anton Vorontsov <anton@...msg.org>,
Colin Cross <ccross@...roid.com>,
Tony Luck <tony.luck@...el.com>,
Thomas Gleixner <tglx@...utronix.de>, sboyd@...nel.org,
linux-kselftest@...r.kernel.org,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: possible BUG: selftest about raw_skew failed
On Sat, Apr 21, 2018 at 7:47 AM, Jeffrin Thalakkottoor
<jeffrin@...agiritech.edu.in> 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) [FAILED]
So you're ignoring the warning above. If an ADJ_OFFSET operation is
going on, ntpd (or something similar) is changing the clock, which
will kill the estimated drift calculation.
-john
Powered by blists - more mailing lists