Laptop special key events work only once

[tnoo]

Special keys are only recognized once. E.g. adjusting the brightness with Fn+F1 works, and gives the right key codes in /var/log/acpid, and also calls the panabright.sh script. Any further Function keys are ignored, and no more events are visible in the log file.

Fn+PgUp and so on still work, but don't produce any events in acpi.

Here is my logfile

> sudo tail -f /var/log/acpid

[Wed Feb 15 17:03:02 2006] received event "pcc HKEY 00000080 00000081"
[Wed Feb 15 17:03:02 2006] notifying client 3692[112:112]
[Wed Feb 15 17:03:02 2006] executing action "/etc/acpi/panabright.sh down"
[Wed Feb 15 17:03:02 2006] BEGIN HANDLER MESSAGES
[Wed Feb 15 17:03:03 2006] END HANDLER MESSAGES
[Wed Feb 15 17:03:03 2006] action exited with status 0
[Wed Feb 15 17:03:03 2006] completed event "pcc HKEY 00000080 00000081"

Ubuntu Dapper (2/15/06), Panasonic W4

[John Stowers (nzjrs)]

Confirmed that I am seeing this

https://wiki.ubuntu.com/LaptopTestingTeam/PanasonicCFR4

This is a serious regression from breezy. Maybe also see https://launchpad.net/distros/ubuntu/+bug/33855

[James Whitlock (wiggleraway)]

I'm also experiencing this problem. This output can be seen on dmesg on the first key press, subsequent keypress show nothing:
[4294787.247000] Oops: 0000 [#1]
[4294787.247000] PREEMPT SMP
[4294787.247000] Modules linked in: binfmt_misc rfcomm l2cap bluetooth i915 drm speedstep_centrino cpufreq_powersave cpufreq_stats cpufreq_userspace cpufreq_ond emand cpufreq_conservative freq_table tc1100_wmi video acpi_sbs battery i2c_acpi _ec i2c_core container button pcc_acpi sony_acpi ac dev_acpi hotkey ntfs nls_iso 8859_1 nls_cp437 vfat fat dm_mod md_mod parport_pc lp parport pcmcia 8139too ipw 2200 ieee80211 ieee80211_crypt tsdev 8139cp mii yenta_socket rsrc_nonstatic pcmc ia_core snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_pcm_oss snd_mixer_oss snd_p cm snd_timer psmouse snd soundcore serio_raw snd_page_alloc shpchp pci_hotplug h w_random intel_agp agpgart evdev joydev usbhid reiserfs ehci_hcd uhci_hcd usbcor e ide_disk piix generic thermal processor fan capability commoncap vga16fb vgast ate fbcon tileblit font bitblit softcursor
[4294787.247000] CPU: 0
[4294787.247000] EIP: 0060:[<c0278888>] Not tainted VLI
[4294787.247000] EFLAGS: 00210246 (2.6.15-18-686)
[4294787.247000] EIP is at input_event+0xb8/0x4c0
[4294787.247000] eax: 00000000 ebx: ffffffec ecx: 00000000 edx: 00000000
[4294787.247000] esi: da78f800 edi: 00000001 ebp: 000000e1 esp: df173efc
[4294787.247000] ds: 007b es: 007b ss: 0068
[4294787.247000] Process kacpid (pid: 10, threadinfo=df172000 task=df6c0030)
[4294787.247000] Stack: c043e5e0 000000fe 00000001 c022b15b 00000001 da78f800 d9 5a890c df65ef40
[4294787.247000] d95a8900 e04d269c da78f800 00000001 000000e1 00000001 d9 cf1184 c021933d
[4294787.247000] df2f5760 00000080 df2f5760 d95a8900 c0214eb5 d9cf1184 00 200202 c01370b3
[4294787.247000] Call Trace:
[4294787.247000] [<c022b15b>] acpi_bus_generate_event+0xb1/0xba
[4294787.247000] [<e04d269c>] acpi_pcc_generete_keyinput+0x4c/0x80 [pcc_acpi]
[4294787.247000] [<c021933d>] acpi_ev_notify_dispatch+0x4e/0x5b
[4294787.247000] [<c0214eb5>] acpi_os_execute_deferred+0xe/0x1b
[4294787.247000] [<c01370b3>] worker_thread+0x1b3/0x270
[4294787.247000] [<c0214ea7>] acpi_os_execute_deferred+0x0/0x1b
[4294787.247000] [<c011f0d0>] default_wake_function+0x0/0x20
[4294787.247000] [<c0136f00>] worker_thread+0x0/0x270
[4294787.247000] [<c013bf78>] kthread+0xc8/0xd0
[4294787.247000] [<c013beb0>] kthread+0x0/0xd0
[4294787.247000] [<c0101525>] kernel_thread_helper+0x5/0x10
[4294787.247000] Code: 24 30 8b 6c 24 20 89 7c 24 2c 8b 7c 24 1c 89 54 24 28 89 44 24 34 83 c4 24 ff e1 ff 24 bd a0 34 31 c0 8b 86 dc 06 00 00 8d 58 ec <8b> 53 14 0f 18 02 90 81 c6 dc 06 00 00 39 c6 75 1b e9 5e ff ff

After this, module pcc_acpi stops responding and makes it impossible to remove with rmmod.

This problem is solved using pcc_acpi fixes mentioned in here https://launchpad.net/distros/ubuntu/+source/linux-image-2.6.15-15-386/+bug/33855

[TedKisner (tskisner-public)]

Just wanted to add another confirmation that this kernel oops is caused by an old version of driver "pcc_acpi". The newer version of the driver linked to in bug #33855 fixes this problem (on my R4 anyway).

Since the fix has already been committed according to the the status of #33855, I suggest this bug be closed (or at least marked as a duplicate).

[Matt Zimmerman (mdz)]

If the original reporter can confirm that their problem was caused by this oops, we can close it.

[tnoo (answer)]

Yes, I am listening, and yes, the new driver mentioned in bug #33855 solves the problem.

Also the new scriptsBug #16424 by Ted Kisner described in bug #16424 further improved the situation.
Now if hibernate and suspend work I am all happy.

Thanks

[Daniel Robitaille (robitaille)]

> If the original reporter can confirm that their
> problem was caused by this oops, we can close it.

confirmed fixed by the original reporter. Thanks for testing this.