Frans & Pavel;
I too saw the random key repeats you are seeing with 2.6.25-rc1 -
however, I saw it (or something very much like the problem you are
reporting - I am not smart enough to determine if the root cause is the
same) with 2.6.25-git15
A number of corrispondents on this list offered troubleshooting
suggestions, most of which centered arund the high performance timer.
If you too feel that the issue you are seeing might be releated to the
one I saw the following clips from the email I received might be of
interest to you.
>From Jiri Kosina:
It could be some timing problem. Does this happen also in console, or
only when running X?
Could you please try to
- boot with 'nohpet' kernel parameter
- taskset -p 0x00000002 <pid_of_Xserver> if this is a multi-CPU/core
machine and you are experiencing the problems only in X
>From Thomas Gleixner:
Can you please apply the following patch, boot w/o nohpet and provide
the dmesg output ?
diff --git a/arch/x86/kernel/hpet.c b/arch/x86/kernel/hpet.c
index 429d084..4e98241 100644
--- a/arch/x86/kernel/hpet.c
+++ b/arch/x86/kernel/hpet.c
@@ -375,8 +375,10 @@ int __init hpet_enable(void)
{
unsigned long id;
- if (!is_hpet_capable())
+ if (!is_hpet_capable()) {
+ printk(KERN_INFO "HPET not available\n");
return 0;
+ }
hpet_set_mapping();
@@ -392,6 +394,7 @@ int __init hpet_enable(void)
* information and the number of channels
*/
id = hpet_readl(HPET_ID);
+ printk(KERN_INFO "HPET available. ID = %lx\n", id);
#ifdef CONFIG_HPET_EMULATE_RTC
/*
@@ -412,6 +415,7 @@ int __init hpet_enable(void)
return 0;
out_nohpet:
+ printk(KERN_INFO "HPET disabled\n");
hpet_clear_mapping();
boot_hpet_disable = 1;
return 0;
I have been trying to narrow it down using bisect (my first attempt at
using this utility) with mixed results - just when I think I understand
where the problem was introduced I hit a brick wall.
However, you comment on system loading may have turned the old light
bulb on - that is one area where I have not been consistant.
Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
