keyboard.c floods syslog

[Lemmit Kaplinski]

Binary package hint: linux-source-2.6.20

just a few lines from dmesg:
[14324.508000] keyboard.c: can't emulate rawmode for keycode 0
[14324.544000] keyboard.c: can't emulate rawmode for keycode 0
[14324.580000] keyboard.c: can't emulate rawmode for keycode 0
[14324.616000] keyboard.c: can't emulate rawmode for keycode 0
[14324.652000] keyboard.c: can't emulate rawmode for keycode 0

running 2.6.20-12-generic #2 SMP i686 on MacBook Core Duo 2 GHz.

this is rather annoying as I have to shut down syslog or it will generate huge files.

[Ben Collins (ben-collins)]

Do you have any odd keyboard like devices (IR remotes, etc) that might be generating this? I strongly suspect this is a bad keyboard. Can you test another one?

[Lemmit Kaplinski (lemmit)]

The MacBook has an IR interface, which I havent tried yet. Maybe this is to blame, but I have no idea how to test it. Suggestions welcome.

I am also attaching the output of `cat /proc/bus/input/devices` - maybe someone sees something suspicious there.

Another thing - I've had problems with the Num Lock key. Some time ago (2.6.20-9 I believe), it tended to get stuck (on the software side - couldn't turn it off) and only allow numeric entries using the Fn key. I had to do a restart every time. With 2.6.20-12 I haven't had this issue (yet :), but now I cannot turn Num Lock on at all. Maybe this is somehow connected to the syslog problem.

And another remark - the MacBook requires loading appletouch trackpad module _before_ the usbhid module. Maybe this messes something up?

[Lemmit Kaplinski (lemmit)]

As far as trying another keyboard is concerned - I can do that, but it would be rather difficult to disconnect the current one. This is a laptop after all. Can I switch it off somehow?

[Smurphy (smurphy-linux)]

Got a Mac-Mini 1.66GHz, 1GB Ram showing the same beheaviour.
Disconnected the actual keyboard (Logitech MX700 Keboard & Mouse) and connected another one. Didn't make a difference.
Even rebooting...
Linux deimos.solsys.org 2.6.20-12-generic #2 SMP Sun Mar 18 03:07:14 UTC 2007 i686 GNU/Linux

Note that a self compiled plain 2.6.20.3 doesn't have this beheaviour...
But I'll check. Have to reboot for this.

[Smurphy (smurphy-linux)]

Rebootet into 2.6.20.3 - and didn't have that beheaviour ...
So it seems a bug in 2.6.20-12-generic....
Confirmed.
Please note that I can't test with other keyboards - as I only have 2 ;)

[Smurphy (smurphy-linux)]

If there is anything specific I can do - let me know.
Can play around with the Mac mini (Without screwing the OS) to check what is going on.
But I need direction ... Long time I did some deep kernel debugging ...

[Smurphy (smurphy-linux)]

Seems that has been fixed with the latest kernel.
Running 2.6.20-12.20 here - and no more syslog flooding ...
Ah yes - this is the guy with the mac-mini ...
Thx folks :)

[Smurphy (smurphy-linux)]

Sorry folks...
I was too fast ...
It stopped flooding syslog - however /var/log/messages get's it all now ...
So - even with 2.6.20-12.20 we still have the flooding.

[Super Gab (go-supergab)]

I have the same problem running feisty (2.6.20-13-generic) on my black MacBook 1st generation and a custom MacBook french keymap by Bersace (http://bersace03.free.fr/pub/Linux/xkb-mac/fr).

I don't know if these are related though.

[Javier Cabezas (javier-cabezas)]

It seems that here <a href="http://lkml.org/lkml/2007/3/24/135">http://lkml.org/lkml/2007/3/24/135</a> it is the solution. I hope a fix is released before Feisty is launched by the end of this month.

[Leann Ogasawara (leannogasawara)]

This bug report was marked "Fix Committed" a while ago but there hasn't been any recent activity. Can you just verify this bug has been resolved and we'll go ahead and mark this bug report as "Fix Released". Thanks in advance.

[Super Gab (go-supergab)]

Le 11-02-2008 à 16:17, Leann Ogasawara a écrit :

> This bug report was marked "Fix Committed" a while ago but there
> hasn't
> been any recent activity. Can you just verify this bug has been
> resolved and we'll go ahead and mark this bug report as "Fix
> Released".
> Thanks in advance.
>
> --
> keyboard.c floods syslog
> https://bugs.launchpad.net/bugs/94160
> You received this bug notification because you are a direct subscriber
> of the bug.

Sorry I don't have any Linux system available for testing.

Good luck.

[Leann Ogasawara (leannogasawara)]

It looks like the above lkml patch was applied to the Gutsy kernel:

commit 9e35d20663344b38339ffb6127ba08285f3397a9
Author: Dmitry Torokhov <email address hidden>
Date: Thu Apr 12 01:30:52 2007 -0400

    Input: keyboard handler - use printk_ratelimit()

    Use printk_ratelimit() to protect ourselves from buggy drivers or
    devices endlessly generating invalid events.

    Suggested by Andrew Morton.
        Signed-off-by: Dmitry Torokhov <email address hidden>

I'm going to go ahead and mark this "Fix Released". Lemmit, since you are the original bug reporter, if this is not resolved for you please feel free to reopen this report by setting the status back to "New". Thanks.

[Lemmit Kaplinski (lemmit)]

I have no access to the hardware in question anymore, so I cannot verify.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.