Function keys stop functioning (atkbd.c: Unknown key pressed)

[Foobar]

Initially I can use the function keys just fine, but after some time, e.g. a few hours. All of my function keys (F1-F12) fail. After a reboot everything works again. It is a Logitech keyboard. The model name on the bottom of the keyboard says:

Y-SAE71
SK-2930

The dmesg log adds an

[ 9931.839242] atkbd.c: Unknown key released (translated set 2, code 0xc3 on isa0060/serio0).
[ 9931.839244] atkbd.c: Use 'setkeycodes e043 <keycode>' to make it known.

entry every time a function key is pressed.

Although, this is a custom Ubuntu kernel, it also happened with a released Ubuntu kernel.

[Foobar (ron-gamr7)]

Linux foobox 2.6.29-rc7-custom #1 SMP Wed Mar 4 14:49:18 CET 2009 i686 GNU/Linux

[Foobar (ron-gamr7)]

Using Linux one 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 16:20:31 UTC 2009 i686 GNU/Linux the same happens.

[Jeremy Foshee (jeremyfoshee)]

Hi Foobar,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . If the issue remains, please 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 392489

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

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

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