Return-Path: <amu@MIT.EDU>
Received: from grand-central-station.mit.edu by po11.mit.edu (8.9.2/4.7) id PAA00108; Sat, 20 Apr 2002 15:18:16 -0400 (EDT)
Received: from manawatu-mail-centre.mit.edu (MANAWATU-MAIL-CENTRE.MIT.EDU [18.7.7.71])
	by grand-central-station.mit.edu (8.9.2/8.9.2) with ESMTP id PAA10281;
	Sat, 20 Apr 2002 15:17:40 -0400 (EDT)
Received: from multics.mit.edu (MULTICS.MIT.EDU [18.187.1.73])
	by manawatu-mail-centre.mit.edu (8.9.2/8.9.2) with ESMTP id PAA10463;
	Sat, 20 Apr 2002 15:17:40 -0400 (EDT)
Received: (from amu@localhost) by multics.mit.edu (8.9.3)
	id PAA23909; Sat, 20 Apr 2002 15:17:39 -0400 (EDT)
Sender: amu@MULTICS.MIT.EDU
To: Alex Coventry <alex_c@MIT.EDU>
Cc: Sipb-Office <sipb-office@MIT.EDU>
Subject: Re: yet another kinesis failure.
References: <200204201733.NAA23965@opus.mit.edu>
From: amu@alum.mit.edu (Aaron M. Ucko)
Date: 20 Apr 2002 15:17:39 -0400
In-Reply-To: <200204201733.NAA23965@opus.mit.edu>
Message-ID: <udl662mrxgs.fsf@multics.mit.edu>
Lines: 15
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

[Kinesis dropped from Cc: list.]

Alex Coventry <alex_c@MIT.EDU> writes:

> If sending another replacement chip is the least-effort solution to
> this, that would suit me.  However, I'm starting to wonder if it's not a
> problem with this batch of boards.  If you'd like me to send this board
> back for more thorough diagnosis, let me know how to do so.

Another hypothesis is that these chip failures result from attempting
to hot-swap keyboards, which IIRC is Unsupported all around.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
Finger amu@monk.mit.edu (NOT a valid e-mail address) for more info.
