Bug 19630

Summary:	systat consumes 100% CPU stuck in read() loop
Product:	Base System	Reporter:	Doug White <dwhite>
Component:	bin	Assignee:	freebsd-bugs (Nobody) <bugs>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	4.0-RELEASE
Hardware:	Any
OS:	Any

Description Doug White freebsd_committer

2000-07-01 22:10:01 UTC

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.

Comment 1 Sheldon Hearn 2000-07-03 12:22:58 UTC

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.

Comment 2 dwhite 2000-07-04 00:55:39 UTC

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

Comment 3 Sheldon Hearn freebsd_committer

2000-07-05 11:49:34 UTC

State Changed
From-To: open->closed

The originator suspects his hardware and will open a new PR 
if he comes up with some more reproducible findings.