public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Miquel van Smoorenburg" <miquels@cistron.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: uptime reset after about 45 days
Date: Thu, 30 Oct 2003 23:34:03 +0000 (UTC)	[thread overview]
Message-ID: <bns75b$ssn$1@news.cistron.nl> (raw)
In-Reply-To: Pine.LNX.4.44.0310310005090.11473-100000@gaia.cela.pl

In article <Pine.LNX.4.44.0310310005090.11473-100000@gaia.cela.pl>,
Maciej Zenczykowski  <maze@cela.pl> wrote:
>> After about 45 days or so, my uptime was reset. My idle time is correct.
>> 
>> $ cat /proc/uptime
>> 94245.37 3686026.54
>> 
>> $ cat /proc/version Linux version 2.4.20-gentoo-r1
>> (root@dpb2.resnet.calvin.edu) (gcc version 3.2.2) #6 SMP Thu Apr 17
>> 14:11:34 EDT 2003
>
>Uptime is stored in jiffies which is 32bit on your arch, which results in 
>an overflow after 2^32 clock ticks. TTTicks were 100 HZ till recently 
>(overflow after 470 or so days) now, they're 1000 -> overflows after 45 
>days.  Doesn't wreck anything except for uptime display - known problem, 

No, that's only on 2.6, and it has been fixed in 2.6 too.
The 2.4 32 bits kernels run with HZ=100.

Sounds like the gentoo-kernel has just upped HZ to 1000 without
fixing these problems properly. That's .. disappointing.

Mike.


  reply	other threads:[~2003-10-30 23:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-30 22:19 uptime reset after about 45 days Dave Brondsema
2003-10-30 23:09 ` Maciej Zenczykowski
2003-10-30 23:34   ` Miquel van Smoorenburg [this message]
2003-10-31  0:03     ` Robert Love
2003-10-31 10:37   ` Jakob Oestergaard
2003-10-31 13:20     ` Gene Heskett
2003-10-31 14:59       ` Mike Dresser
2003-10-31 15:26     ` Tim Schmielau
2003-10-31 16:40       ` Tim Schmielau
2003-11-01  3:08         ` Robert Love
2003-11-01  8:35           ` Tim Schmielau

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='bns75b$ssn$1@news.cistron.nl' \
    --to=miquels@cistron.nl \
    --cc=linux-kernel@vger.kernel.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