* Sporadic failures of rt/tst-cputimer1 on ppc64le (POWER8 hardware)?
@ 2016-04-29 19:00 Carlos O'Donell
2016-04-29 20:58 ` Tulio Magno Quites Machado Filho
0 siblings, 1 reply; 4+ messages in thread
From: Carlos O'Donell @ 2016-04-29 19:00 UTC (permalink / raw)
To: GNU C Library, Tulio Magno Quites Machado Filho, Carlos Eduardo Seo
On ppc64le I see a sporadic failure in rt/tst-cputimer1:
clock_gettime returned timespec = { 0, 405994 }
clock_getres returned timespec = { 0, 1 }
*** timer sig1 invoked too soon: 0.400715218 instead of expected 0.400761014
*** timer sig2 invoked too soon: 0.500710982 instead of expected 0.500761014
The kernel says the clock resolution is 1 nanosecond, that seems exceedingly
prcise.
The kernel invokes the signal ~46 micorseconds too early, which is not
allowed by the tests. You can invoke late, but not early.
Have either of you seen this before?
--
Cheers,
Carlos.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Sporadic failures of rt/tst-cputimer1 on ppc64le (POWER8 hardware)?
2016-04-29 19:00 Sporadic failures of rt/tst-cputimer1 on ppc64le (POWER8 hardware)? Carlos O'Donell
@ 2016-04-29 20:58 ` Tulio Magno Quites Machado Filho
2016-04-30 1:02 ` Carlos O'Donell
0 siblings, 1 reply; 4+ messages in thread
From: Tulio Magno Quites Machado Filho @ 2016-04-29 20:58 UTC (permalink / raw)
To: Carlos O'Donell, GNU C Library, Carlos Eduardo Seo
Carlos O'Donell <carlos@redhat.com> writes:
> [ text/plain ]
> On ppc64le I see a sporadic failure in rt/tst-cputimer1:
>
> clock_gettime returned timespec = { 0, 405994 }
> clock_getres returned timespec = { 0, 1 }
> *** timer sig1 invoked too soon: 0.400715218 instead of expected 0.400761014
> *** timer sig2 invoked too soon: 0.500710982 instead of expected 0.500761014
>
> The kernel says the clock resolution is 1 nanosecond, that seems exceedingly
> prcise.
I believe it has been that way since http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=597bc5c00b666fe123abb0af64f6e86f7ab72a90
>
> The kernel invokes the signal ~46 micorseconds too early, which is not
> allowed by the tests. You can invoke late, but not early.
>
> Have either of you seen this before?
I noticed this for the first time earlier today on a Linux 3.13 box, but I
still wasn't able to reproduce it on another server with a newer kernel.
I suspect it might be related to another failure on rt/tst-cputimer3 which I
can reproduce only on the same server that rt/tst-cputimer1 failed today.
Notice that I'm able to reproduce rt/tst-cputimer3 on glibc 2.23, while
rt/tst-cputimer1 failed with 2.24.
I wonder if these failures are related to this:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=6e998916dfe327e785e7c2447959b2c1a3ea4930
Where did you reproduce it?
--
Tulio Magno
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Sporadic failures of rt/tst-cputimer1 on ppc64le (POWER8 hardware)?
2016-04-29 20:58 ` Tulio Magno Quites Machado Filho
@ 2016-04-30 1:02 ` Carlos O'Donell
2016-07-19 13:20 ` Tulio Magno Quites Machado Filho
0 siblings, 1 reply; 4+ messages in thread
From: Carlos O'Donell @ 2016-04-30 1:02 UTC (permalink / raw)
To: Tulio Magno Quites Machado Filho, GNU C Library, Carlos Eduardo Seo
On 04/29/2016 04:58 PM, Tulio Magno Quites Machado Filho wrote:
> Where did you reproduce it?
On a RHEL7 kernel (Linux Kernel 3.10.0-229.ael7b.ppc64le) which
has a lot of backports. It was a POWER8 box with 32 cores.
--
Cheers,
Carlos.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Sporadic failures of rt/tst-cputimer1 on ppc64le (POWER8 hardware)?
2016-04-30 1:02 ` Carlos O'Donell
@ 2016-07-19 13:20 ` Tulio Magno Quites Machado Filho
0 siblings, 0 replies; 4+ messages in thread
From: Tulio Magno Quites Machado Filho @ 2016-07-19 13:20 UTC (permalink / raw)
To: Carlos O'Donell, GNU C Library, Carlos Eduardo Seo
Carlos O'Donell <carlos@redhat.com> writes:
> [ text/plain ]
> On 04/29/2016 04:58 PM, Tulio Magno Quites Machado Filho wrote:
>> Where did you reproduce it?
>
> On a RHEL7 kernel (Linux Kernel 3.10.0-229.ael7b.ppc64le) which
> has a lot of backports. It was a POWER8 box with 32 cores.
I have just received a confirmation that Linux commit 6e998916dfe3 does
indeed solve this issue and it depends on commit 23cfa361f3e5.
--
Tulio Magno
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-07-19 13:17 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-04-29 19:00 Sporadic failures of rt/tst-cputimer1 on ppc64le (POWER8 hardware)? Carlos O'Donell
2016-04-29 20:58 ` Tulio Magno Quites Machado Filho
2016-04-30 1:02 ` Carlos O'Donell
2016-07-19 13:20 ` Tulio Magno Quites Machado Filho
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 read-only IMAP folder(s) and NNTP newsgroup(s).