Andy Green wrote on Mon, 21 Aug 2006 15:35:21 +0100:
This disease seems to be ongoing for some people. On the box of mine that was affected, a later kernel fixed it.
So you are running an FC kernel on CentOS or RHEL? Or running FC anyway?
Thanks for the link, Andy. Didn't sound that similar in the beginning. I tried to repro those network transfer issues and couldn't. But the keyboard repeat stuff reported later sounds "promising". Seems there were really two problems mixed in one report.
If you look in your dmesg you might see complaints about missing interrupts.
None. After reading the bug report I added report_lost_ticks to grub.conf and rebooted, but still no errors in dmesg. Is my understanding correct that report_lost_ticks enables reporting in dmesg or logs or is it something else? Hm, according to Google it's exactly for this. Do I need to add something, f.i. "report_lost_ticks=1" or so?
Hm, a few minutes later. The problem wasn't very apparent over the last hours. After an ntpdate it differed about 2 seconds within a few seconds and basically stayed that way, no increase or at least no noticable increase. Maybe it jumps from time to time to "achieve" a greater skew. However, now after rebooting with report_lost_ticks there's almost no difference. Hm. And, wow, I changed to runlevel 5 and the keyboard repeat problem is gone! I hope that really cures it, great!
And another few minutes later. Time is still okay, but maybe it's too early for that. But the keyboard repeat problem is back. Not as bad as before, though. Weird.
Kai