From owner-freebsd-current Mon Nov 27 08:34:56 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA10928 for current-outgoing; Mon, 27 Nov 1995 08:34:56 -0800 Received: from ast.com (irvine.ast.com [165.164.128.2]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id IAA10922 for ; Mon, 27 Nov 1995 08:34:50 -0800 Received: from fw.ast.com by ast.com with SMTP id AA15900 (5.67b/IDA-1.5 for ); Mon, 27 Nov 1995 08:36:15 -0800 Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #4) id m0tK6Kw-00008TC; Mon, 27 Nov 95 10:23 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #20) id m0tK6Cl-0008mtC; Mon, 27 Nov 95 10:14 WET Message-Id: Date: Mon, 27 Nov 95 10:14 WET To: current@FreeBSD.org From: uhclem%nemesis@fw.ast.com (Frank Durda IV) Sent: Mon Nov 27 1995, 10:14:55 CST Subject: Re: Theory Failed: screen vs keyboard lock-up Sender: owner-current@FreeBSD.org Precedence: bulk [1]I can't tell you what's causing it but I've got similar symptoms [1]since the beginnings. Right now I'm running 2.1.0-SNAP-9507?? and [1]it still happens every now and then. The only thing I noticed is [1]that it always happens when I switch screens during disk activity. [1]Also note that during a lockup I'm able to login on a serial line [1]and everything works OK*. It's only the console input which is lost [1]until I reboot the machine. I also came across this problem in 1.1.5.1 on keyboards made by Fujitsu and others (all keyboards 8042-based). If the system was particularly busy on disk when I did a ALT-Fn screen change, about 10% of the time the keyboard would appear to lock up. You could effectively cause the lockup to happen by rapidly changing between screens that had updates occuring on them, such as "ls -alR /" on a couple of screens, then toggle between them. I also found that all I had to do was unplug and reconnect the keyboard while the system was running and the keyboard would resume functioning. No need to reboot. The problem completely disappeared for these keyboard brands (at least on the systems I am responsible for) when I switched them over to 2.0.5-RELEASE. Perhaps the timing was changed but not enough to cover all keyboards, such as those using the "COPS" controller instead of a 8042. (The "COPS" controller is a different processor used in some keyboards to avoid the fury of the Texas Instruments Patent Lawyers(TM) who have a patent on keyboard matrix scanning from the pocket calculator days.) Try unplugging and reconnecting the keyboard and see if it "wakes up". Frank Durda IV |"Knowledge is power, so be sure or uhclem%nemesis@fw.ast.com (Fastest Route)| to give some away today. ...letni!rwsys!nemesis!uhclem | Doing this annoys Microsoft." ...decvax!fw.ast.com!nemesis!uhclem | (c) 1995 FDIV