Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265406AbTFMRF0 (ORCPT ); Fri, 13 Jun 2003 13:05:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265437AbTFMRF0 (ORCPT ); Fri, 13 Jun 2003 13:05:26 -0400 Received: from p68.rivermarket.wintek.com ([208.13.56.68]:29174 "EHLO dust") by vger.kernel.org with ESMTP id S265406AbTFMRFU (ORCPT ); Fri, 13 Jun 2003 13:05:20 -0400 Date: Fri, 13 Jun 2003 12:21:11 -0500 (EST) From: Alex Goddard To: Tim Schmielau Cc: Clemens Schwaighofer , Linux Kernel Mailing List Subject: Re: uptime wrong in 2.5.70 In-Reply-To: Message-ID: References: X-GPG-PUBLIC_KEY: N/a X-GPG-FINGERPRINT: BCBC 0868 DB78 22F3 A657 785D 6E3B 7ACB 584E B835 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 Content-Length: 928 Lines: 26 On Fri, 13 Jun 2003, Tim Schmielau wrote: > > I a got a test vmware running with a 2.5.70 and I have sligh "overflow" > > with my uptime. > > > > gentoo root # uptime > > 22:29:47 up 14667 days, 19:08, 3 users, load average: 0.00, 0.00, 0.00 > > Doesn't ring any bell yet. Can you cat /proc/uptime and /proc/stat output? > Is this immediately after booting? Reproducable? I had this happen yesterday with a 2.5.70-bkWhatever from about three days ago. Immediately after boot my uptime was reported as 14664 days, 13 hours. I didn't do a cat of either /proc/uptime or /proc/stat. If the bug hits again, I'll do so and post the results. -- Alex Goddard agoddard@purdue.edu - 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/