Skip to contentSkip to conversation

strange keyboard lag after suspend testing

DISCUSSION Pavel Machek 5 participants 9 messages Mar 20, 2007 – Mar 21, 2007

lore
Share & tools
lore
#0 lore raw

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?
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#1 lore raw

Hi,

Quoted 7 lines · Pavel Machek

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?

Andreas Mohr

#2 lore raw

Hi!

Quoted 10 lines
Quoted 5 lines

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...
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#3 lore raw
Quoted 8 lines · Pavel Machek

Hi!

Quoted 6 lines
Quoted 5 lines

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?

Quoted 7 lines
Quoted 4 lines

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?

Signature · 1 line
Dmitry
#4 lore raw

Hi!

Quoted 11 lines
Quoted 11 lines
Quoted 10 lines
Quoted 5 lines

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?

Quoted 6 lines
Quoted 2 lines

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.

Quoted 2 lines

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

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#5 lore raw

Hi!

Quoted 23 lines
Quoted 11 lines
Quoted 11 lines
Quoted 10 lines
Quoted 5 lines

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?

Quoted 6 lines
Quoted 2 lines

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.

Quoted 2 lines

that mouse is OK... Hmm, what happens if you load evbug and type while watching syslog. Do you observe the same delays?

Quoted 7 lines

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:

It gets weirder: I killed some tasks and now: (on unloaded system running X, notice that top latency was ~1sec at 33:09).

root@amd:~# while true ; do echo -n . ; sleep .2; date; done
.Tue Mar 20 17:33:07 CET 2007
.Tue Mar 20 17:33:07 CET 2007
.Tue Mar 20 17:33:08 CET 2007
.Tue Mar 20 17:33:08 CET 2007
.Tue Mar 20 17:33:08 CET 2007
.Tue Mar 20 17:33:08 CET 2007
.Tue Mar 20 17:33:09 CET 2007
.Tue Mar 20 17:33:10 CET 2007
.Tue Mar 20 17:33:10 CET 2007
.Tue Mar 20 17:33:10 CET 2007
.Tue Mar 20 17:33:10 CET 2007
.Tue Mar 20 17:33:10 CET 2007
.Tue Mar 20 17:33:11 CET 2007
.Tue Mar 20 17:33:11 CET 2007
.Tue Mar 20 17:33:11 CET 2007
.Tue Mar 20 17:33:12 CET 2007
.Tue Mar 20 17:33:12 CET 2007

As soon as I load the cpu up with while1, machine starts to behave.

When I turn on bluetooth (USB), ACPI can no longer use C3, and machine starts to behave. Hmm?
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#6 lore raw
Quoted 55 lines · Pavel Machek

Hi!

Quoted 23 lines
Quoted 11 lines
Quoted 11 lines
Quoted 10 lines
Quoted 5 lines

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?

Quoted 6 lines
Quoted 2 lines

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.

Quoted 2 lines

that mouse is OK... Hmm, what happens if you load evbug and type while watching syslog. Do you observe the same delays?

Quoted 7 lines

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:

It gets weirder: I killed some tasks and now: (on unloaded system running X, notice that top latency was ~1sec at 33:09).

root@amd:~# while true ; do echo -n . ; sleep .2; date; done
.Tue Mar 20 17:33:07 CET 2007
.Tue Mar 20 17:33:07 CET 2007
.Tue Mar 20 17:33:08 CET 2007
.Tue Mar 20 17:33:08 CET 2007
.Tue Mar 20 17:33:08 CET 2007
.Tue Mar 20 17:33:08 CET 2007
.Tue Mar 20 17:33:09 CET 2007
.Tue Mar 20 17:33:10 CET 2007
.Tue Mar 20 17:33:10 CET 2007
.Tue Mar 20 17:33:10 CET 2007
.Tue Mar 20 17:33:10 CET 2007
.Tue Mar 20 17:33:10 CET 2007
.Tue Mar 20 17:33:11 CET 2007
.Tue Mar 20 17:33:11 CET 2007
.Tue Mar 20 17:33:11 CET 2007
.Tue Mar 20 17:33:12 CET 2007
.Tue Mar 20 17:33:12 CET 2007
Quoted 4 lines

As soon as I load the cpu up with while1, machine starts to behave.

