From owner-freebsd-questions  Mon Mar 30 23:50:48 1998
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id XAA08001
          for freebsd-questions-outgoing; Mon, 30 Mar 1998 23:50:48 -0800 (PST)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from alpha.delta.edu (alpha.delta.edu [161.133.129.3])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA07991
          for <freebsd-questions@freebsd.org>; Mon, 30 Mar 1998 23:50:44 -0800 (PST)
          (envelope-from dakott@alpha.delta.edu)
Received: from pm143-01.dialip.mich.net by alpha.delta.edu; (5.65v3.0/1.1.8.2/06Jan97-0932AM)
	id AA25264; Tue, 31 Mar 1998 02:53:44 -0500
Received: from kott.my.domain (dakott@kott.my.domain [192.168.0.1])
	by kott.my.domain (8.8.8/8.8.5) with SMTP id VAA27935
	for <freebsd-questions@freebsd.org>; Mon, 30 Mar 1998 21:50:47 -0500 (EST)
Date: Mon, 30 Mar 1998 21:50:43 -0500 (EST)
From: David Kott <dakott@alpha.delta.edu>
To: freebsd-questions@FreeBSD.ORG
Subject: "Hung" Virtual terminal in -stable.  Doesn't respond to "kill -KILL".
Message-Id: <Pine.BSF.3.96.980330212403.20039A-100000@kott.my.domain>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


This happens to my machine on a semi-regular basis, basically, when the
computer is left running for several days unattended;  that is, I don't
login, ttyv0 ends up "hanging".  It no longer responds to keypresses or
"kill -KILL" attempts.  In the past, I have to reboot the computer to
get rid of this process.  I have never seen any other virtual terminal
exibit this behavior; only ttyv0.   Here is some output from ps:

USER       PID  PPID  PGID   SESS JOBC STAT  TT       TIME COMMAND
root     18274     1 18274 7aace0    0 I<Es+  v0-   0:00.00  (login)

According to the manpage, this process is idling, not surprising as I
haven't done anything with that terminal all night... Has "raised CPU
scheduling".. no clue there.. it seems that no other processes are listed
as having increased service rates.  "E", denoting that the process is
trying to exit.. no doubt from the kill -KILL I sent it when it stopped
responding.  "s", denoting that the process is a session leader, and
finally the "+" showing that the process is the forground group.

top had this information to provide on this process:

PID USERNAME PRI NICE SIZE    RES STATE    TIME   WCPU    CPU COMMAND
18274 root      4  -4   184K   228K ttywai   0:00  0.00%  0.00% login

I am using:

FreeBSD 2.2.6-BETA FreeBSD 2.2.6-BETA #0: Sun Mar 22 22:44:22 EST
1998

Has anyone experienced anything similar, or perhaps have a suggestion on
how to clear up this behavior?

								-d


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message