linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Andi Kleen <andi@firstfloor.org>,
	rjw@sisk.pl, linux-input@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [regression] 2.6.30 leaking keys on console switch
Date: Thu, 9 Jul 2009 22:03:18 +0200	[thread overview]
Message-ID: <20090709200318.GB16355@basil.fritz.box> (raw)
In-Reply-To: <alpine.LNX.2.00.0907091319480.27327@wotan.suse.de>

On Thu, Jul 09, 2009 at 01:20:56PM +0200, Jiri Kosina wrote:
> On Tue, 7 Jul 2009, Dmitry Torokhov wrote:
> 
> > > Are you seeing with a specific keyboard type(s), or is this a general 
> > > problem? Could you confirm whether it is specific either to PS2 or USB 
> > > keyboards only, or it does happen for both?
> > Can't think of any input chnages in this timeftrame that would cause
> > such effect. Maybe TTY changes?
> 
> By the way, if I understand it correctly, Andi is able to see the very 
> same effect even inside X, so tty can be possibly ruled out, right?
> 
> Still, I don't see the leaking F key in the evtest output (see the mail 
> from yesterday), which is quite puzzling.

Everything quite puzzling.

I find it puzzling that people cannot reproduce this. I see this on two
quite different systems (different keyboard, system). Does really nobody
else see it?

I checked now and it happens with both when I switch with Alt-Fx
and Ctrl-Alt-Fx (at least on SUSE the later works from the consoles
too, so i usually use that)

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only.

  parent reply	other threads:[~2009-07-09 20:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07  8:44 [regression] 2.6.30 leaking keys on console switch Andi Kleen
2009-07-07  8:50 ` Jiri Kosina
2009-07-07  9:12   ` Andi Kleen
2009-07-07  9:15     ` Jiri Kosina
2009-07-08  6:53   ` Dmitry Torokhov
2009-07-08 11:20     ` Jiri Kosina
2009-07-09 11:29       ` Jiri Kosina
2009-07-09 20:01         ` Andi Kleen
2009-10-14  4:58       ` Dmitry Torokhov
2009-10-14  7:19         ` Andi Kleen
2009-10-14  7:39           ` Dmitry Torokhov
2009-10-14  7:50             ` Dmitry Torokhov
2009-10-16  5:41             ` H. Peter Anvin
2009-10-19 21:38             ` Pavel Machek
2009-10-21  8:15               ` Dmitry Torokhov
2009-10-23 20:29                 ` Pavel Machek
2009-07-09 11:20     ` Jiri Kosina
2009-07-09 12:00       ` Andi Kleen
2009-07-09 20:03       ` Andi Kleen [this message]
2009-07-09 21:58         ` Jiri Kosina
2009-07-13  4:05       ` Dmitry Torokhov
2009-07-13  7:07         ` Jiri Kosina
2009-07-13  8:25           ` Andi Kleen
2009-07-16  9:02             ` Jiri Kosina
2009-07-16  9:24               ` Andi Kleen
2009-10-16  4:59                 ` Dmitry Torokhov

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=20090709200318.GB16355@basil.fritz.box \
    --to=andi@firstfloor.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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).