Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S279889AbRJ3Hgn>; Tue, 30 Oct 2001 02:36:43 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S279892AbRJ3Hgc>; Tue, 30 Oct 2001 02:36:32 -0500
Received: from gw.lowendale.com.au ([203.26.242.120]:18288 "EHLO
	marina.lowendale.com.au") by vger.kernel.org with ESMTP
	id <S279889AbRJ3Hg1>; Tue, 30 Oct 2001 02:36:27 -0500
Date: Tue, 30 Oct 2001 18:46:03 +1100 (EST)
From: Neale Banks <neale@lowendale.com.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Nasty suprise with uptime
In-Reply-To: <E15yJD1-0003uO-00@the-village.bc.nu>
Message-ID: <Pine.LNX.4.05.10110301839250.23080-100000@marina.lowendale.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

On Mon, 29 Oct 2001, Alan Cox wrote:

> > and received a nasty surprise. The uptime, which had been 496+ days
> > on Friday, was back down to a few hours. I was ready to lart somebody
> > with great vigor when I realized the uptime counter had simply wrapped
> > around.
> > 
> > So, I thought to myself, at least the 2.4 kernels on our new boxes won't
> 
> It wraps at 496 days. The drivers are aware of it and dont crash the box

You mean there was a time when uptime>496days would crash a system?

If so, approximtely when did that get fixed?

(I'm thinking back to an as yet unexplained crash of a 2.0.38 system at
~496days uptime :-( )

Thanks,
Neale.

-
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/