Skip site navigation (1)Skip section navigation (2)
Date:      Sat,  1 Jul 2000 14:03:32 -0700 (PDT)
From:      dwhite@freebsd.org
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   bin/19630: systat consumes 100% CPU stuck in read() loop
Message-ID:  <20000701210332.88D1737BA6A@hub.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         19630
>Category:       bin
>Synopsis:       systat consumes 100% CPU stuck in read() loop
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jul 01 14:10:01 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     Doug White
>Release:        4.0-RELEASE
>Organization:
eGroups
>Environment:
FreeBSD nat1.egroups.com 4.0-RELEASE FreeBSD 4.0-RELEASE #1: Wed Jun 28 12:22:28 PDT 2000     root@test.corp.onelist.com:/usr/src/sys/compile/NATBOX  i386
466MHz Celeron, 256MB RAM
>Description:
After about a minute of running 'systat -vm 2', systat consumes 100% CPU,
50% user 50% system.  Running truss on it finds that it is getting 
EAGAIN trying to read stdin.  Truss output is available at 
http://www.freebsd.org/~dwhite/systat.truss, as it is too large to
post here.  I started truss after systat so the initialization is cut off,
but it shows the problem.
>How-To-Repeat:
Run systat -vm 2 and wait about a minute.
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:


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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000701210332.88D1737BA6A>