linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Paul Faure <paul@engsoc.org>, linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.0.35 limits
Date: Sat, 16 Jun 2001 14:11:40 +0200	[thread overview]
Message-ID: <20010616141140.A1593@solo.franken.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0106151702300.22155-100000@stout.engsoc.carleton.ca> <E15B17v-000790-00@the-village.bc.nu>
In-Reply-To: <E15B17v-000790-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Fri, Jun 15, 2001 at 10:27:35PM +0100

On Fri, Jun 15, 2001 at 10:27:35PM +0100, Alan Cox wrote:
> > Just this morning, our firewall get a kernel panic after 500 days of
> > uptime.
> 
> Interesting very interesting in fact. There is a 497 day wrap on the kernel but
> it should do nothing more than send the uptime back to zero. Im not sure
> how the crash fits in to this but it could be significant that its about
> the wrap time

there is a division by zero possibilty in the 2.0.35 do_fast_gettimeoffset
(there is a division by jiffies, which is 0 for one tick). Our department
server got struck by this at the jiffies rollover some time ago.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea.                                 [ Alexander Viro on linux-kernel ]

  parent reply	other threads:[~2001-06-16 12:16 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 [this message]
2001-06-15 21:35         ` Alexander Viro
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=20010616141140.A1593@solo.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@engsoc.org \
    --subject='Re: Kernel 2.0.35 limits' \
    /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

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).