From owner-freebsd-bugs Tue May 15 7:10:15 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id EE98C37B423 for ; Tue, 15 May 2001 07:10:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f4FEA2Z56345; Tue, 15 May 2001 07:10:02 -0700 (PDT) (envelope-from gnats) Received: from psychotic.aberrant.org (psychotic.aberrant.org [64.81.134.141]) by hub.freebsd.org (Postfix) with ESMTP id 8F9A337B440 for ; Tue, 15 May 2001 07:01:14 -0700 (PDT) (envelope-from seth@psychotic.aberrant.org) Received: by psychotic.aberrant.org (Postfix, from userid 1000) id D071672501; Tue, 15 May 2001 10:01:13 -0400 (EDT) Message-Id: <20010515140113.D071672501@psychotic.aberrant.org> Date: Tue, 15 May 2001 10:01:13 -0400 (EDT) From: seth@psychotic.aberrant.org Reply-To: seth@psychotic.aberrant.org To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: kern/27334: load average constantly above 1.0, even when idle Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 27334 >Category: kern >Synopsis: load average constantly above 1.0, even when idle >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue May 15 07:10:02 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Seth >Release: FreeBSD 4.3-STABLE i386 >Organization: >Environment: System: FreeBSD psychotic.aberrant.org 4.3-STABLE FreeBSD 4.3-STABLE #0: Mon May 14 22:11:40 EDT 2001 seth@psychotic.aberrant.org:/usr/src/sys/compile/KERNEL-E i386 -STABLE from two days ago (13 May 2001). AMD Athlon Thunderbird 1GHz, /proc filesystem, securelevel=1. >Description: This sounds similar to kern/21155, but occurs in -STABLE rather than -CURRENT. It didn't happen on my old system (a dual-proc ppro 200), but there are so many differences: smp, 4.0 (vs -stable) that it's not a good comparison. Nothing seems to be affected, but any programs that rely on load average to determine whether or not to take or suspend action will be affected. This is why I made this report a medium priority. A quick snapshot from top: last pid: 1729; load averages: 1.00, 1.00, 1.00 up 0+11:41:00 09:58:15 40 processes: 1 running, 39 sleeping CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle Mem: 12M Active, 39M Inact, 21M Wired, 60K Cache, 35M Buf, 177M Free Swap: 512M Total, 512M Free PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 1729 seth 28 0 1892K 1172K RUN 0:00 1.08% 0.20% top 1367 root 2 0 2272K 1892K select 0:01 0.00% 0.00% sshd 1348 root 2 0 2232K 1852K select 0:01 0.00% 0.00% sshd 158 root 2 -12 1256K 844K select 0:00 0.00% 0.00% ntpd 1356 seth 2 0 2152K 1876K select 0:00 0.00% 0.00% epic-EPIC4-1.0 1354 seth 2 0 1568K 1256K select 0:00 0.00% 0.00% screen (there's more, but those are the top 6.) >How-To-Repeat: run top or uptime, check load average. >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message