* tst-nanosleep, tst-clock_nanosleep Failures
@ 2003-06-13 19:15 Steve Munroe
2003-06-13 19:47 ` Andreas Jaeger
0 siblings, 1 reply; 2+ messages in thread
From: Steve Munroe @ 2003-06-13 19:15 UTC (permalink / raw)
To: libc-hacker, libc-alpha
Is anyone else seeing make check failures in tst-nanosleep and
tst-clock_nanosleep?
I see these fail at various times (7.5%+ failure rate) on PPC64 (both 2.4
and 2.5) kernels running either PPC32 or PPC64 applications. These are all
SMP machines. In each case the measured time averages 0.5 jiffies less
than 1 second!
The nanosleep code is in the kernel is arch independent so I would expect
this test to fail on the SMP platforms?
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: tst-nanosleep, tst-clock_nanosleep Failures
2003-06-13 19:15 tst-nanosleep, tst-clock_nanosleep Failures Steve Munroe
@ 2003-06-13 19:47 ` Andreas Jaeger
0 siblings, 0 replies; 2+ messages in thread
From: Andreas Jaeger @ 2003-06-13 19:47 UTC (permalink / raw)
To: Steve Munroe; +Cc: libc-hacker, libc-alpha
Steve Munroe <sjmunroe@us.ibm.com> writes:
> Is anyone else seeing make check failures in tst-nanosleep and
> tst-clock_nanosleep?
>
> I see these fail at various times (7.5%+ failure rate) on PPC64 (both 2.4
> and 2.5) kernels running either PPC32 or PPC64 applications. These are all
> SMP machines. In each case the measured time averages 0.5 jiffies less
> than 1 second!
>
> The nanosleep code is in the kernel is arch independent so I would expect
> this test to fail on the SMP platforms?
Perhaps your clock is going wrong? The time keeping code is
architecture dependend...
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2003-06-13 19:47 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-06-13 19:15 tst-nanosleep, tst-clock_nanosleep Failures Steve Munroe
2003-06-13 19:47 ` Andreas Jaeger
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).