From: Andreas Jaeger <aj@suse.de>
To: Steve Munroe <sjmunroe@us.ibm.com>
Cc: libc-hacker@sources.redhat.com, libc-alpha@sources.redhat.com
Subject: Re: tst-nanosleep, tst-clock_nanosleep Failures
Date: Fri, 13 Jun 2003 19:47:00 -0000 [thread overview]
Message-ID: <u8he6t4vy0.fsf@gromit.moeb> (raw)
In-Reply-To: <OF8D96D34E.CEEBD0E0-ON86256D44.00687296-86256D44.0069C7EB@us.ibm.com> (Steve Munroe's message of "Fri, 13 Jun 2003 14:15:19 -0500")
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
prev parent reply other threads:[~2003-06-13 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 19:15 Steve Munroe
2003-06-13 19:47 ` Andreas Jaeger [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=u8he6t4vy0.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=libc-alpha@sources.redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=sjmunroe@us.ibm.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 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).