Comment 23 for bug 227359
Revision history for this message
| Ariel Faigon (ariel.faigon) wrote Re: [Bug 227359] Re: suddenly keyboard event recognition gets really slow after multiple suspend/resumes | #23 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Hi Tommy
Answering your Qs:
Q) Does it mean that I have 288 chars typed?
A) Yes. 'wc' is word-count, by default it prints 3 numbers:
number of lines
number of words
number of chars
The last one is 288 - number of chars.
Q) Isn't it too low number?
A) Not if auto-repeat generated 288 chars
The main question is how _long_ it took to print these 288
chars. If you held the 'c' key down for 6 seconds, it means you
have 48-chars per second generated. This is pretty fast and means
you're probably not losing chars. I can get a max of about 50cps
in autorepeat, so this is healthy.
If you get lags, I would try to understand better what's causing
the extra load: start with 'top' (anything highly CPU intensive?
suspicious?) then look at the logs /var/log/* during the exact
time of the lag (every log message has an exact timestamp).
Any errors?
etc.
HTH
On Sun, Aug 15, 2010 at 09:31:36AM -0000, Tommy_CZ wrote:
> Ariel Faigon:
>
> Hi, I tried it as you told, I got this:
> tom@tom-laptop:~$ cat - | wc
> ccccccccccccccc
>
> Does it mean that I have 288 chars typed? Isn't it too low number? I get
> lags when typing in konsole, other parts of system looks good by the
> moment.
>
> It is with kernel 2.6.32-
>
> I'll try kernel 2.6.32-24 as it is probably latest distributed by
> updates.
>
> --
> suddenly keyboard event recognition gets really slow after multiple suspend/resumes
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
--
Peace, Ariel