Re: 2.6.23.1-rt5 rtc lost interrupt

[Dragan Noveski <perodog@gmx.net>]

Steven Rostedt wrote:
> --
> When I'm asked what language is my mother tongue,
> I simply answer "C".
>
> On Wed, 31 Oct 2007, Dragan Noveski wrote:
>
>   
>> hallo list, yesterday strange thing happened here.
>> i am running 2.6.23.1-rt5, and actually it is running good, but
>> yesterday partially my keyboard stopped working. usually if i press any
>> key (inside of xterm) and do not release, but keep pressed, the
>> letter/sign will be printed all the time again and again as long as i
>> release the key.
>> something like:
>>
>> aaaaaaaaaaaaaaaaaaaaa
>>     
>
> What X drivers are you running (hopefully not nVidia or some other
> proprietary module).
>   
no it is perhaps one of these both:

00:02.0 VGA compatible controller: Intel Corporation 82852/855GM 
Integrated Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated 
Graphics Device (rev 02)

...but nothing proprietary here.

>   
>> but yesterday, if i was holding the key, the letter got displayed on the
>> screen just one time.
>> if i released and pressed again, one more time.....
>> so i was not able to press only one time a key and hold to get sth like
>> these:
>>
>> ........................
>>
>> than in /var/log/system i found this lines:
>>
>>
>> Oct 30 21:22:37 murija2 kernel: rtc: lost 8 interrupts
>> Oct 30 21:22:50 murija2 kernel: rtc: lost 4 interrupts
>> Oct 30 21:22:50 murija2 kernel: rtc: lost 20 interrupts
>>     
>
> Unfortunately, this gives me no clue to what went wrong. Perhaps, you have
> a high priority process running somewhere that is keeping things from
> running.
>   

ok, but this gives me an idea, because i was just backtracing 'aqualung' 
and 'bristol synth emulator' and letting them crash again and again.
but i was not thinking that this could be causing the issue.
> What type of system is this? SMP?
>   
no, ibm-thinkpad-r50e with celeronM
>   
>> this also appeared in dmesg.
>>
>> is this explained so that someone is able to understand?
>> does any one has an idea what went wrong here?
>>
>> after a reboot the keyboard was working as usually again and the issue
>> did not happened again since them.
>>
>> hope to get some suggestions/answers?!
>>
>>     
>
> I can't figure out much with the current info.
>
> -- Steve
>
>   
i was expecting that the info i had is not info enough!

anyway, it did not appeared again, so i will not be scared too much now, 
if it comes again, you ll hear from me.

cheers,
doc