From owner-freebsd-hackers  Wed Feb 21 09:06:59 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA14088
          for hackers-outgoing; Wed, 21 Feb 1996 09:06:59 -0800 (PST)
Received: from baygull.rtd.com (baygull.rtd.com [198.102.68.5])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA14079
          for <hackers@freebsd.org>; Wed, 21 Feb 1996 09:06:55 -0800 (PST)
Received: (from news@localhost) by baygull.rtd.com (8.6.9/8.6.9.1) id KAA21886; Wed, 21 Feb 1996 10:06:35 -0700
To: hackers@freebsd.org
Path: freefall.freebsd.org!owner-freebsd-hackers
From: bugs@freebsd.netcom.com (Mark Hittinger)
Newsgroups: rtd.freebsd.hackers
Subject: re: processes wouldn't die
Date: Wed, 21 Feb 1996 08:47:24 -0600 (CST)
Lines: 31
Message-ID: <199602211447.IAA12886@freebsd.netcom.com>
NNTP-Posting-Host: seagull.rtd.com
Sender: owner-hackers@freebsd.org
Precedence: bulk

> From: "Philippe Charnier" <charnier@lirmm.fr>
> 
> Since some weeks, I run xsystats+rpc.rstatd to get information. rpc.rstatd
> receive signal 11 one or two times in a day. I also got the following
> configuration (reported by top) where I was not able to run the ps
> program nor to kill ps and rpc.rstatd.
> 11130 root     -18    0  484K   12K lockrd   0:00  0.00%  0.00% ps
> 11076 charnier -18    0  480K   12K lockrd   0:00  0.00%  0.00% ps
> 11088 charnier -18    0  480K   12K lockrd   0:00  0.00%  0.00% ps
> 11100 charnier -18    0  480K   12K lockrd   0:00  0.00%  0.00% ps
> 11143 root     -18    0  476K   12K lockrd   0:00  0.00%  0.00% ps
> 11154 root     -18    0  476K   12K lockrd   0:00  0.00%  0.00% ps
> 10967 root     -18    0  208K   12K lockrd   0:00  0.00%  0.00% rpc.rstatd

I'm seeing this problem also.  I believe that the 'ps' processes are hung 
trying to read something out of swap space.  It feels like a deadlock
condition to me.

Philippe, could you tell us about your hardware configuration and what sort
of software packages you run on that box?

For the 2.1 historically conscious I had these problems for awhile in the
sups after the 2.0-SNAP-0211 cut.  After a few weeks of sup'ing the problem
went away.  It returned a few weeks prior to the 2.1R cut and has been there
ever since.

Regards,

Mark Hittinger
Netcom/Dallas
bugs@freebsd.netcom.com