LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jeffrin Thalakkottoor <jeffrin@rajagiritech.edu.in>
To: John Stultz <john.stultz@linaro.org>
Cc: Shuah Khan <shuah@kernel.org>, Kees Cook <keescook@chromium.org>,
	Anton Vorontsov <anton@enomsg.org>,
	Colin Cross <ccross@android.com>, Tony Luck <tony.luck@intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	sboyd@kernel.org, linux-kselftest@vger.kernel.org,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: possible BUG: selftest about raw_skew failed
Date: Fri, 27 Apr 2018 20:57:53 +0530	[thread overview]
Message-ID: <CAG=yYwmaVT5cEoi9s=YDs-OHNd6z6UScY+Ebos=cJ24ONG3U0Q@mail.gmail.com> (raw)
In-Reply-To: <CALAqxLWphJvPe=v2T2ksjHnQP1Vu7+gZernEgFVXcx5kB+efsQ@mail.gmail.com>

I kind of ignored. i was not sure what that meant actually.

On Fri, Apr 27, 2018 at 3:03 AM, John Stultz <john.stultz@linaro.org> wrote:
> On Sat, Apr 21, 2018 at 7:47 AM, Jeffrin Thalakkottoor
> <jeffrin@rajagiritech.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



-- 
software engineer
rajagiri school of engineering and technology

      reply	other threads:[~2018-04-27 15:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-21 14:47 Jeffrin Thalakkottoor
2018-04-26 21:28 ` Thomas Gleixner
2018-04-27  7:41   ` Miroslav Lichvar
2018-04-27 15:28     ` Jeffrin Thalakkottoor
2018-04-26 21:33 ` John Stultz
2018-04-27 15:27   ` Jeffrin Thalakkottoor [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAG=yYwmaVT5cEoi9s=YDs-OHNd6z6UScY+Ebos=cJ24ONG3U0Q@mail.gmail.com' \
    --to=jeffrin@rajagiritech.edu.in \
    --cc=anton@enomsg.org \
    --cc=ccross@android.com \
    --cc=john.stultz@linaro.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=sboyd@kernel.org \
    --cc=shuah@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --subject='Re: possible BUG: selftest about raw_skew failed' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).