From owner-freebsd-questions Tue Jan 18 14:16:12 2000 Delivered-To: freebsd-questions@freebsd.org Received: from sticky.usu.edu (sticky.usu.edu [129.123.1.155]) by hub.freebsd.org (Postfix) with ESMTP id 958B114F47 for ; Tue, 18 Jan 2000 14:16:10 -0800 (PST) (envelope-from hal@sticky.usu.edu) Received: from [129.123.1.184] (buffy.usu.edu [129.123.1.184]) by sticky.usu.edu (Postfix) with ESMTP id CAEAE3482E; Tue, 18 Jan 2000 15:16:09 -0700 (MST) X-Sender: hal@sticky.usu.edu (Unverified) Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 18 Jan 2000 15:16:09 -0700 To: FreeBSDQuestions From: hal Lynch Subject: HELP: Hung console Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG System: 3.0 with the bouncing daemon screen saver What I saw: The bouncing daemon was on the screen but was not bouncing. Not moving at all. Pushing keys including F1-F3 did nothing. Killing console all processes (ttyv0-2) did nothing. Telnet sessions, wweb server, etc worked just fine. Top reported ~98% idle time, no strangeness. Except for the console everything seemed to be working fine. What I did: Rebooted of course. Some of my users consider a daytime reboot to be anti-social behavior. What should I do: Short of rebooting what can I do when this happens again? Thanks hal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message