From owner-freebsd-hackers Sun Apr 18 0:30:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id A0D8E150AB for ; Sun, 18 Apr 1999 00:30:50 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA77722; Sun, 18 Apr 1999 00:28:24 -0700 (PDT) (envelope-from dillon) Date: Sun, 18 Apr 1999 00:28:24 -0700 (PDT) From: Matthew Dillon Message-Id: <199904180728.AAA77722@apollo.backplane.com> To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: "paused" system References: <199904180418.AAA23919@cs.rpi.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I have another 'paused' system. It responds to kernel level stuff fine; :pings, VTY switches, scroll lock/pgup/pgdn. Nothing beyond that. No :network activity beyond what I send at it (the last case had NFS traffic). :This is not a critical system this time, so I am quite willing to let it sit :for awhile (it seemed to have died on april 15th). Anyone have any commands :or anything they would like me to try? : :BTW: This is a system from the days of 3.1-BETA. : :-- :David Cross | email: crossd@cs.rpi.edu If you can break into DDB ( usually ctl-alt-esc ), you can do a 'ps' to see what the processes are blocked on. It ought to be possible to narrow the problem down given that information. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message