From: mlichvar at redhat.com (Miroslav Lichvar)
Subject: possible BUG: selftest about raw_skew failed
Date: Fri, 27 Apr 2018 09:41:30 +0200 [thread overview]
Message-ID: <20180427074130.GN20050@localhost> (raw)
In-Reply-To: <alpine.DEB.2.21.1804262327480.1596@nanos.tec.linutronix.de>
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) 16.820(act) [FAILED]
Was ntpd, systemd-timesyncd, or some other NTP/PTP daemon running
shortly before or during the test?
The warning indicates that the clock was slewed by adjtime() or
adjtimex(), which makes the measurement of the frequency less accurate
and the test may fail.
Maybe this test and other tests that measure the frequency of the
system clock should be modified to SKIP when adjtimex() returns a
non-zero offset (or the frequency changes during the test)?
--
Miroslav Lichvar
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: mlichvar@redhat.com (Miroslav Lichvar)
Subject: possible BUG: selftest about raw_skew failed
Date: Fri, 27 Apr 2018 09:41:30 +0200 [thread overview]
Message-ID: <20180427074130.GN20050@localhost> (raw)
Message-ID: <20180427074130.3nAyvTWVG7CXgEMgRmzZ-orqWRNzsSTGKeHqO6vDmYg@z> (raw)
In-Reply-To: <alpine.DEB.2.21.1804262327480.1596@nanos.tec.linutronix.de>
On Thu, Apr 26, 2018@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) 16.820(act) [FAILED]
Was ntpd, systemd-timesyncd, or some other NTP/PTP daemon running
shortly before or during the test?
The warning indicates that the clock was slewed by adjtime() or
adjtimex(), which makes the measurement of the frequency less accurate
and the test may fail.
Maybe this test and other tests that measure the frequency of the
system clock should be modified to SKIP when adjtimex() returns a
non-zero offset (or the frequency changes during the test)?
--
Miroslav Lichvar
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Jeffrin Thalakkottoor <jeffrin@rajagiritech.edu.in>
Cc: Thomas Gleixner <tglx@linutronix.de>,
shuah@kernel.org, Kees Cook <keescook@chromium.org>,
anton@enomsg.org, ccross@android.com,
Tony Luck <tony.luck@intel.com>,
John Stultz <john.stultz@linaro.org>,
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 09:41:30 +0200 [thread overview]
Message-ID: <20180427074130.GN20050@localhost> (raw)
In-Reply-To: <alpine.DEB.2.21.1804262327480.1596@nanos.tec.linutronix.de>
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) 16.820(act) [FAILED]
Was ntpd, systemd-timesyncd, or some other NTP/PTP daemon running
shortly before or during the test?
The warning indicates that the clock was slewed by adjtime() or
adjtimex(), which makes the measurement of the frequency less accurate
and the test may fail.
Maybe this test and other tests that measure the frequency of the
system clock should be modified to SKIP when adjtimex() returns a
non-zero offset (or the frequency changes during the test)?
--
Miroslav Lichvar
next prev parent reply other threads:[~2018-04-27 7:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-21 14:47 possible BUG: selftest about raw_skew failed jeffrin
2018-04-21 14:47 ` Jeffrin Thalakkottoor
2018-04-21 14:47 ` Jeffrin Thalakkottoor
2018-04-26 21:28 ` tglx
2018-04-26 21:28 ` Thomas Gleixner
2018-04-26 21:28 ` Thomas Gleixner
2018-04-27 7:41 ` mlichvar [this message]
2018-04-27 7:41 ` Miroslav Lichvar
2018-04-27 7:41 ` Miroslav Lichvar
2018-04-27 15:28 ` jeffrin
2018-04-27 15:28 ` Jeffrin Thalakkottoor
2018-04-27 15:28 ` Jeffrin Thalakkottoor
2018-04-26 21:33 ` john.stultz
2018-04-26 21:33 ` John Stultz
2018-04-26 21:33 ` John Stultz
2018-04-27 15:27 ` jeffrin
2018-04-27 15:27 ` Jeffrin Thalakkottoor
2018-04-27 15:27 ` Jeffrin Thalakkottoor
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=20180427074130.GN20050@localhost \
--to=unknown@example.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.