From: Grant Grundler <grundler@puffin.external.hp.com>
To: Andreas Thienemann <andreas@thienemann.net>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Clock skew problems
Date: Thu, 19 Apr 2001 12:02:54 -0600 [thread overview]
Message-ID: <200104191802.MAA24940@puffin.external.hp.com> (raw)
In-Reply-To: Your message of "Thu, 19 Apr 2001 15:22:08 +0200." <Pine.LNX.4.10.10104191518560.30090-100000@gate.ixs.com>
Andreas Thienemann wrote:
> But now, when I try do compile some software I'm having problems.
>
> I'm getting the following message from make:
>
> make: *** Warning: File `libdb.a' has modification time in the future
> (2001-04-19 15:15:33 > 2001-04-19 15:15:04)
>
> And I have absolutely no Idea why this is happening.
Everytime one updates the kernel time and it gets set *back*,
make will notice the derived objects (ie libdb.a) are newer than
current time and complain.
However, I suspect the kernel isn't keeping time perfectly and updating
from the HW clock (YMMV: historically, some servers had better RTC crystals)
is causing the problem. Having a bad RTC will also look like
the kernel isn't keeping time when in fact it is.
a500# date
Thu Apr 19 11:11:02 MDT 2001
a500# hwclock
Thu Apr 19 11:11:01 2001 -1.003308 seconds
a500# uptime
11:11:36 up 21:25, 1 user, load average: 0.00, 0.04, 0.04
So not doing too badly - but it needs to be fixed.
I'm assuming the A500 has a good RTC.
I'll submit a bug for you.
grant
Grant Grundler
parisc-linux {PCI|IOMMU|SMP} hacker
+1.408.447.7253
next prev parent reply other threads:[~2001-04-19 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-19 13:22 [parisc-linux] Clock skew problems Andreas Thienemann
2001-04-19 18:02 ` Grant Grundler [this message]
2001-04-19 18:18 ` Andreas Thienemann
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=200104191802.MAA24940@puffin.external.hp.com \
--to=grundler@puffin.external.hp.com \
--cc=andreas@thienemann.net \
--cc=parisc-linux@parisc-linux.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