linux-kernel - Re: 2.6.34-rc3++ looses PS2 keyboard eventually in xterms

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 8 Apr 2010 15:08:37 +0200
From:	"Hans-Peter Jansen" <hpj@...la.net>
To:	linux-kernel@...r.kernel.org
Cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>
Subject: Re: 2.6.34-rc3++ looses PS2 keyboard eventually in xterms

On Thursday 08 April 2010, 00:40:41 Hans-Peter Jansen wrote:
> Hi,
>
> after switching to 2.6.34-rc3 with follow ups added up to 5e11611a (e.g.
> including the tty fix), I still suffer from "loosing" my PS2 keyboard
> eventually during work in xterms (which I do use a lot). Everything else,
> ssh'ing from remotes, mouse operations, even mouse clicks into xterms is
> still functional, e.g. I'm able to quit htop by clicking on F10. Just
> every direct keyboard input is lost, without a trace in syslog, as well
> as Alt-SysReq sequences. echo r > /proc/sysrq-trigger doesn't show any
> effects either. AFAICT, it doesn't happen with older kernels
> (2.6.33.2/2.6.27.y).

Correction: 2.6.33.2 is affected as well. Problem is, I don't know a 
procedure, that reproduces the issue reliable, thus bisecting is not an 
option.

sysrq triggered process and lock state trace (when the keyboard was "lost") 
is available here: ftp://urpla.net/xrated-kbd-lockup

Dmitry, I've CC'ed you, since you seems the premier guy for input related 
issues. Do you have an idea? I guess, that my hardware setup isn't that 
uncommon, my keyboard is a "solid as a rock" Cherry G80, btw.

> OS/Hardware:
> openSUSE 11.1/i586, KDE3, ASUS P7P55-WS, Xeon X3460, 4 GB.
>
> Any hint on how to debug such an issue is much appreciated.
>
> Thanks,
> Pete
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> in the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/