Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 30 Oct 2001 02:46:03 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 30 Oct 2001 02:45:53 -0500 Received: from adsl-63-194-239-202.dsl.lsan03.pacbell.net ([63.194.239.202]:28667 "EHLO mmp-linux.matchmail.com") by vger.kernel.org with ESMTP id ; Tue, 30 Oct 2001 02:45:47 -0500 Date: Mon, 29 Oct 2001 23:46:15 -0800 From: Mike Fedyk To: Neale Banks Cc: Alan Cox , Linux kernel Subject: Re: Nasty suprise with uptime Message-ID: <20011029234615.A14476@mikef-linux.matchmail.com> Mail-Followup-To: Neale Banks , Alan Cox , Linux kernel In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 30, 2001 at 06:46:03PM +1100, Neale Banks wrote: > 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 :-( ) > AFAIK, the system didn't crash, but the uptime counter went down to zero. - 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/