Re: Bad autorepeat problems in 2.5.75

Re: Bad autorepeat problems in 2.5.75

[Vojtech Pavlik]

On Tue, Jul 15, 2003 at 12:22:51AM +0200, Pavel Machek wrote:

> Hi!
> 
> I have bad problems with autorepeat. When switching consoles with
> alt-left / alt-right it sometimes skips wrong number of consoles, and
> sometimes it just keeps repeating even through I already released a
> key.
> 
> Syslog complains:
> 
> Jul 15 00:15:52 amd kernel: atkbd.c: Unknown key (set 2, scancode
> 0x1cb, on isa0060/serio0) pressed.
> Jul 15 00:16:21 amd kernel: atkbd.c: Unknown key (set 2, scancode
> 0x1cb, on isa0060/serio0) pressed.
> Jul 15 00:19:02 amd kernel: atkbd.c: Unknown key (set 2, scancode
> 0x1cd, on isa0060/serio0) pressed.
> Jul 15 00:20:04 amd kernel: atkbd.c: Unknown key (set 2, scancode
> 0x1cd, on isa0060/serio0) pressed.
> 
> Its vesafb -> switching consoles is not exactly fast, maybe that has
> some role?

Probably keyboard interrupts get lost. Bad. Can you track with DEBUG
enabled in i8042.c?

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

Re: Bad autorepeat problems in 2.5.75

[Faik Uygur]

Vojtech Pavlik <vojtech@suse.cz> wrote:
> On Tue, Jul 15, 2003 at 12:22:51AM +0200, Pavel Machek wrote:
> 
> > Hi!
> > 
> > I have bad problems with autorepeat. When switching consoles with
> > alt-left / alt-right it sometimes skips wrong number of consoles, and
> > sometimes it just keeps repeating even through I already released a
> > key.
> > 
> > Syslog complains:
> > 
> > Jul 15 00:15:52 amd kernel: atkbd.c: Unknown key (set 2, scancode
> > 0x1cb, on isa0060/serio0) pressed.
> > Jul 15 00:16:21 amd kernel: atkbd.c: Unknown key (set 2, scancode
> > 0x1cb, on isa0060/serio0) pressed.
> > Jul 15 00:19:02 amd kernel: atkbd.c: Unknown key (set 2, scancode
> > 0x1cd, on isa0060/serio0) pressed.
> > Jul 15 00:20:04 amd kernel: atkbd.c: Unknown key (set 2, scancode
> > 0x1cd, on isa0060/serio0) pressed.
> > 
> > Its vesafb -> switching consoles is not exactly fast, maybe that has
> > some role?
> 
> Probably keyboard interrupts get lost. Bad. Can you track with DEBUG
> enabled in i8042.c?

Hi,

Related or same problem here. This is Toshiba 1410-902.

Here is some debug output:

drivers/input/serio/i8042.c: 25 <- i8042 (interrupt, kbd, 1) [1154471]
drivers/input/serio/i8042.c: 24 <- i8042 (interrupt, kbd, 1) [1154532]
drivers/input/serio/i8042.c: a5 <- i8042 (interrupt, kbd, 1) [1154538]
drivers/input/serio/i8042.c: a4 <- i8042 (interrupt, kbd, 1) [1154664]
drivers/input/serio/i8042.c: a4 <- i8042 (interrupt, kbd, 1) [1154672]
atkbd.c: Unknown key (set 2, scancode 0xa4, on isa0060/serio0) pressed.
drivers/input/serio/i8042.c: 25 <- i8042 (interrupt, kbd, 1) [1154683]
drivers/input/serio/i8042.c: 24 <- i8042 (interrupt, kbd, 1) [1154743]
drivers/input/serio/i8042.c: a5 <- i8042 (interrupt, kbd, 1) [1154769]
drivers/input/serio/i8042.c: a4 <- i8042 (interrupt, kbd, 1) [1154873]
drivers/input/serio/i8042.c: a4 <- i8042 (interrupt, kbd, 1) [1154881]
atkbd.c: Unknown key (set 2, scancode 0xa4, on isa0060/serio0) pressed.
drivers/input/serio/i8042.c: 25 <- i8042 (interrupt, kbd, 1) [1154892]
drivers/input/serio/i8042.c: 24 <- i8042 (interrupt, kbd, 1) [1154971]
drivers/input/serio/i8042.c: a5 <- i8042 (interrupt, kbd, 1) [1154995]
drivers/input/serio/i8042.c: a4 <- i8042 (interrupt, kbd, 1) [1155099]
drivers/input/serio/i8042.c: a4 <- i8042 (interrupt, kbd, 1) [1155109]
atkbd.c: Unknown key (set 2, scancode 0xa4, on isa0060/serio0) pressed.
drivers/input/serio/i8042.c: 25 <- i8042 (interrupt, kbd, 1) [1155118]

	Faik