From: Pavel Machek <pavel@ucw.cz>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Andreas Mohr <andi@rhlx01.fht-esslingen.de>,
vojtech@suse.cz, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: strange keyboard lag after suspend testing
Date: Tue, 20 Mar 2007 17:31:13 +0100 [thread overview]
Message-ID: <20070320163113.GA5740@elf.ucw.cz> (raw)
In-Reply-To: <d120d5000703200909v326ab6benc3fb85badc061018@mail.gmail.com>
Hi!
> >> > I was testing suspend in 2.6.21-rc4 a lot, and now... machine feels
> >> > like someone added 50..100msec delay somewhere in keyboard
> >> > handling. Mouse does not seem affected. /proc/interrupts seem to
> >> > increase as they should, for both keyboard and mouse. Can someone
> >> > reproduce it? Any ideas how to debug it?
> >>
> >> Probably just asking the obvious:
> >> it's not a trivial "failed to re-configure repeat rate upon resume"
> >> (which one could rule out by running "kbdrate" again)
> >> but a lag in some interrupt handler or somewhere else deeper, right?
> >
> >No, it is not keyboard rate. Keyboard lags during normal typing,
> >sometimes letters come in groups of two or so...
>
> I might start looking at embedded controller changes and switches. If
> ACPI misbehaves that could starve keyboard controller... But you
> said
Mouse _seems_ okay, but I'm not sure if I'd notice lag there.
> that mouse is OK... Hmm, what happens if you load evbug and type while
> watching syslog. Do you observe the same delays?
Hmm, seems that it only happens in X... so maybe it is some strange
scheduling artefact?
Hmm, something is wrong here:
On console, I get expected 4-5 ticks a second. In x in gnome-terminal,
I get this:
root@amd:~# while true ; do echo -n . ; sleep .2; date; done
.Tue Mar 20 17:28:34 CET 2007
.Tue Mar 20 17:28:35 CET 2007
.Tue Mar 20 17:28:35 CET 2007
.Tue Mar 20 17:28:35 CET 2007
.Tue Mar 20 17:28:36 CET 2007
.Tue Mar 20 17:28:36 CET 2007
.Tue Mar 20 17:28:36 CET 2007
.Tue Mar 20 17:28:36 CET 2007
.Tue Mar 20 17:28:37 CET 2007
.Tue Mar 20 17:28:37 CET 2007
.Tue Mar 20 17:28:37 CET 2007
.Tue Mar 20 17:28:37 CET 2007
.Tue Mar 20 17:28:38 CET 2007
.Tue Mar 20 17:28:38 CET 2007
.Tue Mar 20 17:28:38 CET 2007
.Tue Mar 20 17:28:39 CET 2007
.Tue Mar 20 17:28:39 CET 2007
.Tue Mar 20 17:28:39 CET 2007
.Tue Mar 20 17:28:39 CET 2007
.Tue Mar 20 17:28:39 CET 2007
.Tue Mar 20 17:28:40 CET 2007
.Tue Mar 20 17:28:40 CET 2007
.Tue Mar 20 17:28:40 CET 2007
.Tue Mar 20 17:28:40 CET 2007
.Tue Mar 20 17:28:41 CET 2007
.Tue Mar 20 17:28:41 CET 2007
.Tue Mar 20 17:28:41 CET 2007
.Tue Mar 20 17:28:42 CET 2007
.Tue Mar 20 17:28:42 CET 2007
So sorry for false alarm, it is not keyboard related, it is just very
very strange.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2007-03-20 16:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-20 15:33 strange keyboard lag after suspend testing Pavel Machek
2007-03-20 16:00 ` Andreas Mohr
2007-03-20 16:03 ` Pavel Machek
2007-03-20 16:09 ` Dmitry Torokhov
2007-03-20 16:31 ` Pavel Machek [this message]
2007-03-20 16:38 ` Pavel Machek
2007-03-20 21:56 ` Rafael J. Wysocki
2007-03-21 20:12 ` Luca Tettamanti
2007-03-21 22:22 ` Pavel Machek
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=20070320163113.GA5740@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=andi@rhlx01.fht-esslingen.de \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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