From nobody@FreeBSD.ORG  Sat Jul  1 14:03:32 2000
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 88D1737BA6A; Sat,  1 Jul 2000 14:03:32 -0700 (PDT)
Message-Id: <20000701210332.88D1737BA6A@hub.freebsd.org>
Date: Sat,  1 Jul 2000 14:03:32 -0700 (PDT)
From: dwhite@freebsd.org
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@FreeBSD.org
Subject: systat consumes 100% CPU stuck in read() loop
X-Send-Pr-Version: www-1.0

>Number:         19630
>Category:       bin
>Synopsis:       systat consumes 100% CPU stuck in read() loop
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jul 01 14:10:01 PDT 2000
>Closed-Date:    Wed Jul 5 03:49:34 PDT 2000
>Last-Modified:  Wed Jul 05 03:50:10 PDT 2000
>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:

From: Sheldon Hearn <sheldonh@uunet.co.za>
To: dwhite@FreeBSD.ORG
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: bin/19630: systat consumes 100% CPU stuck in read() loop 
Date: Mon, 03 Jul 2000 13:22:58 +0200

 On Sat, 01 Jul 2000 14:03:32 MST, dwhite@FreeBSD.ORG wrote:
 
 > >How-To-Repeat:
 > Run systat -vm 2 and wait about a minute.
 
 I can't duplicate this in 5.0-CURRENT (as of 2000-06-29).  Could you try
 with a 4.0-STABLE to see whether the problem exists there also?
 
 Ciao,
 Sheldon.
 

From: Doug White <dwhite@resnet.uoregon.edu>
To: Sheldon Hearn <sheldonh@uunet.co.za>
Cc: dwhite@FreeBSD.ORG, freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: bin/19630: systat consumes 100% CPU stuck in read() loop 
Date: Mon, 3 Jul 2000 16:55:39 -0700 (PDT)

 On Mon, 3 Jul 2000, Sheldon Hearn wrote:
 
 > 
 > 
 > On Sat, 01 Jul 2000 14:03:32 MST, dwhite@FreeBSD.ORG wrote:
 > 
 > > >How-To-Repeat:
 > > Run systat -vm 2 and wait about a minute.
 > 
 > I can't duplicate this in 5.0-CURRENT (as of 2000-06-29).  Could you try
 > with a 4.0-STABLE to see whether the problem exists there also?
 
 Doesn't happen on a -STABLE sup'd this morning (12:30AM PDT).  Doesn't do
 it on another 4.0-RELEASE box either, but it's not the same type of
 condition.  The problematic machine may have memory issues, though... grr.
 
 Doug White                    |  FreeBSD: The Power to Serve
 dwhite@resnet.uoregon.edu     |  www.FreeBSD.org
 
 
State-Changed-From-To: open->closed 
State-Changed-By: sheldonh 
State-Changed-When: Wed Jul 5 03:49:34 PDT 2000 
State-Changed-Why:  
The originator suspects his hardware and will open a new PR 
if he comes up with some more reproducible findings. 


http://www.freebsd.org/cgi/query-pr.cgi?pr=19630 
>Unformatted:
