From: Joerg Vehlow <lkml@jv-coder.de>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Miroslav Lichvar <mlichvar@redhat.com>,
linux-stable <stable@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
John Stultz <john.stultz@linaro.org>,
lkft-triage@lists.linaro.org
Subject: Re: [4.14] Failing selftest timer/adjtick
Date: Thu, 11 Feb 2021 11:34:58 +0100 [thread overview]
Message-ID: <4fa3c57d-23ea-2f8c-72fe-d23f3146f571@jv-coder.de> (raw)
In-Reply-To: <CA+G9fYuQL9=gJJtWp7wHRzY1dc4q-Be4XjrZJUmYTJUbDEN=dA@mail.gmail.com>
Hi,
On 2/10/2021 7:59 PM, Naresh Kamboju wrote:
> I have tested adjtick on arm64 juno-r2 device and it got pass
> and here is the test output on Linux version 4.14.221-rc1.
Interesting. Is this vanilla 4.14.221 or are there some o-e patches applied?
I just tried again on qemu arm with 4.14.222 from kernel.org stable tree
and still have failures like the one below every time I try. The failing
test step differs, but it always fails.
Each iteration takes about 15 seconds
Estimating tick (act: 9000 usec, -100000 ppm): 9000 usec, -100000 ppm
[OK]
Estimating tick (act: 9250 usec, -75000 ppm): 9250 usec, -75001 ppm [OK]
Estimating tick (act: 9500 usec, -50000 ppm): 9501 usec, -49995 ppm [OK]
Estimating tick (act: 9750 usec, -25000 ppm): 9750 usec, -25003 ppm [OK]
Estimating tick (act: 10000 usec, 0 ppm): 9996 usec, -463 ppm [FAILED]
Bail out!
Pass 0 Fail 0 Xfail 0 Xpass 0 Skip 0 Error 0
1..0
Joerg
next prev parent reply other threads:[~2021-02-11 10:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 12:43 [4.14] Failing selftest timer/adjtick Joerg Vehlow
2021-02-10 13:00 ` Greg KH
2021-02-10 13:07 ` Joerg Vehlow
2021-02-10 13:19 ` Miroslav Lichvar
2021-02-10 18:59 ` Naresh Kamboju
2021-02-11 10:34 ` Joerg Vehlow [this message]
2021-02-11 10:33 ` Joerg Vehlow
2021-02-11 10:45 ` Greg KH
2021-02-11 10:59 ` Miroslav Lichvar
2021-02-18 7:05 ` Joerg Vehlow
2021-03-01 7:04 ` Joerg Vehlow
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=4fa3c57d-23ea-2f8c-72fe-d23f3146f571@jv-coder.de \
--to=lkml@jv-coder.de \
--cc=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mingo@kernel.org \
--cc=mlichvar@redhat.com \
--cc=naresh.kamboju@linaro.org \
--cc=stable@vger.kernel.org \
/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 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).