From owner-freebsd-questions Mon Oct 16 01:54:46 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA00963 for questions-outgoing; Mon, 16 Oct 1995 01:54:46 -0700 Received: from pcca71.gallaudet.edu (root@pcca71.gallaudet.edu [134.231.56.107]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA00956 for ; Mon, 16 Oct 1995 01:54:39 -0700 Received: (from jon@localhost) by pcca71.gallaudet.edu (8.6.12/8.6.12) id EAA00457; Sun, 15 Oct 1995 04:57:06 GMT Date: Sun, 15 Oct 1995 04:57:06 +0000 () From: Basket Case To: Freebsd Questions Subject: Keyboard locking up again along with potential answers/problems (I guess) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org Precedence: bulk Hi -- Ive reported this problem twice and am now making a third report with more detailed information... I'm running 2.1.0-950928-SNAP on a p5-100 machine with 16 mb ram, 42 mb swap. When I was using the machine, I had a few things compiling at once, and so were a few of my users. All of a sudden the machine locked up after I switched virtual consoles. This time screen saver was not enabled at all, nor was XWindows. After investigating this problem further, I notice that when I use a lot of ram (disk processes), some things get thrown in infinite swap space and never is drawn out (apparently.) What I am thinking the problem may be with that the keyboard driver/daemon is thrown in the swap space and "dies". I know a few of my programs get thrown there and they never resume processing for some odd reason, even if memory requirements reduce. =( I guess the only way to fix this right now is to buy more memory... Jon