From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Roger Leigh <rleigh@whinlatter.ukfsn.org>
Cc: Linux Kernel ML <linux-kernel@vger.kernel.org>,
debian-powerpc@lists.debian.org
Subject: Re: 2.6.16-rc2 powerpc timestamp skew
Date: Tue, 14 Feb 2006 09:34:24 +1100 [thread overview]
Message-ID: <1139870065.5237.26.camel@localhost.localdomain> (raw)
In-Reply-To: <87irrj85vp.fsf@hardknott.home.whinlatter.ukfsn.org>
> > Can you strace vs. ltrace and see if the gettimeofday or clock_gettime
> > syscalls are ever called ?
>
> | strace | ltrace
> -----------+---------------+------------------------------------
> 2.6.15 | |
> date | clock_gettime | clock_gettime -> SYS_clock_gettime,
> | | localtime, strftime
> touch | utimes | futimes -> SYS_utimes
> | |
> 2.6.16-rc2 | |
> date | clock_gettime | clock_gettime -> SYS_clock_gettime,
> | | localtime, strftime
> touch | utimes | futimes -> SYS_utimes
>
> [clock_gettime(CLOCK_REALTIME, {1139826613, 157402000}) = 0]
>
> > I wonder if you have a glibc new enough to
> > use the vDSO to obtain the time or if it's using the syscall... The vDSO
> > on ppc32 is very new.
>
> It's glibc 2.3.5 (Debian libc6 2.3.5-13).
Ok, does not using NTP fixes it ?
Ben.
next prev parent reply other threads:[~2006-02-13 22:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-12 17:13 2.6.16-rc2 powerpc timestamp skew Roger Leigh
2006-02-12 17:39 ` Gabriel Paubert
2006-02-12 17:58 ` Roger Leigh
2006-02-12 20:15 ` Bin Zhang
2006-02-12 19:55 ` Olaf Hering
2006-02-13 10:57 ` Olaf Hering
2006-02-13 12:51 ` Olaf Hering
2006-02-12 21:33 ` Benjamin Herrenschmidt
2006-02-13 18:34 ` Roger Leigh
2006-02-13 22:34 ` Benjamin Herrenschmidt [this message]
2006-02-15 5:27 ` Paul Mackerras
2006-02-15 10:30 ` Olaf Hering
2006-02-15 11:53 ` Mikael Pettersson
2006-02-16 11:30 ` Roger Leigh
2006-02-13 0:13 ` Andrew Morton
2006-02-13 0:41 ` Roger Leigh
2006-02-13 4:00 ` [PATCH] powerpc: dont allow old RTC to be selected Anton Blanchard
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=1139870065.5237.26.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=debian-powerpc@lists.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rleigh@whinlatter.ukfsn.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