Keyboard Stuttering
Quoted 5 lines
I'm experiencing some severe keyboard stuttering on my laptop. The problem is particularly bad in X, and I believe it also occurs at the console, though I'm having a difficult time verifying that. The problem shows up as repeated characters (not regular key-repeat-related), and sometimes dropped key presses.
(I'm not subscribed to the list, CC: to me if needed)
Same problem here. Intel Core 2 Duo with 2.6.19-rc1 x86_64 SMP. Happens on 2.6.17 too. I use 'noapic' as a workaround but that disables one of the CPU core of course.
I cannot reproduce the problem within the console nor gdm. Only on the X desktop.
dmesg and dmidecode outputs are available at:
http://zapek.com/misc/9400_dmesg
http://zapek.com/misc/9400_dmidecode
This is a Dell Inspiron 9400.
Signature · 1 line
Dave - http://zapek.com/
Quoted 4 lines · David Gerber
Quoted 1 line
I'm experiencing some severe keyboard stuttering on my laptop. The problem is particularly bad in X, and I believe it also occurs at the console, though I'm having a difficult time verifying that. The problem shows up as repeated characters (not regular key-repeat-related), and sometimes dropped key presses.
(I'm not subscribed to the list, CC: to me if needed)
Quoted 9 lines
Same problem here. Intel Core 2 Duo with 2.6.19-rc1
x86_64SMP. Happens on 2.6.17 too. I use 'noapic' as a workaround but that disables one of the CPU core of course.I cannot reproduce the problem within the console nor gdm. Only on the X desktop.
dmesg and dmidecode outputs are available at:
http://zapek.com/misc/9400_dmesg
http://zapek.com/misc/9400_dmidecode
This is a Dell Inspiron 9400.
The Dell Inspiron 9400 and Inspiron E1705 are pretty much the same laptop. I'm glad to hear it's not just my keyboard or anything like that.
It sounds like there are several others who are experiencing the same or related issues.
Is there a way to change the interrupt trigger for the keyboard (the other devices seem to work just fine)? Is there a way to force i8042 to XT-PIC on interrupt 1, to see whether it's related to the interrupt trigger, or something else that just looks similar? Any other ideas for debugging or fixing?
I'd really love not to have to do the noapic or nolapic workaround...
Frank
Quoted 6 lines · David Gerber
Quoted 5 lines
I'm experiencing some severe keyboard stuttering on my laptop. The problem is particularly bad in X, and I believe it also occurs at the console, though I'm having a difficult time verifying that. The problem shows up as repeated characters (not regular key-repeat-related), and sometimes dropped key presses.
Quoted 9 lines
(I'm not subscribed to the list, CC: to me if needed)
Same problem here. Intel Core 2 Duo with 2.6.19-rc1
x86_64SMP. Happens on 2.6.17 too. I use 'noapic' as a workaround but that disables one of the CPU core of course.I cannot reproduce the problem within the console nor gdm. Only on the X desktop.
John,
It looks like the only clocksource available on David's box is "jiffies" although the processor shows that it supporst tsc and PM timer is enabled and I think that this is what causes keyboard stuttering in X. See http://bugzilla.kernel.org/show_bug.cgi?id=7291.
I believe clocksources is your turf, could you please take a look at this.
Thanks!
Signature · 1 line
Dmitry
Quoted 17 lines · Dmitry Torokhov
Quoted 6 lines · David Gerber
Quoted 5 lines
I'm experiencing some severe keyboard stuttering on my laptop. The problem is particularly bad in X, and I believe it also occurs at the console, though I'm having a difficult time verifying that. The problem shows up as repeated characters (not regular key-repeat-related), and sometimes dropped key presses.
Quoted 9 lines
(I'm not subscribed to the list, CC: to me if needed)
Same problem here. Intel Core 2 Duo with 2.6.19-rc1
x86_64SMP. Happens on 2.6.17 too. I use 'noapic' as a workaround but that disables one of the CPU core of course.I cannot reproduce the problem within the console nor gdm. Only on the X desktop.
Quoted 8 lines
John,
It looks like the only clocksource available on David's box is "jiffies" although the processor shows that it supporst tsc and PM timer is enabled and I think that this is what causes keyboard stuttering in X. See http://bugzilla.kernel.org/show_bug.cgi?id=7291.
I believe clocksources is your turf, could you please take a look at this.
Sure thing. I followed up in the bug, but I don't think the clocksource code is involved. x86_64 hasn't converted to GENERIC_TIME, so jiffies is what we use to increment xtime, but the TSC, ACPI PM, or HPET is used for gettimeofday, etc.
I suspect C3 idling is the culprit, since noapic works around the issue.
thanks
-john
Quoted 18 lines · john stultz
Quoted 8 lines · Dmitry Torokhov
Quoted 7 lines
Same problem here. Intel Core 2 Duo with 2.6.19-rc1
x86_64SMP. Happens on 2.6.17 too. I use 'noapic' as a workaround but that disables one of the CPU core of course.I cannot reproduce the problem within the console nor gdm. Only on the X desktop.
Quoted 8 lines
John,
It looks like the only clocksource available on David's box is "jiffies" although the processor shows that it supporst tsc and PM timer is enabled and I think that this is what causes keyboard stuttering in X. See http://bugzilla.kernel.org/show_bug.cgi?id=7291.
I believe clocksources is your turf, could you please take a look at this.
Quoted 6 lines
Sure thing. I followed up in the bug, but I don't think the clocksource code is involved.
x86_64hasn't converted toGENERIC_TIME, so jiffies is what we use to increment xtime, but the TSC, ACPI PM, or HPET is used for gettimeofday, etc.I suspect C3 idling is the culprit, since noapic works around the issue.
Wait, does this mean that Intel's x86-64 implementation has the same buggy TSC as AMD's?
Lee
Quoted 22 lines · Lee Revell
Quoted 21 lines · john stultz
Quoted 8 lines · Dmitry Torokhov
Quoted 7 lines
Same problem here. Intel Core 2 Duo with 2.6.19-rc1
x86_64SMP. Happens on 2.6.17 too. I use 'noapic' as a workaround but that disables one of the CPU core of course.I cannot reproduce the problem within the console nor gdm. Only on the X desktop.
Quoted 6 lines
It looks like the only clocksource available on David's box is "jiffies" although the processor shows that it supporst tsc and PM timer is enabled and I think that this is what causes keyboard stuttering in X. See http://bugzilla.kernel.org/show_bug.cgi?id=7291.
I believe clocksources is your turf, could you please take a look at this.Sure thing. I followed up in the bug, but I don't think the clocksource code is involved.
x86_64hasn't converted toGENERIC_TIME, so jiffies is what we use to increment xtime, but the TSC, ACPI PM, or HPET is used for gettimeofday, etc.
Quoted 4 lines
Quoted 1 line
I suspect C3 idling is the culprit, since noapic works around the issue.
Wait, does this mean that Intel's x86-64 implementation has the same buggy TSC as AMD's?
Not the same issue, no.. but the TSCs do halt in lower powersaving modes, which can cause similar results. The new TSC clocksource code on i386 will disqualify itself if those lower powerstates are entered, so it should auto detect and fall back. On x86_64, this logic apparently is sill needed.
thanks
-john
Quoted 25 lines · john stultz
Quoted 24 lines · Lee Revell
Quoted 22 lines · john stultz
Quoted 8 lines · Dmitry Torokhov
Quoted 7 lines
Same problem here. Intel Core 2 Duo with 2.6.19-rc1
x86_64SMP. Happens on 2.6.17 too. I use 'noapic' as a workaround but that disables one of the CPU core of course.I cannot reproduce the problem within the console nor gdm. Only on the X desktop.
Quoted 6 lines
It looks like the only clocksource available on David's box is "jiffies" although the processor shows that it supporst tsc and PM timer is enabled and I think that this is what causes keyboard stuttering in X. See http://bugzilla.kernel.org/show_bug.cgi?id=7291.
I believe clocksources is your turf, could you please take a look at this.Sure thing. I followed up in the bug, but I don't think the clocksource code is involved.
x86_64hasn't converted toGENERIC_TIME, so jiffies is what we use to increment xtime, but the TSC, ACPI PM, or HPET is used for gettimeofday, etc.I suspect C3 idling is the culprit, since noapic works around the issue.
Quoted 8 lines
Quoted 2 lines
Wait, does this mean that Intel's x86-64 implementation has the same buggy TSC as AMD's?
Not the same issue, no.. but the TSCs do halt in lower powersaving modes, which can cause similar results. The new TSC clocksource code on i386 will disqualify itself if those lower powerstates are entered, so it should auto detect and fall back. On
x86_64, this logic apparently is sill needed.
x86-64 has code to not use TSC when there is C3. And special case code for some big boxes which don't sync the TSC fully.
AFAIK the logic is correct.
There were a few failures, but they were either totally broken BIOS or overclocking (some ways of overclocking seem to break the TSC synchronization on dual die Intel dual core CPUs)
Overclocking is not supported (and those people who want it can use notsc) and the broken BIOS cases were all fixed with a BIOS update
-Andi