From owner-freebsd-current  Wed Nov 29 05:14:58 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id FAA14087
          for current-outgoing; Wed, 29 Nov 1995 05:14:58 -0800
Received: from terra.stack.urc.tue.nl (terra.stack.urc.tue.nl [131.155.140.128])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id FAA14082
          for <current@freebsd.org>; Wed, 29 Nov 1995 05:14:55 -0800
Received: (from uucp@localhost) by terra.stack.urc.tue.nl (8.6.11) with UUCP id OAA11528; Wed, 29 Nov 1995 14:14:33 +0100
Received: (from freebsd@localhost) by xaa.stack.urc.tue.nl (8.6.12/8.6.9) id NAA06456; Wed, 29 Nov 1995 13:28:20 +0100
From: FreeBSD matters of Mark Huizer (xaa) <freebsd@xaa.stack.urc.tue.nl>
Message-Id: <199511291228.NAA06456@xaa.stack.urc.tue.nl>
Subject: Re: Theory Failed: screen vs keyboard lock-up
To: scrappy@hub.org (Marc G. Fournier)
Date: Wed, 29 Nov 1995 13:28:18 +0100 (MET)
Cc: current@freebsd.org
In-Reply-To: <Pine.BSF.3.91.951128130740.7163F-100000@hub.org> from "Marc G. Fournier" at Nov 28, 95 01:10:20 pm
Reply-To: xaa@stack.urc.tue.nl (Mark Huizer)
X-Mailer: ELM [version 2.4 PL24 ME8b]
Content-Type: text
Content-Length: 599       
Sender: owner-current@freebsd.org
Precedence: bulk

> 	Oops, glad you reminded me of that...I had totally forgotten that
> it did do that :(  I've been trying everyone's suggestions on how to see
> where the problem is too...
> 
> 	But it still leaves us effectively nowhere.  

Hmm... I had the problem too, and wrote a little program that just performs


  struct { int rep:5;
           int del:2;
	   int pad:1;
	 } rate;

  rate.del = 1;
  rate.rep = 15;
  while (1)
  {
    if (ioctl(0,KDSETRAD,rate) < 0)
	perror("Setting keyboard rate");
    sleep(5);
  }

And I never have to wait for more than a few seconds to get my keyboard back
> 

Mark