From owner-freebsd-current@FreeBSD.ORG Wed Jan 2 07:31:48 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7494F16A417 for ; Wed, 2 Jan 2008 07:31:48 +0000 (UTC) (envelope-from silby@silby.com) Received: from relay02.pair.com (relay02.pair.com [209.68.5.16]) by mx1.freebsd.org (Postfix) with SMTP id 2769313C442 for ; Wed, 2 Jan 2008 07:31:47 +0000 (UTC) (envelope-from silby@silby.com) Received: (qmail 20800 invoked from network); 2 Jan 2008 07:31:46 -0000 Received: from unknown (HELO localhost) (unknown) by unknown with SMTP; 2 Jan 2008 07:31:46 -0000 X-pair-Authenticated: 209.68.2.70 Date: Wed, 2 Jan 2008 01:31:45 -0600 (CST) From: Mike Silbersack To: current@freebsd.org In-Reply-To: <20071224020713.F1390@odysseus.silby.com> Message-ID: <20080102004324.U9178@odysseus.silby.com> References: <20071224020713.F1390@odysseus.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: Update: Repeated or missed keys after upgrading from 6.2 to 7.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jan 2008 07:31:48 -0000 On Mon, 24 Dec 2007, Mike Silbersack wrote: > In order to eat my own dog food, I upgraded my laptop from 6.2 to 7.0. This > seemed to have gone well, until I started writing a long e-mail while sitting > on the couch today. As I was typing the e-mail, I noticed that my typing > skills seemed to have gone missing; there were words missing 2-3 letters, and > other places where I was apparently holding down keyyyys. Heh, that's a real > example of the phenomenon right there. > > After a while I realized that I was not typing sloppily, but that in fact > keys are being lost in certain cases and duplicated in others. Since I did > not rebuild any ports or packages, I'm convinced that this is directly > related to the 7.0 upgrade. > > This behavior has shown up when running a local copy of pine (inside > konsole), chatting in ksirc, and in a few other programs. (I'm running KDE.) > I think it happens more when on battery than when plugged into an outlet. > I'm running xbattbar, so it could be querying the battery status and causing > problems. This is using the laptop's built-in keyboard (non-USB.) > > I'm going to try to track this down, although I don't know how successful > I'll be. I'd like to know if anyone else has seen this problem and if they > have any additional information that might help me track it down faster. > > Thanks, > > Mike "Silby" Silbersack Thanks to everyone who responded to this thread. Here's what I've learned since my initial message: 1. Other people have seen this problem (or something similar) as far back as 5.x. 1a. I noticed in my kernel config file that I did NOT have kdbmux in my 6.2 kernel config file, but I do have it in my 7.0 kernel config file. However, I also tried recompiling 7.0 without kbdmux, and the problem still occurs. 2. The problem only happens when I have xbattbar running. Whether or not I'm actually running on battery makes no difference. 3. Ssh sessions into the box do not appear to be affected. 4. If I plug in a USB keyboard, it does not seem to be affected. (Either with or without kbdmux.) I've added some KTR debugging statements to try to help me track this down, but I have not yet made much progress. Mike "Silby" Silbersack