Strange (deadlock?) when running ps(1) and top(1)

From: Xin LI <delphij_at_frontfree.net>
Date: Tue, 2 Mar 2004 23:32:54 +0800
Hello gang,

With a recently built kernel and world from -HEAD, I found that
running ps(1) or top(1) can sometimes trigger some weird problem
to cause the system to completely stop to respond. The situation
is very serious that even ddb(4) could not be activated, hence I
can not provide more useful information at present.

Currently I am trying to figure out what caused the problem. The
box runs 5-CURRENT built 20 days ago previously, it builds world
and kernel periodically (twice a week or even more), it crashed
today and therefore it is now running:

FreeBSD beastie.frontfree.net 5.2-CURRENT FreeBSD 5.2-CURRENT #40: Tue Mar  2 17:38:46 CST 2004     delphij_at_beastie.frontfree.net:/usr/obj/usr/src/sys/BEASTIE  i386

A friend of mine encountered similar problem on his Alpha box, as
well as a VMWare contained FreeBSD/i386 guest. I'll post subsequent
results here if I got some findings, and hopefully, a patch to
solve this :-)

Cheers,
-- 
Xin LI <delphij frontfree net>	http://www.delphij.net/
See complete headers for GPG key and other information.


Received on Tue Mar 02 2004 - 06:33:13 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:45 UTC