From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Patrick Moor <pmoor@netpeople.ch>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: time jumps (again)
Date: 04 Aug 2003 17:37:30 +0100 [thread overview]
Message-ID: <1060015049.719.1.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <3F2E8B3B.3070003@netpeople.ch>
On Llu, 2003-08-04 at 17:35, Patrick Moor wrote:
> few years! Uptime of the machine is now 218 days, and problems began
> appearing after 215 days approximately.
Not sure why 215 days should be significant
> What happens: when doing a
> $ while true; do date; done
> I'm noticing time jumps _exactly_ at the beginning of a "new" second (or
> at the end of an "old" one). the jump is exactly 4294 (4295) seconds
> into the future. Example:
4294.. top of -1
Smells of some kind of sign propogation bug
next prev parent reply other threads:[~2003-08-04 16:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 16:35 time jumps (again) Patrick Moor
2003-08-04 16:37 ` Alan Cox [this message]
2003-08-04 21:49 ` Tim Schmielau
2003-08-04 22:38 ` george anzinger
2003-08-05 1:08 ` Andries Brouwer
2003-08-06 18:16 ` Timothy Miller
2003-08-06 18:55 ` George Anzinger
2003-08-07 0:29 ` Andries Brouwer
2003-08-05 10:32 ` Jan Niehusmann
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=1060015049.719.1.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pmoor@netpeople.ch \
/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 NNTP newsgroup(s).