[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
port-sgimips/47639: O2 keyboard: After a period of light activity, keyboard scrambles
>Synopsis: O2 keyboard: After a period of light activity, keyboard
>Arrival-Date: Sun Mar 10 17:55:00 +0000 2013
NetBSD machine 6.0.1 NetBSD 6.0.1 (GENERIC32_IP3x) sgimips
mainbus0 (root): SGI-IP32 [SGI, a], 1 processor
cpu0 at mainbus0: MIPS R12000 CPU (0xe35) Rev. 3.5 with unknown FPC type
(0x900) Rev. 0.0
After a successful installation with correct keyboard and console function
(pleasantly fast and felt high quality), observed the keyboard becomes
Basic services running (NTP, SSH, Postfix, mdnsd). Quiescent system, recently
installed with 6.0.1. Not running X.
First observed running top(1) overnight on a quiet system.
Second observed logged into console shortly after boot ~6minutes.
Third observed after physically reconnecting keyboard while logged into console
On the Second occurrence, witnessed flash from CAPS NUM and SCROLL keyboard
lights. Was not interacting with the machine at that moment. Then observed
keyboard was corrupted - 'm' became capslock, 'q' became 'Y', other keys could
produce control key combinations, rendered as garbage in console display. Some
key presses repeat randomly.
Remote SSH into machine and observe system is otherwise functioning normally.
Killed processes attached to console session sh(1) and login(1) and observed
console return to login prompt. No change in symptoms.
No additional info in dmesg, no log in /var/log/messages.
Unknown how to reinitialize a keyboard. Reboot and keyboard working normally
again until next occurrence.
Physically reproduced after boot by unplugging and plugging in keyboard.
Observed same key-reassignment: "m" capslock, 'g' period 'o' numlock '9'
scrolllock. Some key reassignments weren't completely the same.
Don't suspect faulty keyboard PS/2 connector. Keyboard is US SGI O2 keyboard
062-0002-001 circa 1998. Keyboard functions normally in PROM (and in IRIX).
Repeating after obtaining console is inconsistent.
Physically disconnecting the keyboard PS/2 plug, wait a few seconds and then
reconnect seems to reliably cause fault.
Main Index |
Thread Index |