From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 7 Feb 2003 05:20:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 7 Feb 2003 05:20:52 -0500 Received: from [213.171.53.133] ([213.171.53.133]:14 "EHLO gulipin.miee.ru") by vger.kernel.org with ESMTP id ; Fri, 7 Feb 2003 05:20:52 -0500 Date: Fri, 7 Feb 2003 13:28:06 +0300 From: Samium Gromoff Message-Id: <200302071028.h17AS6Sx001862@ibe.miee.ru> To: jsimmons@infradead.org CC: linux-kernel@vger.kernel.org In-reply-to: (message from James Simmons on Fri, 20 Dec 2002 19:29:29 +0000 (GMT)) Subject: Re: [2.5.50] Keyboard dying References: User-Agent: SEMI/1.14.4 (Hosorogi) FLIM/1.14.4 (=?ISO-8859-4?Q?Kashiharaji?= =?ISO-8859-4?Q?ng=FE-mae?=) APEL/10.4 Emacs/21.2 (i386-pc-linux-gnu) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > > > > After some X <-> back switches keyboard stops doing anything. > > > > 2.5.50 + preempt enabled, X 4.2.1-debian-unstable. > > > > > > > > showkey started using gpm tells that the keys actually are pressed and > > > > processed by the kernel. > > > > Although even alt+sysrq+whatever do not make any effect. > > > > > > Can you disable preempt and see if you have the same problem. > > > > After some days of testing all seems fine. So preempt must be the trigger. > > The VT console system is totally not preempt safe. Everything is global. > I finished most of the work to make a preempt safe VT console system but > that will not go in this developement cycle. Same bug in 2.5.59/preempt. regards, Serge Kosyrev aka Samium Gromoff