Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755770AbYCMNBi (ORCPT ); Thu, 13 Mar 2008 09:01:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753397AbYCMNBb (ORCPT ); Thu, 13 Mar 2008 09:01:31 -0400 Received: from rtr.ca ([76.10.145.34]:2604 "EHLO mail.rtr.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753345AbYCMNBa (ORCPT ); Thu, 13 Mar 2008 09:01:30 -0400 Message-ID: <47D925A7.1030706@rtr.ca> Date: Thu, 13 Mar 2008 09:01:27 -0400 From: Mark Lord Organization: Real-Time Remedies Inc. User-Agent: Thunderbird 2.0.0.12 (X11/20080213) MIME-Version: 1.0 To: "Fred ." Cc: linux-kernel@vger.kernel.org Subject: Re: Keys get stuck References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 839 Lines: 20 My Dell X1 notebook had this problem HUGELY, back in about 2.6.18 or so. Under *no* load to speak of, X would lose track of a "key up" event and forever be stuck on "key down". I could still use the mouse to start another X session simultaneously, and in that alternate X things worked fine. So it was definitely an X server process issue, not a system wide kernel thing. And not a GNOME thing -- I use KDE exclusively. Problem seems to have gone away since I put 2.6.23 onto that machine. Newer kernels have broken suspend/resume there, so 2.6.23 is as high as that one gets for now. -ml -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/