From: "Natalie Protasevich" <protasnb@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>, Dmitry Torokhov <dtor@mail.ru>,
Vojtech Pavlik <vojtech@suse.cz>,
linux-input@atrey.karlin.mff.cuni.cz,
Alan Stern <stern@rowland.harvard.edu>
Subject: Keyboard problem
Date: Sun, 15 Jul 2007 21:28:37 -0600 [thread overview]
Message-ID: <32209efe0707152028h69b507b1j6ecd6c8e358ead62@mail.gmail.com> (raw)
Hello,
We have a problem with keybords here. It only hits several systems out
of many, and really impossible to reproduce because it happens on
different combinations of hardware/software and no one managed to find
out what triggers it. I had it on my workstation for a while, then it
was gone (was as of Friday when I hit it again).
Keyboard stops responding while mouse is still functional, if you hold
a key for a few seconds it reacts and displays a key (several of
them). If I hold down well ctrl-alt-F1 then I'm able to switch to text
screen and keyboard is just fine there. So it happens while X is
running, seems more likely when memory intensive apps are running
(firefox, kernel builds). Doesn't depend on type of videocard, whether
it is double or single monitor configuration, type of mouse (USB or
PS2 - but our HW guys said the systems have PS2 connector through the
USB bridge) - nothing seems to matter only presence of X. Restarting X
fixes a problem, but it is still very disruptive to everyone affected.
It seems like Linux input driver, USB and X may be involved. What can
be done to diagnose this problem? There is nothing in the logs, only
couple messages in X log which tell that screen saver was run a couple
times and mysterious message about Screen 0 and 1 now "sharing
resources". Do we need USB sniffer to trace traffic? Anything we can
do to get information from the kernel? Maybe instrumenting keyboard
driver and Xorg keyboard library somehow, use kprobes.
Any recommendations?
Thanks,
--Natalie
next reply other threads:[~2007-07-16 3:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 3:28 Natalie Protasevich [this message]
2007-07-16 13:29 ` Keyboard problem Dmitry Torokhov
2007-07-30 14:26 ` Jiri Kosina
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=32209efe0707152028h69b507b1j6ecd6c8e358ead62@mail.gmail.com \
--to=protasnb@gmail.com \
--cc=dtor@mail.ru \
--cc=jkosina@suse.cz \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=stern@rowland.harvard.edu \
--cc=vojtech@suse.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;
as well as URLs for NNTP newsgroup(s).