From ortmann@sparc.isl.net  Fri Apr 11 20:58:05 1997
Received: from watcher.isl.net (ppp-52.isl.net [199.3.25.101])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA11589
          for <FreeBSD-gnats-submit@freebsd.org>; Fri, 11 Apr 1997 20:58:01 -0700 (PDT)
Received: (from ortmann@localhost)
	by watcher.isl.net (8.8.5/8.8.5) id LAA00384;
	Fri, 11 Apr 1997 11:08:45 -0500 (CDT)
Message-Id: <199704111608.LAA00384@watcher.isl.net>
Date: Fri, 11 Apr 1997 11:08:45 -0500 (CDT)
From: Daniel Ortmann <ortmann@sparc.isl.net>
Reply-To: ortmann@sparc.isl.net
To: FreeBSD-gnats-submit@freebsd.org
Subject: /bin/ps: kernel kernel, lockups, performance problems
X-Send-Pr-Version: 3.2

>Number:         3259
>Category:       kern
>Synopsis:       /bin/ps: kernel kernel, lockups, performance problems
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Apr 11 21:00:01 PDT 1997
>Closed-Date:    Sat Aug 23 17:58:40 MEST 1997
>Last-Modified:  Sat Aug 23 17:59:00 MEST 1997
>Originator:     Daniel Ortmann
>Release:        FreeBSD 3.0-CURRENT i386
>Organization:
n/a
>Environment:

I am running a lightly-loaded system with very few users (all myself).
My standard shell is bash2.

>Description:

I've been able to lockup my system, causing kernel panics, severe
performance problems, etc doing the following:

ps ax

That's all.  This began occurring on FreeBSD 3.0-current around 
Apr 4, 1997 (or in that general timeframe).

This has happened both running as a regular user and as root.

If more than a couple of these ps commands are done then the system
is unable to survive ... even a shutdown causes a panic.

Note: I've experienced performance problems as well.  These problems
have appeared to be in sendmail, the gcc compiler (a make world
now takes at least 3 times longer than before!)

>How-To-Repeat:

ps ax should do it.  if that doesn't, then try running it in bash2.
if that still doesn't do it, then try it in bash2 like this:
MYVAR=`ps axwwopid,command | grep 'p*s'`  ... that's what led
originally to my observing the problem.

>Fix:

I don't know how to fix it; I'm not a kernel hacker.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: joerg 
State-Changed-When: Sat Aug 23 17:58:40 MEST 1997 
State-Changed-Why:  

Check request: does it still happen? 
>Unformatted:
