From owner-freebsd-stable Thu Dec 4 07:12:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA27856 for stable-outgoing; Thu, 4 Dec 1997 07:12:12 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from silvia.HIP.Berkeley.EDU (ala-ca34-49.ix.netcom.com [207.93.143.177]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA27848 for ; Thu, 4 Dec 1997 07:12:08 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.8/8.6.9) id HAA01752; Thu, 4 Dec 1997 07:12:06 -0800 (PST) Date: Thu, 4 Dec 1997 07:12:06 -0800 (PST) Message-Id: <199712041512.HAA01752@silvia.HIP.Berkeley.EDU> To: stable@freebsd.org Subject: rc564 weirdness From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just noticed that rc564, started with idprio 31, sometimes goes to sleep and doesn't come back after a huge compilation. This is what it looks like now on one of our 2.2-stable (Aug 14 vintage) machines: === >> ps glx UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 569 13352 1 110 -18 19 816 72 vmopar DN ?? 20327:27.01 rc564 569 5730 5728 0 10 0 812 716 wait Ss p0 0:00.89 -bash (bash) 569 9870 5730 1 28 0 624 268 - R+ p0 0:00.00 ps -glx === I'm not sure if you can tell from this, but if I look with "top", the process is not taking up any CPU time anymore, even when the machine is idle. The rc564 binary is on an NFS server (2.2-stable, Oct 31), if that makes any difference. Also, on another machine, I didn't realize that rc564 is still there and started it again, and the second one immediately went to sleep too. I'm not sure if it's waiting on the same thing, I didn't ps glx that one. Satoshi