When I turn on bluetooth (USB), ACPI can no longer use C3, and machine starts to behave. Hmm?

Smells like a cpufreq problem or something related.

Greetings,
Rafael

#7 lore raw
In reply to Pavel Machek

Adding Thomas Gleixner to CC

Pavel Machek <[email protected]> ha scritto:

Quoted 55 lines

Hi!

Quoted 23 lines
Quoted 11 lines
Quoted 11 lines
Quoted 10 lines
Quoted 5 lines

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?

Quoted 6 lines
Quoted 2 lines

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.

Quoted 2 lines

that mouse is OK... Hmm, what happens if you load evbug and type while watching syslog. Do you observe the same delays?

Quoted 7 lines

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:

It gets weirder: I killed some tasks and now: (on unloaded system running X, notice that top latency was ~1sec at 33:09).

root@amd:~# while true ; do echo -n . ; sleep .2; date; done
.Tue Mar 20 17:33:07 CET 2007
.Tue Mar 20 17:33:07 CET 2007
.Tue Mar 20 17:33:08 CET 2007
.Tue Mar 20 17:33:08 CET 2007
.Tue Mar 20 17:33:08 CET 2007
.Tue Mar 20 17:33:08 CET 2007
.Tue Mar 20 17:33:09 CET 2007
.Tue Mar 20 17:33:10 CET 2007
.Tue Mar 20 17:33:10 CET 2007
.Tue Mar 20 17:33:10 CET 2007
.Tue Mar 20 17:33:10 CET 2007
.Tue Mar 20 17:33:10 CET 2007
.Tue Mar 20 17:33:11 CET 2007
.Tue Mar 20 17:33:11 CET 2007
.Tue Mar 20 17:33:11 CET 2007
.Tue Mar 20 17:33:12 CET 2007
.Tue Mar 20 17:33:12 CET 2007
Quoted 4 lines

As soon as I load the cpu up with while1, machine starts to behave.

When I turn on bluetooth (USB), ACPI can no longer use C3, and machine starts to behave. Hmm?

When the CPU is in C3 the TSC and LAPIC (IIRC) are stopped, sounds like the problem is here. Maybe after resume kernel fails to fall back to a "safe" clocksource.

Luca

Signature · 3 lines
Inquietudine sintetica
Solo, davanti all'ignoto
Tienimi stretto a te
#8 lore raw

Hi!

Quoted 42 lines
Quoted 42 lines
Quoted 12 lines
Quoted 6 lines
Quoted 2 lines

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.

Quoted 2 lines

that mouse is OK... Hmm, what happens if you load evbug and type while watching syslog. Do you observe the same delays?

Quoted 7 lines

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:

It gets weirder: I killed some tasks and now: (on unloaded system running X, notice that top latency was ~1sec at 33:09).

root@amd:~# while true ; do echo -n . ; sleep .2; date; done
.Tue Mar 20 17:33:07 CET 2007
.Tue Mar 20 17:33:07 CET 2007
.Tue Mar 20 17:33:08 CET 2007
.Tue Mar 20 17:33:08 CET 2007
.Tue Mar 20 17:33:08 CET 2007
.Tue Mar 20 17:33:08 CET 2007
.Tue Mar 20 17:33:09 CET 2007
.Tue Mar 20 17:33:10 CET 2007
.Tue Mar 20 17:33:10 CET 2007
.Tue Mar 20 17:33:10 CET 2007
.Tue Mar 20 17:33:10 CET 2007
.Tue Mar 20 17:33:10 CET 2007
.Tue Mar 20 17:33:11 CET 2007
.Tue Mar 20 17:33:11 CET 2007
.Tue Mar 20 17:33:11 CET 2007
.Tue Mar 20 17:33:12 CET 2007
.Tue Mar 20 17:33:12 CET 2007
Quoted 8 lines
Quoted 4 lines

As soon as I load the cpu up with while1, machine starts to behave.

When I turn on bluetooth (USB), ACPI can no longer use C3, and machine starts to behave. Hmm?

When the CPU is in C3 the TSC and LAPIC (IIRC) are stopped, sounds like the problem is here. Maybe after resume kernel fails to fall back to a "safe" clocksource.

Notice that problem is _not_ easily reproducible :-(. One suspend is not enough to trigger it.

Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html