atkbd.c: Spurious NAK on isa0060/serio0. Some program might be trying access hardware directly.

[papukaija]

I was asked in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/414808/comments/6 to to open a new bug for this problem due to different hardware. My laptop is Fujitu-Simens Amilo a 1645. This bug might be related to bug 34501.

In dmesg I see:

localhost kernel: [ 3066.166692] atkbd.c: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0).
May 11 12:25:34 localhost kernel: [ 3066.166701] atkbd.c: Use 'setkeycodes 00 <keycode>' to make it known.
May 11 12:25:34 localhost kernel: [ 3066.166736] atkbd.c: Spurious NAK on isa0060/serio0. Some program might be trying access hardware directly.
May 11 12:25:34 localhost kernel: [ 3066.168921] psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 4
May 11 12:25:34 localhost kernel: [ 3066.170697] psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 1
May 11 12:25:34 localhost kernel: [ 3066.184470] psmouse.c: TouchPad at isa0060/serio2/input0 - driver resynched.
May 11 12:35:27 localhost kernel: [ 3659.145383] atkbd.c: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0).
May 11 12:35:27 localhost kernel: [ 3659.145387] atkbd.c: Use 'setkeycodes 00 <keycode>' to make it known.
May 11 12:35:27 localhost kernel: [ 3659.149585] atkbd.c: Spurious NAK on isa0060/serio0. Some program might be trying access hardware directly.
May 11 12:35:27 localhost kernel: [ 3659.149605] psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 1
May 11 12:35:27 localhost kernel: [ 3659.151333] psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 1
May 11 12:35:27 localhost kernel: [ 3659.153339] psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 1
May 11 12:35:27 localhost kernel: [ 3659.155888] psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 1
May 11 12:35:27 localhost kernel: [ 3659.158584] psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 1
May 11 12:35:27 localhost kernel: [ 3659.158588] psmouse.c: issuing reconnect request

ProblemType: Bug

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: SI7012 [SiS SI7012], device 0: Intel ICH [SiS SI7012]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: username 1239 F.... pulseaudio
CRDA: Error: [Errno 2] Tiedostoa tai hakemistoa ei ole
Card0.Amixer.info:
 Card hw:0 'SI7012'/'SiS SI7012 with VIA1612A at irq 18'
   Mixer name : 'VIA Technologies VIA1612A'
   Components : 'AC97a:56494161'
   Controls : 37
   Simple ctrls : 23
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=6e4d26df-835c-41cb-8411-64c44da66af5
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Lsusb:
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: FUJITSU SIEMENS Amilo A1645
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
 Socket 1:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=adefe281-edd8-4e96-a81c-eb7076c03ad6 ro quiet splash
ProcEnviron:
 LANG=fi_FI.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Regression: No
RelatedPackageVersions: linux-firmware 1.34
Reproducible: Yes
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: lucid needs-upstream-testing
Uname: Linux 2.6.32-22-generic i686
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare tape video
dmi.bios.date: 06/15/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.02C
dmi.board.name: 255KI / 259KI Series
dmi.board.vendor: Uniwill
dmi.board.version: 0.01
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.02C:bd06/15/2005:svnFUJITSUSIEMENS:pnAmiloA1645:pvr0.01:rvnUniwill:rn255KI/259KISeries:rvr0.01:cvnFUJITSUSIEMENS:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: Amilo A1645
dmi.product.version: 0.01
dmi.sys.vendor: FUJITSU SIEMENS

[papukaija (papukaija)]

@Jeremy: Can you confirm this bug?

[Jeremy Foshee (jeremyfoshee)]

Hi papukaija,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 526988

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[papukaija (papukaija)]

This bug seems to be fixed in Lucid.

[papukaija (papukaija)]

Unfortunately I spoke too soon.

[papukaija (papukaija)]

apport information

[papukaija (papukaija)]

apport information

[papukaija (papukaija)]

apport information

[papukaija (papukaija)]

apport information

[papukaija (papukaija)]

apport information

[papukaija (papukaija)]

apport information

[papukaija (papukaija)]

apport information

[papukaija (papukaija)]

apport information

[papukaija (papukaija)]

apport information

[papukaija (papukaija)]

apport information

[papukaija (papukaija)]

apport information

[papukaija (papukaija)]

apport information

[papukaija (papukaija)]

apport information

[papukaija (papukaija)]

apport information

[papukaija (papukaija)]

apport information

[papukaija (papukaija)]

apport information

[papukaija (papukaija)]

Here are the the results with the mainline kernels:

Mainline kernel | Result
-------------------------------------
2.6.32.11-lucid | not fixed
2.6.34-lucid | not fixed
2.6.35-rc1-lucid | not fixed

[papukaija (papukaija)]

The same results in one file.

[papukaija (papukaija)]

Maverick and Natty update: The mouse is more stable now but I still get the error message to syslog.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc5-precise/

[papukaija (papukaija)]

 Bad news with mainline kernel 3.4.0-030400rc5-generic-pae #201205011817 SMP Tue May 1 22:31:34 UTC 2012 i686 athlon i386 GNU/Linux:

[ 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.

[papukaija (papukaija)]

The upstream bug https://bugzilla.kernel.org/show_bug.cgi?id=9147 is about the Unknown key pressed error (ie. the first three lines above). I also found https://bugzilla.kernel.org/show_bug.cgi?id=12193 which is very old and occurs much more often than on my system. I'll forward this bug to upstream in a second.

[papukaija (papukaija)]

This bug is now sent to upstream: https://bugzilla.kernel.org/show_bug.cgi?id=43202

[penalvch (penalvch)]

papukaija, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[papukaija (papukaija)]

Sorry for the delay but I don't have full time access to this laptop. I was unable to reproduce the issue on fully updated Precise, 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.