linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Viro <viro@math.psu.edu>
To: Paul Faure <paul@engsoc.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.0.35 limits
Date: Fri, 15 Jun 2001 17:35:49 -0400 (EDT)	[thread overview]
Message-ID: <Pine.GSO.4.21.0106151726050.9091-100000@weyl.math.psu.edu> (raw)
In-Reply-To: <Pine.LNX.4.33.0106151702300.22155-100000@stout.engsoc.carleton.ca>



On Fri, 15 Jun 2001, Paul Faure wrote:

> Just this morning, our firewall get a kernel panic after 500 days of
> uptime.
> 
> As you can see from the log files, the date starts at June 15th, where we
> get two div by zeros, then jumps May 11th, then a kernel panic. A reboot
> brings it back to June 15th. Since cron could not open /dev/rtc. My first
> thought was an internal kernel limit on the time, but 500 days seems a bit
> short.
> 
> Any ideas ?

(1<<32) / (24 * 60 * 60 * 100) == 497

IOW, 2^32 timer interrupts since the boot.


  parent reply	other threads:[~2001-06-15 21:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-15 19:54 drivers/usb/ov511.c does not compile Kelledin Tane
2001-06-15 20:05 ` Johannes Erdfelt
2001-06-15 20:34   ` Alan Cox
2001-06-15 20:52     ` Johannes Erdfelt
2001-06-15 21:23       ` Kernel 2.0.35 limits Paul Faure
2001-06-15 21:27         ` Alan Cox
2001-06-16  5:27           ` Paul Faure
2001-06-16 12:11           ` Thomas Bogendoerfer
2001-06-15 21:35         ` Alexander Viro [this message]
2001-06-15 20:11 ` drivers/usb/ov511.c does not compile Kelledin Tane

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=Pine.GSO.4.21.0106151726050.9091-100000@weyl.math.psu.edu \
    --to=viro@math.psu.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@engsoc.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;
as well as URLs for NNTP newsgroup(s).