From owner-freebsd-hackers Mon May 22 07:26:30 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA25171 for hackers-outgoing; Mon, 22 May 1995 07:26:30 -0700 Received: from Glock.COM (root@glock.com [198.82.228.165]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA25164 for ; Mon, 22 May 1995 07:26:28 -0700 Received: (from mmead@localhost) by Glock.COM (8.6.11/8.6.9) id KAA09095; Mon, 22 May 1995 10:27:15 -0400 Date: Mon, 22 May 1995 10:27:15 -0400 From: "matthew c. mead" Message-Id: <199505221427.KAA09095@Glock.COM> To: hackers@FreeBSD.org Subject: Diagnostics for a hanging machine? Sender: hackers-owner@FreeBSD.org Precedence: bulk The ACM student chapter at Virginia Tech has a FreeBSD machine for our members use which I administrate. Recently FreeBSD was installed on this machine in favor of NetBSD, and we are experiencing frequent machine hangs. It appears the hangs are hardware related, as they also occurred in NetBSD. Unfortunately what happens is the machine gets frozen on a vty, and does not go through a clean reboot. Does anyone know of a diagnostic utility that could either constantly spew information to disk, or (preferably) across the net to a machine that's more stable so we can find out what's going on? Any help whatsoever is appreciated; we really need to get the machine stable. Thanks! -matt -- Matthew C. Mead -> Virginia Tech Center for Transportation Research - -> Multiple Platform System and Network Administration Work Related -> mmead@ctr.vt.edu | mmead@goof.com <- All Other ---- ------- WWW -> http://www.goof.com/~mmead --- -----