Another problem

[Johnny Billquist <bqt%softjar.se@localhost>]

I've temporarily given up on my mutex implementation, since it's a big 
headache somewhere trying to figure out all the corners of the NetBSD 
mutex implementation.

Going back to the (new) cas implementation by Matt seems to atleast work 
(and slimmer than before, I think).
However, I have another observable problem, which I thought I'd drop in 
here, and see if anyone have any ideas on what is going on, or how to 
diagnose it better.

This on a system that has been up for almost one day, and running a 
bunch of things.

Looking at top:

load averages:  10.0,  9.25,  7.62;               up 0+22:08:03 
15:23:05
79 processes: 9 runnable, 69 sleeping, 1 on CPU
CPU states: 67.1% user,  0.0% nice, 28.8% system,  4.1% interrupt,  0.0% 
idle
Memory: 27M Act, 14M Inact, 4464K Wired, 8512K Exec, 4128K File, 824K Free
Swap: 256M Total, 44M Used, 212M Free

  PID USERNAME PRI NICE   SIZE   RES STATE      TIME   WCPU    CPU COMMAND
11311 root      25    0    26M   23M RUN       29:31 26.37% 26.37% cc1
15139 root      25    0  6608K 3620K RUN       10:26 19.19% 19.19% pkg_admin
21940 bqt       26    0  9964K 2288K RUN       50:24 17.92% 17.92% sshd
  166 bqt       79    0  3708K 1296K ttyraw    66:30  6.15%  6.15% systat
24014 bqt       78    0  3140K  620K pipe_rd   18:35  6.10%  6.10% dd
 1522 bqt       79    0  3708K 1288K ttyraw    50:37  5.86%  5.86% systat
20721 bqt       82    0  3536K 1116K select    10:02  4.15%  4.15% top
  167 bqt       36    0  3536K 1144K CPU       33:39  3.32%  3.32% top
11315 root       0    0     0K    0K RUN        0:00  0.00%  0.00% tcsh
22077 root       0    0     0K    0K RUN        0:00  0.00%  0.00% cron
12744 root       0    0     0K    0K RUN        0:00  0.00%  0.00% cron
24159 root       0    0     0K    0K RUN        0:00  0.00%  0.00% cron
12647 root       0    0     0K    0K RUN        0:00  0.00%  0.00% master
11881 root       0    0     0K    0K RUN        0:00  0.00%  0.00% cron

Notice the several processes that are marked as "RUN", but which are not 
using any memory at all. They have been sitting there for a while now, 
and don't seem to get unstuck.
I remember seeing this a few weeks ago as well, and they never got 
unstuck, and eventually the whole system stopped working.

Any suggestions on what is the problem?

Anything I could look at to find out more?

        Johnny