From: Jiri Kosina <jkosina@suse.cz>
To: Bringer Didier <dda@awalis.com>
Cc: Pavel Machek <pavel@ucw.cz>, linux-kernel@vger.kernel.org
Subject: Re: keyboard problems on HP Pavilion ZE4200
Date: Tue, 16 Jun 2009 10:48:27 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.0906161044590.7457@wotan.suse.de> (raw)
In-Reply-To: <2558ACFA-84E2-4948-B371-D4F9606C0B15@awalis.com>
[ restored CC list ]
On Thu, 11 Jun 2009, Bringer Didier wrote:
> > > >Under linux (ubuntu 9) some keys are "pressed" even when I'm not
> > > >touching the keyboard, so for example it launches the tool for the
> > > >printscreen hundreds of times and then the machine is not usable
> > > >anymore...
> > >Which kernel? Does it happen on 2.6.30? Does it happen on console?
> > >Which keys?
> >
> >Also output of 'evtest' on the corresponding device in /dev/input/event?
> >from the time the key(s) get stuck will be helpful.
> >
> >Is the keyboard in question PS2-conntected or USB-connected?
> First of all, thank you for your answer
>
> Kernel : Linux champ 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC
> 2009 i686 GNU/Linux
>
> Output of evtest /dev/input/event4 while the bug appears
> Event: time 1244751563.258790, -------------- Report Sync ------------
>Event: time 1244751563.349861, type 4 (Misc), code 4 (ScanCode), value 54
> Event: time 1244751563.349897, type 1 (Key), code 99 (SysRq), value 1
> Event: time 1244751563.349900, -------------- Report Sync ------------
> Event: time 1244751563.370076, type 4 (Misc), code 4 (ScanCode), value 38
> Event: time 1244751563.370107, type 1 (Key), code 56 (LeftAlt), value 0
> Event: time 1244751563.370109, -------------- Report Sync ------------
> Event: time 1244751563.401550, type 4 (Misc), code 4 (ScanCode), value 0f
> Event: time 1244751563.401583, type 1 (Key), code 15 (Tab), value 0
> Event: time 1244751563.401586, -------------- Report Sync ------------
> Event: time 1244751563.599697, type 4 (Misc), code 4 (ScanCode), value 54
> Event: time 1244751563.599731, type 1 (Key), code 99 (SysRq), value 2
So forever-repeating sysrq/printscreen is really coming out of the evdev
input node.
Could you please boot you kernel with i8042.debug kernel parameter and
send the output from the time the bug triggers? This way we'll see whether
the repeated key really arrives from PS/2.
> I will try with a 2.6.30 soon
Do you know about any kernel version where this bug didn't trigger?
> Weirdly the bug doesn't seem to work when I use KDE as windowsmanager...
> Under gnome it is every 20 seconds that it happens. I cannot say that
> the bug really doesn't appear under kde but I cannot see effects of it
You can check the evtest output when running KDE, if the repeated key
appears there as well.
--
Jiri Kosina
SUSE Labs
prev parent reply other threads:[~2009-06-16 8:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3277220fa08b0d9b83dd7598e6f360d5@192.168.1.20>
2009-06-09 20:02 ` Pavel Machek
2009-06-09 22:47 ` Jiri Kosina
[not found] ` <2558ACFA-84E2-4948-B371-D4F9606C0B15@awalis.com>
2009-06-16 8:48 ` Jiri Kosina [this message]
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=alpine.LNX.2.00.0906161044590.7457@wotan.suse.de \
--to=jkosina@suse.cz \
--cc=dda@awalis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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
all inboxes | Powered by JetHome®