| |||||||||||||
|
| |||||||||||||
Con Kolivas returns with a new schedulerCon Kolivas returns with a new schedulerPosted Sep 3, 2009 13:15 UTC (Thu) by nix (subscriber, #2304)In reply to: Con Kolivas returns with a new scheduler by charris Parent article: Con Kolivas returns with a new scheduler
It's certainly not the bluetooth driver or X, because I see this on the console of a one-die four-core Nehalem (Core i7) with no X running at all and a PS/2 keyboard. It's lightly loaded by these standards (load average 8.1, which as it's hyperthreaded is pretty much equivalent to 'everything loaded but not much'), and surely isn't swapping (12Gb RAM, 6Gb *free*, not even used for cache). Yet I see three-second pauses in keyboard activity.
I'll turn on latencytop and see what it says, but the pauses are fairly rare so it might be interesting to interpret.
(Log in to post comments)
Con Kolivas returns with a new scheduler Posted Sep 3, 2009 13:39 UTC (Thu) by jzbiciak (✭ supporter ✭, #5246) [Link]
I've only gotten multi-second pauses like that when I had a hard drive going bad, or I was swapping rather furiously.
With that much RAM, I wonder if VM housekeeping itself could cause such lags. 12Gb would have 3 million 4K pages. If you are running at 3GHz and did something that averaged 3000 cycles/page across all 3 million pages, that's 3 seconds.
Con Kolivas returns with a new scheduler Posted Sep 3, 2009 17:31 UTC (Thu) by charris (subscriber, #13263) [Link]
I also see "stuck" keys where a letter will repeat until the buffer is full. I see this on various hardware with various keyboards, so it isn't an actual stuck key. Do you see that also?
Con Kolivas returns with a new scheduler Posted Sep 3, 2009 18:14 UTC (Thu) by jzbiciak (✭ supporter ✭, #5246) [Link]
That sounds more like a dropped event somewhere such as dropped interrupt or the like. I haven't experienced that on any Linux box so far.
Stuck keys. Posted Sep 4, 2009 2:47 UTC (Fri) by ncm (subscriber, #165) [Link]
I've seen on 2.6.29. Unplugging and re-plugging the (USB) keyboard didn't fix it. Only switching to console and back did it. I was inclined to blame the new X input system. It hasn't happened since I upgraded X and also went to 2.6.30, so who knows?
|
|
||||||||||||