From: J Sloan <joe@tmsusa.com>
To: Tim Schmielau <tim@physik3.uni-rostock.de>
Cc: Oliver Hillmann <oh@novaville.de>, linux-kernel@vger.kernel.org
Subject: Re: jiffies rollover, uptime etc.
Date: Mon, 18 Feb 2002 15:22:01 -0800 [thread overview]
Message-ID: <3C718C99.9030909@tmsusa.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0202182305390.10354-100000@gans.physik3.uni-rostock.de>
Many will be grateful if this finally allows
the correct uptime to be generated after
497 days - my busy mail/dns servers now
have 611 days uptime, but to outsiders it
appears they only have 114 days uptime,
and there are bizarre items in the process
table, e.g. programs that were apparently
started in the year 2003...
Joe
Tim Schmielau wrote:
>On Mon, 18 Feb 2002, Oliver Hillmann wrote:
>
>>Hello,
>>
>>yes, I know this is defenitely no new issue (maybe its none to you
>>anyway), since I found posts about this dating from 1998: the
>>jiffies counter rolls over after approx. 497 days uptime, which
>>causes the uptime to roll over as well, and seems to cause some
>>other irretation in the system itself (my pc speaker starting
>>beeping constantely...)
>>
>
>See
>http://www.lib.uaa.alaska.edu/linux-kernel/archive/2001-Week-47/0736.html
>for a patch.
>I intend to submit this for 2.4.19pre after some more testing and
>feedback.
>
>Also note that several patches for jiffies rollover bugs have gone into
>2.4.18pre, maybe one of them fixes the speaker driver.
>
>Tim
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2002-02-18 23:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-18 21:42 jiffies rollover, uptime etc Oliver Hillmann
2002-02-18 22:10 ` Alan Cox
2002-02-18 22:03 ` Oliver Hillmann
2002-02-18 22:19 ` Ben Greear
2002-02-18 22:32 ` Tim Schmielau
2002-02-18 22:43 ` Alan Cox
2002-02-18 23:26 ` bert hubert
2002-02-18 23:56 ` J Sloan
2002-02-18 23:57 ` Alan Cox
2002-02-19 0:58 ` Stephen Frost
2002-02-19 4:47 ` Paul Jakma
2002-02-19 0:17 ` Bill Davidsen
2002-02-19 20:55 ` george anzinger
2002-02-20 11:36 ` Ville Herva
2002-02-20 17:20 ` Mike Fedyk
2002-02-20 17:24 ` Rik van Riel
2002-02-20 17:32 ` Mike Fedyk
2002-02-20 17:39 ` Rik van Riel
2002-02-20 17:44 ` Mike Fedyk
2002-02-20 17:56 ` Derek Gladding
2002-02-21 13:19 ` Bill Davidsen
2002-02-20 19:08 ` David Mosberger
2002-02-20 19:53 ` Robert Love
2002-02-20 15:46 ` Bill Davidsen
2002-02-20 16:50 ` george anzinger
2002-02-18 22:12 ` Tim Schmielau
2002-02-18 23:22 ` J Sloan [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-19 2:54 Chris Adams
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=3C718C99.9030909@tmsusa.com \
--to=joe@tmsusa.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oh@novaville.de \
--cc=tim@physik3.uni-rostock.de \
/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