From owner-freebsd-current Wed Aug 19 16:48:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01372 for freebsd-current-outgoing; Wed, 19 Aug 1998 16:48:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-d7.dialup.hilink.com.au [203.2.144.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01340 for ; Wed, 19 Aug 1998 16:48:05 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA03559; Wed, 19 Aug 1998 16:45:37 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808191645.QAA03559@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman cc: Bruce Evans , freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: 13 months of user time? In-reply-to: Your message of "Wed, 19 Aug 1998 17:22:50 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Aug 1998 16:45:36 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At a guess, it's either in or related to this fragment from kern/kern_synch.c: /* * Compute the amount of time during which the current * process was running, and add that to its total so far. */ microuptime(&switchtime); p->p_runtime += (switchtime.tv_usec - p->p_switchtime.tv_usec) + (switchtime.tv_sec - p->p_switchtime.tv_sec) * (int64_t)1000000; Either microuptime() is returning garbage, or the calculation is bogus. > It's probably a good idea to get this fixed ASAP, since people have been > complaining about this exact bug for months now. Would anyone like to give > me any pointers to where to start evaluating the code at, or what > functions this could be caused by? I think I'll check the process > accounting code first then the actual timing code, if noone has any better > ideas. > > Brian Feldman > green@unixhelp.org > > On Thu, 20 Aug 1998, Bruce Evans wrote: > > > > I found this on a 3 month old snap, and have now replicated it > > >on 3.0-980818-SNAP. > > > > > >for i in /bin/*; do > > > time rsh nodename uptime > > >done > > > > > > Yields the following output: > > > > > >..... > > > 2:00PM up 1 day, 1:39, 1 user, load averages: 0.00, 0.00, 0.00 > > > 0.19s real 0.00s user 0.00s system > > > 2:00PM up 1 day, 1:39, 1 user, load averages: 0.00, 0.00, 0.00 > > > 0.20s real 33554431.00s user 0.00s system > > > > This is probably just a symptom of a negative times bug and assorted > > overflows. This negative times bug usually kills processes with a > > SIGXCPU. > > > > Bruce > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message