From owner-cvs-all  Mon Oct 19 09:47:52 1998
Return-Path: <owner-cvs-all@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA22720
          for cvs-all-outgoing; Mon, 19 Oct 1998 09:47:52 -0700 (PDT)
          (envelope-from owner-cvs-all@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22714;
          Mon, 19 Oct 1998 09:47:50 -0700 (PDT)
          (envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.1/8.9.1) id JAA16488;
	Mon, 19 Oct 1998 09:47:19 -0700 (PDT)
	(envelope-from dillon)
Date: Mon, 19 Oct 1998 09:47:19 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199810191647.JAA16488@apollo.backplane.com>
To: Bruce Evans <bde@zeta.org.au>
Cc: cvs-all@FreeBSD.ORG, cvs-committers@FreeBSD.ORG
Subject: Here's another odd one:  'cputime exceeded' when no cpu limit set
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk

    I get this occassionally (on a 200 MHz PPro).  FreeBSD-current,
    lightly loaded machine.  I've been getting this for several
    months.

apollo:/usr/src/sys# fgrep vm_page_flag_clear */*.c
Cputime limit exceeded

    I added debug code to the kernel.  In calcru() I added:

        if (totusec < 0) {
                /* XXX no %qd in kernel.  Truncate. */
                printf("calcru: negative time of %ld usec for pid %d (%s)\n",
                       (long)totusec, p->p_pid, p->p_comm);
                totusec = 0;
        }

    And whenever I get Cputime limit exceeded, the following
    kernel message is logged:

calcru: negative time of -21451087 usec for pid 16447 (fgrep)

    It seems to occur sometimes I run a command from a shell prompt
    that has been idle for a while.  Whenever I run the command
    a second time, it works.  The shell command run does not
    seem to matter as long as it takes a non-trivial amount of
    time to execute.  i.e. ps, fgrep, trn, etc...

    When it does occur, it seems to occur within the first second
    of command execution.

    At first I thought it was due to me setting various CLK flag
    in the kernel config but I've turned off those flags and it
    still occurs.  I tried to zero the value, but that doesn't
    seem to work either... the fgrep still dies with the cpu
    limit signal.

    It is very weird.

					-Matt

    Matthew Dillon  Engineering, HiWay Technologies, Inc. & BEST Internet 
                    Communications & God knows what else.
    <dillon@backplane.com> (Please include original email in any response)    


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message