mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Pavel Machek" <pavel@ucw.cz>
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 12:09:42 -0400	[thread overview]
Message-ID: <d120d5000703200909v326ab6benc3fb85badc061018@mail.gmail.com> (raw)
In-Reply-To: <20070320160338.GC5533@elf.ucw.cz>

On 3/20/07, Pavel Machek <pavel@ucw.cz> wrote:
> 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
that mouse is OK... Hmm, what happens if you load evbug and type while
watching syslog. Do you observe the same delays?

-- 
Dmitry

  reply	other threads:[~2007-03-20 16:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-20 15:33 Pavel Machek
2007-03-20 16:00 ` Andreas Mohr
2007-03-20 16:03   ` Pavel Machek
2007-03-20 16:09     ` Dmitry Torokhov [this message]
2007-03-20 16:31       ` Pavel Machek
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=d120d5000703200909v326ab6benc3fb85badc061018@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=andi@rhlx01.fht-esslingen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --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

all inboxes | Powered by JetHome®