From owner-freebsd-stable  Wed May  7 17:30:36 1997
Return-Path: <owner-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id RAA27956
          for stable-outgoing; Wed, 7 May 1997 17:30:36 -0700 (PDT)
Received: from sendero.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA27951
          for <freebsd-stable@FreeBSD.ORG>; Wed, 7 May 1997 17:30:33 -0700 (PDT)
Received: (qmail 23258 invoked by uid 1000); 8 May 1997 00:06:39 -0000
Message-ID: <XFMail.970507170638.Shimon@i-Connect.Net>
X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <199705072127.QAA04248@cs.rice.edu>
Date: Wed, 07 May 1997 17:01:10 -0700 (PDT)
Organization: iConnect Corp.
From: Simon Shapiro <Shimon@i-Connect.Net>
To: "Mark W. Krentel" <krentel@cs.rice.edu>
Subject: Re: frozen virtual terminals on Dell system
Cc: freebsd-stable@FreeBSD.ORG
Sender: owner-stable@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


Hi Mark W. Krentel;  On 07-May-97 you wrote: 

...

> That's interesting.  I once had a keyboard lock up after disconnecting
> it for 1 day to use on another machine.  Machine is a PPro 200 on 
> Intel Venus VS440FX board (apparently with Intel's own BIOS) running 
> 2.1.7.  We borrowed the keyboard for > 24 hours, and on reconnecting, 
> all keystrokes were ignored. 
> 
> We ended up rebooting, which worked and also kicked off the screen
> saver.  There was nothing in the logs to indicate trouble, but just
> before it rebooted, I saw a SIGPIPE messge on the console (couldn't
> see it before because of screen saver).

...

This is a feature, I think.  The keyboard is not supposed to unplub and 
re-plug while the system is powderd up.  Most do, but not necessarily.
If something wants to download or configure in the keyboard at power up,
it will not have it.  some keyboard/motherboard combinations want to.

Simon