linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Simmons <jsimmons@infradead.org>
To: Samium Gromoff <deepfire@ibe.miee.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.5.50] Keyboard dying
Date: Thu, 5 Dec 2002 20:40:42 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0212052039560.31967-100000@phoenix.infradead.org> (raw)
In-Reply-To: <200212051456.gB5Eusbv000881@ibe.miee.ru>


>        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.
 


  reply	other threads:[~2002-12-05 20:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-05 14:56 [2.5.50] Keyboard dying Samium Gromoff
2002-12-05 20:40 ` James Simmons [this message]
2002-12-07  9:56   ` Samium Gromoff
2002-12-15 10:07   ` Samium Gromoff
2002-12-20 19:29     ` James Simmons
2003-02-07 10:28       ` Samium Gromoff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.44.0212052039560.31967-100000@phoenix.infradead.org \
    --to=jsimmons@infradead.org \
    --cc=deepfire@ibe.miee.ru \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).