þÿDe : Thibaut VARENE <varenet@esiee.fr>
Date : Mar 11 juin 2002  10:08:05  Europe/Paris
À : Ryan Bradetich <rbradetich@uswest.net>
Cc : parisc-linux@lists.parisc-linux.org, grundler@cup.hp.com, Randolph Chung <randolph@tausq.org>
Objet : Rép : [parisc-linux] 2.4.18-pa35 SMP process hangs on a J200


Le mardi 11 juin 2002, à 07:36 , Ryan Bradetich a écrit :


> Digging into the system a bit, here is what I found:
> 
> 	* The setiathome process that hung (PID 326) will hang any other
> 	  process that tries to access /proc/326/*.  (This is why top,
> 	  ps, etc all hang after the process gets stuck).
Here we run a setiathome client, a distributed.net client, and from times to times we build isos.

This is consistent with what we experienced, but the first time we remarked a hung (after 44 days of uptime),
all proccesses that try to get info about running processes, such as 'top', 'ps' or even a 'ls /proc/PID/' would hang.
'w' would also hang, but not 'uptime'. It was with -pa16.

The second time we got a hang, with -pa33, 'ps -ef' hung just before displaying info about the setiathome client.

Another interesting thing is that after issuing any of these commands, the loadavg increased by 1,
ie if we got a loadavg of 2.00 before trying a ps, a w and a ls /proc/PID,
we would get a loadavg of 5.00 after these 3 commands.
> 
> 	* None of the other processes appear to be stuck. (ie. I can
> 	  access the /proc/PID/* information and the command will 	  return).
We cannot access such info, alas.


Anyway, as Randolph Chung said, Paul Bame's work might be interesting...



Thibaut VARENE
PA/Linux ESIEE Team
http://pateam.esiee.fr/


_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux