Comment 48 for bug 984265

Revision history for this message
Jeff Lane  (bladernr) wrote : Re: Keyboard becomes all but unusable after Precise runs for so long

Ok, so with 3.3.8, I got the keycode messages, but only in a couple instances:

syslog.1:Aug 2 16:01:00 klaatu kernel: [15038.967755] atkbd serio0: Use 'setkeycodes e060 <keycode>' to make it known.
syslog.1:Aug 2 16:02:20 klaatu kernel: [15119.091221] atkbd serio0: Use 'setkeycodes e060 <keycode>' to make it known.
syslog.1:Aug 2 16:02:38 klaatu kernel: [15136.781661] atkbd serio0: Use 'setkeycodes e060 <keycode>' to make it known.
syslog.1:Aug 2 16:05:59 klaatu kernel: [15337.380699] atkbd serio0: Use 'setkeycodes e060 <keycode>' to make it known.
syslog.1:Aug 2 16:08:33 klaatu kernel: [15491.449191] atkbd serio0: Use 'setkeycodes e060 <keycode>' to make it known.
syslog.1:Aug 2 17:00:00 klaatu kernel: [18574.882233] atkbd serio0: Use 'setkeycodes e060 <keycode>' to make it known.
syslog.1:Aug 2 17:02:09 klaatu kernel: [18703.813750] atkbd serio0: Use 'setkeycodes e060 <keycode>' to make it known.
syslog.1:Aug 2 17:06:22 klaatu kernel: [18956.636771] atkbd serio0: Use 'setkeycodes e060 <keycode>' to make it known.
syslog.1:Aug 2 17:43:41 klaatu kernel: [21193.819427] atkbd serio0: Use 'setkeycodes e060 <keycode>' to make it known.

Those were all I got after booting up 3.3.8 and running that for a while. So not fixed, but much better. I did still experience the wonky touchpad thing, so I still had to rmmod psmouse, unlike with 3.4x or 3.5x kernels.

So what's next to test?