Bug 43202 - atkbd serio0: Spurious NAK on isa0060/serio0. Some program might be trying access hardware directly.
Summary: atkbd serio0: Spurious NAK on isa0060/serio0. Some program might be trying ac...
Status: RESOLVED OBSOLETE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Input Devices (show other bugs)
Hardware: All Linux
: P1 low
Assignee: drivers_input-devices
URL: https://bugs.launchpad.net/bugs/526988
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-04 11:10 UTC by papukaija
Modified: 2013-11-02 22:10 UTC (History)
0 users

See Also:
Kernel Version: 3.4.0-030400rc5-generic-pae
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description papukaija 2012-05-04 11:10:57 UTC
My laptop is a Fujitu-Simens Amilo a 1645. This bug might be related to bug 8740 but the touchpad gets locked for maybe one second quite rarely (though the mouse issue was worse in older kernel). Apart from that minor mouse issue, there is no usability issues with this bug.

In dmesg I see:

[ 3403.034926] atkbd serio0: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0).
[ 3403.034937] atkbd serio0: Use 'setkeycodes 00 <keycode>' to make it known.
[ 3403.035444] atkbd_interrupt: 36 callbacks suppressed
[ 3403.035454] atkbd serio0: Spurious NAK on isa0060/serio0. Some program might be trying access hardware directly.
[ 3403.045009] psmouse serio2: TouchPad at isa0060/serio2/input0 lost sync at byte 4
[ 3403.047994] psmouse serio2: TouchPad at isa0060/serio2/input0 lost sync at byte 1
[ 3403.063930] psmouse serio2: TouchPad at isa0060/serio2/input0 - driver resynced.

The above error is the first occurrence in dmesg so this doesn't occur very frequently.

The output of lspci -vvnn is at https://launchpadlibrarian.net/48266440/Lspci.txt and other technical information can be found from https://bugs.launchpad.net/bugs/526988

Other related bugs:
https://bugzilla.kernel.org/show_bug.cgi?id=9147
https://bugzilla.kernel.org/show_bug.cgi?id=12193
Comment 1 papukaija 2013-11-02 22:10:21 UTC
I can no longer reproduce this bug on Ubuntu Precise (12.04) with Kernel 	3.8.13.11., though my testing was not very comprehensive. I'll do more testing when I have access to the laptop for next time but meanwhile, I think it is safe to close this report. Thanks.

Note You need to log in before you can comment on or make changes to this bug.