On 20-Feb-01 AndriusD@labas.com wrote:
one day I found my suse box console filled with messy characters and not responding. I had to reboot it switching it off/on what I found in my logs where repeated messages like this: .......................... kernel: keyboard: unrecognized scancode (6b) - ignored kernel: keyboard: unrecognized scancode (65) - ignored last message repeated 2 times keyboard: unrecognized scancode (64) - ignored kernel: keyboard: unrecognized scancode (6b) - ignored last message repeated 4 times kernel: keyboard: unrecognized scancode (65) - ignored ................................ kernel: keyboard: Too many NACKs -- noisy kbd cable? kernel: keyboard: Too many NACKs -- noisy kbd cable? ...............................
what could be the cause of this? and is there something to worry about?
I noticed these errors on two occasions. First, when I used an ps/2 adapter for an old sub-d AT keyboard, and secondly at home, when one of my cats slept on top of my keyboard :-) On the other hand it seems doubtful wether the keyboard hardware itself is responsible for these errors. I heard from people with machines *without* any keyboard experiencing this error, so maybe there's some bug/conflict in /usr/src/linux/drivers/char/pc_keyb.c, where I found this error message in the linux source tree. FYI NACK means "not acknowledged", the keyboard controller cannot talk to/with the chipset on the motherboard. This error (and the resulting problems) are quite messy but are no signs of an attack, except if you suspect some small furry animals resting on your keys ;-)
thank you, _________ andriusd@labas.com
---
Boris Lorenz