From owner-freebsd-hackers Tue Jun 27 10:25:16 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA23612 for hackers-outgoing; Tue, 27 Jun 1995 10:25:16 -0700 Received: from tserv.lodgenet.com (root@dial13.iw.net [204.157.148.62]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA23482 for ; Tue, 27 Jun 1995 10:23:49 -0700 Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by tserv.lodgenet.com (8.6.12/8.6.12) with ESMTP id MAA01140; Tue, 27 Jun 1995 12:22:42 -0500 Received: from localhost (localhost [127.0.0.1]) by jake.lodgenet.com (8.6.11/8.6.9) with SMTP id MAA21424; Tue, 27 Jun 1995 12:23:07 -0500 Message-Id: <199506271723.MAA21424@jake.lodgenet.com> X-Authentication-Warning: jake.lodgenet.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6 4/21/95 To: jan@bagend.atl.ga.us (Jan Isley) cc: hackers@freebsd.org, rgrimes@gndrsh.aac.dev.com Subject: Re: update on keyboard lockup with SNAP In-reply-to: Your message of "Mon, 26 Jun 1995 11:18:08 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 Jun 1995 12:23:06 -0500 From: "Eric L. Hernes" Sender: hackers-owner@freebsd.org Precedence: bulk > It is definitely related to the number of keystrokes, sort of. > It just spent about two hours playing with the system with no > keyboard freeze. And then it occurred to me that when it locked > up before I was changing windows a lot but this time I had not. > So, with four virtual terminals logged in and one finger on the > ALT key, with something going in each window, like vmstat, top, > etc, I switched windows about once a second ... for about one > minute ... then the keyboard froze. Output from top continued > to the window I got stuck on. Nothing, not even lighting the > caps lock light worked from the keyboard after that... had to > hit the reset button. I had a this problem about a year ago on a bsdi box. I could run stuff on the machine, and I could type for a while, but eventually the keyboard would just lock up. I ended up replacing the keyboard bios on the motherboard and everything started working. > -- > Jan Isley > coordinator, usenet volunteer votetakers > eric. -- erich@lodgenet.com erich@rrnet.com