* [REGRESSION] Toshiba Fn keys + lidswitch
@ 2026-05-12 16:49 Nick
2026-05-19 8:55 ` Thorsten Leemhuis
2026-05-19 14:08 ` Rafael J. Wysocki
0 siblings, 2 replies; 13+ messages in thread
From: Nick @ 2026-05-12 16:49 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: regressions, linux-acpi, linux-kernel, linux-pm, todd.e.brandt,
xi.pardee, platform-driver-x86, stable
My Toshiba Tecra X40 laptop's function keys no longer send events.
Specifically the mute ("KEY_MUTE"), lock ("KEY_COFFEE"), "power plan"
("KEY_BATTERY"), sleep ("KEY_SLEEP"), mic mute (for some reason this
reads as "KEY_SUSPEND"), screen switch ("KEY_SWITCHVIDEOMODE"),
brightness ("KEY_BRIGHTNESSDOWN" and "KEY_BRIGHTNESSUP"), and rfkill
("KEY_WLAN") hotkeys -- these are the Fn-shifted versions of Esc, F1,
F2, F3, F4, F5, F6, F7 and F8 -- keys no longer work. Neither does the
lid-switch.
Fn+F9, Fn+10, Fn+F11 and Fn+12 still work; those show up on
/dev/input/event3 like the rest of my keyboard, but the hotkeys show up
on /dev/input/event6.
I'm on ArchLinux. My keys worked on v6.19.14, I first noticed them
broken on v7.0.2.
I bisected mainline and found the break is: "ACPI: scan: Use
acpi_setup_gpe_for_wake() for buttons"
<https://lore.kernel.org/all/2259694.irdbgypaU6@rafael.j.wysocki/>.
That is, 57c31e6d620f132dcf610b2c52b4cdbd203c6f4a is bad and
88fad6ce090b395af4c654594a54589a386bf24b is good.
#regzbot introduced: 57c31e6d620f132dcf610b2c52b4cdbd203c6f4a
Maybe acpi_mark_gpe_for_wake was initializing something particular to
Toshiba hardware?
To reproduce, just boot and try to use the hotkeys. They won't work.
For more detail, use libinput as follows.
Here is a sample of pressing all the hotkeys in order on a working
version:
+ libinput debug-events --show-keycodes
-event2 DEVICE_ADDED Power Button seat0 default group1 cap:k
-event4 DEVICE_ADDED Video Bus seat0 default group2 cap:k
-event1 DEVICE_ADDED Power Button seat0 default group3 cap:k
-event0 DEVICE_ADDED Lid Switch seat0 default group4 cap:S
-event6 DEVICE_ADDED Toshiba input device seat0 default group5 cap:k
-event12 DEVICE_ADDED Synaptics TM3322-002 seat0 default group6 cap:pg
size 95x53mm tap (dl off) left scroll-nat scroll-2fg-edge
click-buttonareas-clickfinger dwt-on dwtp-on
-event3 DEVICE_ADDED AT Translated Set 2 keyboard seat0 default group7
cap:k
-event6 KEYBOARD_KEY +0.000s KEY_MUTE (113) pressed
event6 KEYBOARD_KEY +0.000s KEY_MUTE (113) released
event6 KEYBOARD_KEY +2.427s KEY_MUTE (113) pressed
event6 KEYBOARD_KEY +2.427s KEY_MUTE (113) released
event6 KEYBOARD_KEY +3.879s KEY_MUTE (113) pressed
event6 KEYBOARD_KEY +3.879s KEY_MUTE (113) released
event6 KEYBOARD_KEY +4.587s KEY_MUTE (113) pressed
event6 KEYBOARD_KEY +4.587s KEY_MUTE (113) released
event6 KEYBOARD_KEY +5.451s KEY_COFFEE (152) pressed
event6 KEYBOARD_KEY +5.451s KEY_COFFEE (152) released
event6 KEYBOARD_KEY +5.937s KEY_COFFEE (152) pressed
event6 KEYBOARD_KEY +5.937s KEY_COFFEE (152) released
event6 KEYBOARD_KEY +6.362s KEY_COFFEE (152) pressed
event6 KEYBOARD_KEY +6.362s KEY_COFFEE (152) released
event6 KEYBOARD_KEY +6.625s KEY_COFFEE (152) pressed
event6 KEYBOARD_KEY +6.625s KEY_COFFEE (152) released
event6 KEYBOARD_KEY +6.868s KEY_COFFEE (152) pressed
event6 KEYBOARD_KEY +6.868s KEY_COFFEE (152) released
event6 KEYBOARD_KEY +7.110s KEY_COFFEE (152) pressed
event6 KEYBOARD_KEY +7.110s KEY_COFFEE (152) released
event6 KEYBOARD_KEY +7.312s KEY_COFFEE (152) pressed
event6 KEYBOARD_KEY +7.312s KEY_COFFEE (152) released
event6 KEYBOARD_KEY +7.495s KEY_COFFEE (152) pressed
event6 KEYBOARD_KEY +7.495s KEY_COFFEE (152) released
event6 KEYBOARD_KEY +9.331s KEY_COFFEE (152) pressed
event6 KEYBOARD_KEY +9.331s KEY_COFFEE (152) released
event6 KEYBOARD_KEY +10.949s KEY_COFFEE (152) pressed
event6 KEYBOARD_KEY +10.949s KEY_COFFEE (152) released
event6 KEYBOARD_KEY +16.572s KEY_BATTERY (236) pressed
event6 KEYBOARD_KEY +16.572s KEY_BATTERY (236) released
event6 KEYBOARD_KEY +16.997s KEY_BATTERY (236) pressed
event6 KEYBOARD_KEY +16.997s KEY_BATTERY (236) released
event6 KEYBOARD_KEY +17.503s KEY_BATTERY (236) pressed
event6 KEYBOARD_KEY +17.503s KEY_BATTERY (236) released
event6 KEYBOARD_KEY +17.705s KEY_BATTERY (236) pressed
event6 KEYBOARD_KEY +17.705s KEY_BATTERY (236) released
event6 KEYBOARD_KEY +18.145s KEY_BATTERY (236) pressed
event6 KEYBOARD_KEY +18.145s KEY_BATTERY (236) released
event6 KEYBOARD_KEY +18.348s KEY_BATTERY (236) pressed
event6 KEYBOARD_KEY +18.348s KEY_BATTERY (236) released
event6 KEYBOARD_KEY +18.711s KEY_BATTERY (236) pressed
event6 KEYBOARD_KEY +18.712s KEY_BATTERY (236) released
event6 KEYBOARD_KEY +25.610s KEY_BATTERY (236) pressed
event6 KEYBOARD_KEY +25.610s KEY_BATTERY (236) released
event6 KEYBOARD_KEY +26.561s KEY_BATTERY (236) pressed
event6 KEYBOARD_KEY +26.561s KEY_BATTERY (236) released
event6 KEYBOARD_KEY +27.673s KEY_SLEEP (142) pressed
event6 KEYBOARD_KEY +27.673s KEY_SLEEP (142) released
event6 KEYBOARD_KEY +29.666s KEY_SLEEP (142) pressed
event6 KEYBOARD_KEY +29.666s KEY_SLEEP (142) released
event6 KEYBOARD_KEY +30.009s KEY_SLEEP (142) pressed
event6 KEYBOARD_KEY +30.009s KEY_SLEEP (142) released
event6 KEYBOARD_KEY +30.494s KEY_SLEEP (142) pressed
event6 KEYBOARD_KEY +30.494s KEY_SLEEP (142) released
event6 KEYBOARD_KEY +30.798s KEY_SLEEP (142) pressed
event6 KEYBOARD_KEY +30.798s KEY_SLEEP (142) released
event6 KEYBOARD_KEY +31.082s KEY_SLEEP (142) pressed
event6 KEYBOARD_KEY +31.082s KEY_SLEEP (142) released
event6 KEYBOARD_KEY +31.384s KEY_SLEEP (142) pressed
event6 KEYBOARD_KEY +31.384s KEY_SLEEP (142) released
event6 KEYBOARD_KEY +32.072s KEY_SLEEP (142) pressed
event6 KEYBOARD_KEY +32.072s KEY_SLEEP (142) released
event6 KEYBOARD_KEY +32.776s KEY_SLEEP (142) pressed
event6 KEYBOARD_KEY +32.776s KEY_SLEEP (142) released
event6 KEYBOARD_KEY +33.458s KEY_SLEEP (142) pressed
event6 KEYBOARD_KEY +33.458s KEY_SLEEP (142) released
event6 KEYBOARD_KEY +40.569s KEY_SUSPEND (205) pressed
event6 KEYBOARD_KEY +40.569s KEY_SUSPEND (205) released
event6 KEYBOARD_KEY +40.813s KEY_SUSPEND (205) pressed
event6 KEYBOARD_KEY +40.813s KEY_SUSPEND (205) released
event6 KEYBOARD_KEY +41.642s KEY_SUSPEND (205) pressed
event6 KEYBOARD_KEY +41.642s KEY_SUSPEND (205) released
event6 KEYBOARD_KEY +43.179s KEY_SUSPEND (205) pressed
event6 KEYBOARD_KEY +43.179s KEY_SUSPEND (205) released
event6 KEYBOARD_KEY +43.705s KEY_SUSPEND (205) pressed
event6 KEYBOARD_KEY +43.705s KEY_SUSPEND (205) released
event6 KEYBOARD_KEY +45.085s KEY_SUSPEND (205) pressed
event6 KEYBOARD_KEY +45.085s KEY_SUSPEND (205) released
event6 KEYBOARD_KEY +48.515s KEY_SWITCHVIDEOMODE (227) pressed
event6 KEYBOARD_KEY +48.515s KEY_SWITCHVIDEOMODE (227) released
event6 KEYBOARD_KEY +48.858s KEY_SWITCHVIDEOMODE (227) pressed
event6 KEYBOARD_KEY +48.858s KEY_SWITCHVIDEOMODE (227) released
event6 KEYBOARD_KEY +49.425s KEY_SWITCHVIDEOMODE (227) pressed
event6 KEYBOARD_KEY +49.425s KEY_SWITCHVIDEOMODE (227) released
event6 KEYBOARD_KEY +49.667s KEY_SWITCHVIDEOMODE (227) pressed
event6 KEYBOARD_KEY +49.667s KEY_SWITCHVIDEOMODE (227) released
event6 KEYBOARD_KEY +50.138s KEY_SWITCHVIDEOMODE (227) pressed
event6 KEYBOARD_KEY +50.138s KEY_SWITCHVIDEOMODE (227) released
event6 KEYBOARD_KEY +50.340s KEY_SWITCHVIDEOMODE (227) pressed
event6 KEYBOARD_KEY +50.340s KEY_SWITCHVIDEOMODE (227) released
event6 KEYBOARD_KEY +50.745s KEY_SWITCHVIDEOMODE (227) pressed
event6 KEYBOARD_KEY +50.745s KEY_SWITCHVIDEOMODE (227) released
event6 KEYBOARD_KEY +50.987s KEY_SWITCHVIDEOMODE (227) pressed
event6 KEYBOARD_KEY +50.987s KEY_SWITCHVIDEOMODE (227) released
event6 KEYBOARD_KEY +51.786s KEY_SWITCHVIDEOMODE (227) pressed
event6 KEYBOARD_KEY +51.786s KEY_SWITCHVIDEOMODE (227) released
event6 KEYBOARD_KEY +52.287s KEY_SWITCHVIDEOMODE (227) pressed
event6 KEYBOARD_KEY +52.287s KEY_SWITCHVIDEOMODE (227) released
event6 KEYBOARD_KEY +56.994s KEY_BRIGHTNESSDOWN (224) pressed
event6 KEYBOARD_KEY +56.994s KEY_BRIGHTNESSDOWN (224) released
event6 KEYBOARD_KEY +57.662s KEY_BRIGHTNESSDOWN (224) pressed
event6 KEYBOARD_KEY +57.662s KEY_BRIGHTNESSDOWN (224) released
event6 KEYBOARD_KEY +58.188s KEY_BRIGHTNESSDOWN (224) pressed
event6 KEYBOARD_KEY +58.188s KEY_BRIGHTNESSDOWN (224) released
event6 KEYBOARD_KEY +58.450s KEY_BRIGHTNESSDOWN (224) pressed
event6 KEYBOARD_KEY +58.450s KEY_BRIGHTNESSDOWN (224) released
event6 KEYBOARD_KEY +59.230s KEY_BRIGHTNESSDOWN (224) pressed
event6 KEYBOARD_KEY +59.230s KEY_BRIGHTNESSDOWN (224) released
event6 KEYBOARD_KEY +63.563s KEY_BRIGHTNESSUP (225) pressed
event6 KEYBOARD_KEY +63.563s KEY_BRIGHTNESSUP (225) released
event6 KEYBOARD_KEY +64.109s KEY_BRIGHTNESSUP (225) pressed
event6 KEYBOARD_KEY +64.109s KEY_BRIGHTNESSUP (225) released
event6 KEYBOARD_KEY +64.888s KEY_BRIGHTNESSUP (225) pressed
event6 KEYBOARD_KEY +64.888s KEY_BRIGHTNESSUP (225) released
event6 KEYBOARD_KEY +65.080s KEY_BRIGHTNESSUP (225) pressed
event6 KEYBOARD_KEY +65.080s KEY_BRIGHTNESSUP (225) released
event6 KEYBOARD_KEY +68.559s KEY_WLAN (238) pressed
event6 KEYBOARD_KEY +68.559s KEY_WLAN (238) released
event6 KEYBOARD_KEY +69.536s KEY_WLAN (238) pressed
event6 KEYBOARD_KEY +69.536s KEY_WLAN (238) released
event6 KEYBOARD_KEY +69.758s KEY_WLAN (238) pressed
event6 KEYBOARD_KEY +69.758s KEY_WLAN (238) released
event6 KEYBOARD_KEY +70.304s KEY_WLAN (238) pressed
event6 KEYBOARD_KEY +70.304s KEY_WLAN (238) released
event6 KEYBOARD_KEY +71.163s KEY_WLAN (238) pressed
event6 KEYBOARD_KEY +71.163s KEY_WLAN (238) released
event6 KEYBOARD_KEY +71.406s KEY_WLAN (238) pressed
event6 KEYBOARD_KEY +71.406s KEY_WLAN (238) released
event6 KEYBOARD_KEY +72.412s KEY_WLAN (238) pressed
event6 KEYBOARD_KEY +72.412s KEY_WLAN (238) released
-event3 KEYBOARD_KEY +78.318s KEY_LEFTCTRL (29) pressed
event3 KEYBOARD_KEY +78.321s KEY_LEFTMETA (125) pressed
event3 KEYBOARD_KEY +78.322s KEY_F24 (194) pressed
event3 KEYBOARD_KEY +78.480s KEY_F24 (194) released
event3 KEYBOARD_KEY +78.482s KEY_LEFTMETA (125) released
event3 KEYBOARD_KEY +78.483s KEY_LEFTCTRL (29) released
event3 KEYBOARD_KEY +83.436s KEY_LEFTCTRL (29) pressed
event3 KEYBOARD_KEY +83.439s KEY_LEFTMETA (125) pressed
event3 KEYBOARD_KEY +83.442s KEY_F24 (194) pressed
event3 KEYBOARD_KEY +83.556s KEY_F24 (194) released
event3 KEYBOARD_KEY +83.559s KEY_LEFTMETA (125) released
event3 KEYBOARD_KEY +83.562s KEY_LEFTCTRL (29) released
event3 KEYBOARD_KEY +84.578s KEY_LEFTCTRL (29) pressed
event3 KEYBOARD_KEY +84.581s KEY_LEFTMETA (125) pressed
event3 KEYBOARD_KEY +84.582s KEY_F24 (194) pressed
event3 KEYBOARD_KEY +84.660s KEY_F24 (194) released
event3 KEYBOARD_KEY +84.663s KEY_LEFTMETA (125) released
event3 KEYBOARD_KEY +84.663s KEY_LEFTCTRL (29) released
event3 KEYBOARD_KEY +84.821s KEY_LEFTCTRL (29) pressed
event3 KEYBOARD_KEY +84.824s KEY_LEFTMETA (125) pressed
event3 KEYBOARD_KEY +84.824s KEY_F24 (194) pressed
event3 KEYBOARD_KEY +84.902s KEY_F24 (194) released
event3 KEYBOARD_KEY +84.906s KEY_LEFTMETA (125) released
event3 KEYBOARD_KEY +84.907s KEY_LEFTCTRL (29) released
event3 KEYBOARD_KEY +86.505s KEY_NUMLOCK (69) pressed
event3 KEYBOARD_KEY +86.626s KEY_NUMLOCK (69) released
event3 KEYBOARD_KEY +87.613s KEY_F10 (68) pressed
event3 KEYBOARD_KEY +87.754s KEY_F10 (68) released
event3 KEYBOARD_KEY +93.300s KEY_NUMLOCK (69) pressed
event3 KEYBOARD_KEY +93.462s KEY_NUMLOCK (69) released
event3 KEYBOARD_KEY +100.823s KEY_SCROLLLOCK (70) pressed
event3 KEYBOARD_KEY +100.985s KEY_SCROLLLOCK (70) released
event3 KEYBOARD_KEY +101.288s KEY_SCROLLLOCK (70) pressed
event3 KEYBOARD_KEY +101.430s KEY_SCROLLLOCK (70) released
event3 KEYBOARD_KEY +102.442s KEY_SCROLLLOCK (70) pressed
event3 KEYBOARD_KEY +102.563s KEY_SCROLLLOCK (70) released
event3 KEYBOARD_KEY +102.704s KEY_SCROLLLOCK (70) pressed
event3 KEYBOARD_KEY +102.866s KEY_SCROLLLOCK (70) released
Here's the same test with a broken kernel -- it only starts responding
when I get to the keys handled by 'event3':
+ libinput debug-events --show-keycodes
-event6 DEVICE_ADDED Toshiba input device seat0 default group1 cap:k
-event12 DEVICE_ADDED Synaptics TM3322-002 seat0 default group2 cap:pg
size 95x53mm tap (dl off) left scroll-nat scroll-2fg-edge
click-buttonareas-clickfinger dwt-on dwtp-on
-event4 DEVICE_ADDED Video Bus seat0 default group3 cap:k
-event2 DEVICE_ADDED Power Button seat0 default group4 cap:k
-event1 DEVICE_ADDED Power Button seat0 default group5 cap:k
-event0 DEVICE_ADDED Lid Switch seat0 default group6 cap:S
-event3 DEVICE_ADDED AT Translated Set 2 keyboard seat0 default group7
cap:k
event3 KEYBOARD_KEY +0.000s KEY_LEFTCTRL (29) pressed
event3 KEYBOARD_KEY +0.003s KEY_LEFTMETA (125) pressed
event3 KEYBOARD_KEY +0.005s KEY_F24 (194) pressed
event3 KEYBOARD_KEY +0.062s KEY_F24 (194) released
event3 KEYBOARD_KEY +0.066s KEY_LEFTMETA (125) released
event3 KEYBOARD_KEY +0.066s KEY_LEFTCTRL (29) released
event3 KEYBOARD_KEY +1.448s KEY_LEFTCTRL (29) pressed
event3 KEYBOARD_KEY +1.452s KEY_LEFTMETA (125) pressed
event3 KEYBOARD_KEY +1.453s KEY_F24 (194) pressed
event3 KEYBOARD_KEY +1.509s KEY_F24 (194) released
event3 KEYBOARD_KEY +1.511s KEY_LEFTMETA (125) released
event3 KEYBOARD_KEY +1.512s KEY_LEFTCTRL (29) released
event3 KEYBOARD_KEY +1.630s KEY_LEFTCTRL (29) pressed
event3 KEYBOARD_KEY +1.633s KEY_LEFTMETA (125) pressed
event3 KEYBOARD_KEY +1.633s KEY_F24 (194) pressed
event3 KEYBOARD_KEY +1.712s KEY_F24 (194) released
event3 KEYBOARD_KEY +1.715s KEY_LEFTMETA (125) released
event3 KEYBOARD_KEY +1.717s KEY_LEFTCTRL (29) released
event3 KEYBOARD_KEY +1.813s KEY_LEFTCTRL (29) pressed
event3 KEYBOARD_KEY +1.816s KEY_LEFTMETA (125) pressed
event3 KEYBOARD_KEY +1.818s KEY_F24 (194) pressed
event3 KEYBOARD_KEY +1.914s KEY_F24 (194) released
event3 KEYBOARD_KEY +1.917s KEY_LEFTMETA (125) released
event3 KEYBOARD_KEY +1.918s KEY_LEFTCTRL (29) released
event3 KEYBOARD_KEY +3.645s KEY_NUMLOCK (69) pressed
event3 KEYBOARD_KEY +3.705s KEY_NUMLOCK (69) released
event3 KEYBOARD_KEY +5.745s KEY_SCROLLLOCK (70) pressed
event3 KEYBOARD_KEY +5.805s KEY_SCROLLLOCK (70) released
event3 KEYBOARD_KEY +7.430s KEY_SCROLLLOCK (70) pressed
event3 KEYBOARD_KEY +7.552s KEY_SCROLLLOCK (70) released
event3 KEYBOARD_KEY +7.957s KEY_SCROLLLOCK (70) pressed
event3 KEYBOARD_KEY +8.058s KEY_SCROLLLOCK (70) released
event3 KEYBOARD_KEY +8.402s KEY_SCROLLLOCK (70) pressed
event3 KEYBOARD_KEY +8.443s KEY_SCROLLLOCK (70) released
event3 KEYBOARD_KEY +8.604s KEY_SCROLLLOCK (70) pressed
event3 KEYBOARD_KEY +8.685s KEY_SCROLLLOCK (70) released
event3 KEYBOARD_KEY +8.928s KEY_SCROLLLOCK (70) pressed
event3 KEYBOARD_KEY +8.968s KEY_SCROLLLOCK (70) released
On a working system:
+ udevadm info /dev/input/event6
P: /devices/LNXSYSTM:00/LNXSYBUS:00/TOS6208:00/input/input8/event6
M: event6
R: 6
J: c13:70
U: input
D: c 13:70
N: input/event6
L: 0
E:
DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/TOS6208:00/input/input8/event6
E: DEVNAME=/dev/input/event6
E: MAJOR=13
E: MINOR=70
E: SUBSYSTEM=input
E: USEC_INITIALIZED=8887326
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_BUS=acpi
E: ID_PATH=acpi-TOS6208:00
E: ID_PATH_TAG=acpi-TOS6208_00
E: ID_INTEGRATION=internal
E: LIBINPUT_DEVICE_GROUP=19/0/0:toshiba_acpi
E: TAGS=:power-switch:
E: CURRENT_TAGS=:power-switch:
On a broken system, event6 is still MAJOR=13, MINOR=70 but it has been
re-assigned to a speaker; meanwhile toshiba_acpi has moved to MAJOR=13
MINOR=69 and event5:
$ udevadm info /dev/input/event6 /dev/input/event5
P: /devices/platform/pcspkr/input/input7/event6
M: event6
R: 6
J: c13:70
U: input
D: c 13:70
N: input/event6
L: 0
S: input/by-path/platform-pcspkr-event-spkr
E: DEVPATH=/devices/platform/pcspkr/input/input7/event6
E: DEVNAME=/dev/input/event6
E: MAJOR=13
E: MINOR=70
E: SUBSYSTEM=input
E: USEC_INITIALIZED=9257335
E: ID_INPUT=1
E: ID_BUS=platform
E: ID_SERIAL=noserial
E: ID_PATH=platform-pcspkr
E: ID_PATH_TAG=platform-pcspkr
E: ID_INTEGRATION=internal
E: LIBINPUT_DEVICE_GROUP=10/1f/1:isa0061
E: DEVLINKS=/dev/input/by-path/platform-pcspkr-event-spkr
P: /devices/LNXSYSTM:00/LNXSYBUS:00/TOS6208:00/input/input6/event5
M: event5
R: 5
J: c13:69
U: input
D: c 13:69
N: input/event5
L: 0
E:
DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/TOS6208:00/input/input6/event5
E: DEVNAME=/dev/input/event5
E: MAJOR=13
E: MINOR=69
E: SUBSYSTEM=input
E: USEC_INITIALIZED=9014054
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_BUS=acpi
E: ID_PATH=acpi-TOS6208:00
E: ID_PATH_TAG=acpi-TOS6208_00
E: ID_INTEGRATION=internal
E: LIBINPUT_DEVICE_GROUP=19/0/0:toshiba_acpi
E: TAGS=:power-switch:
E: CURRENT_TAGS=:power-switch:
Here's the .config I used while bisecting:
https://gist.github.com/kousu/4c8b4b1dd35621bc287fd654179ce9fa/raw/321d86332f1c8e681fce99f2c23d6762cc185c9a/kernel%2520.config
Here's my dmesg:
- working:
https://gist.githubusercontent.com/kousu/4c8b4b1dd35621bc287fd654179ce9fa/raw/6c577488c0477188cf187a04d71e455bc6488204/working.dmesg
- broken:
https://gist.github.com/kousu/4c8b4b1dd35621bc287fd654179ce9fa/raw/6c577488c0477188cf187a04d71e455bc6488204/broken.dmesg
(note: it says "toshiba_acpi: Unable to query Hotkey Event Type" but
that's a red-herring, both versions say that)
Here is my dmidecode:
+ dmidecode -t system
# dmidecode 3.7
Getting SMBIOS data from sysfs.
SMBIOS 3.1.0 present.
Handle 0x001E, DMI type 15, 25 bytes
System Event Log
Area Length: 124 bytes
Header Start Offset: 0x0000
Data Start Offset: 0x0000
Access Method: General-purpose non-volatile data functions
Access Address: 0x0003
Status: Valid, Not Full
Change Token: 0x00000000
Header Format: No Header
Supported Log Type Descriptors: 0
Handle 0x0025, DMI type 32, 11 bytes
System Boot Information
Status: No errors detected
Handle 0x0013, DMI type 1, 27 bytes
System Information
Manufacturer: TOSHIBA
Product Name: TECRA X40-E
Version: PT482C-06D00UHQ
Serial Number: [REDACTED]
UUID: bffba9c3-e4c8-4d87-8665-b3172752031a
Wake-up Type: Other
SKU Number: PT482C
Family: TECRA
Handle 0x001C, DMI type 12, 5 bytes
System Configuration Options
Option 1: GSW:1000000000
+ dmidecode -t bios
# dmidecode 3.7
Getting SMBIOS data from sysfs.
SMBIOS 3.1.0 present.
Handle 0x0012, DMI type 0, 26 bytes
Platform Firmware Information
Vendor: TOSHIBA
Version: Version 2.50
Release Date: 10/19/2021
ROM Size: 8 MiB
Characteristics:
PCI is supported
Firmware is upgradeable
Firmware shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Function key-initiated network boot is supported
Targeted content distribution is supported
UEFI is supported
Platform Firmware Revision: 2.50
Embedded Controller Firmware Revision: 1.40
Handle 0x001D, DMI type 13, 22 bytes
Firmware Language Information
Language Description Format: Abbreviated
Installable Languages: 2
enUS
frCA
Currently Installed Language: enUS
Please let me know if if I can provide any more information. I could
provide acpidump if that's helpful.
Thank you for your work :)
- kousu
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: [REGRESSION] Toshiba Fn keys + lidswitch
2026-05-12 16:49 [REGRESSION] Toshiba Fn keys + lidswitch Nick
@ 2026-05-19 8:55 ` Thorsten Leemhuis
2026-05-19 11:48 ` Rafael J. Wysocki
2026-05-19 14:08 ` Rafael J. Wysocki
1 sibling, 1 reply; 13+ messages in thread
From: Thorsten Leemhuis @ 2026-05-19 8:55 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Nick, regressions, linux-acpi, linux-kernel, linux-pm,
todd.e.brandt, xi.pardee, platform-driver-x86, stable,
Azael Avalos
[CCing Azael, just in case]
On 5/12/26 18:49, Nick wrote:
> My Toshiba Tecra X40 laptop's function keys no longer send events.
Rafael, have you seen that this regression seems to be caused by a
change of yours? Namely 57c31e6d620f13 ("ACPI: scan: Use
acpi_setup_gpe_for_wake() for buttons") [v7.0-rc1]
No complains, just wondering, as it was easy to miss. Ciao, Thorsten
> Specifically the mute ("KEY_MUTE"), lock ("KEY_COFFEE"), "power plan"
> ("KEY_BATTERY"), sleep ("KEY_SLEEP"), mic mute (for some reason this
> reads as "KEY_SUSPEND"), screen switch ("KEY_SWITCHVIDEOMODE"),
> brightness ("KEY_BRIGHTNESSDOWN" and "KEY_BRIGHTNESSUP"), and rfkill
> ("KEY_WLAN") hotkeys -- these are the Fn-shifted versions of Esc, F1,
> F2, F3, F4, F5, F6, F7 and F8 -- keys no longer work. Neither does the
> lid-switch.
>
> Fn+F9, Fn+10, Fn+F11 and Fn+12 still work; those show up on /dev/input/
> event3 like the rest of my keyboard, but the hotkeys show up on /dev/
> input/event6.
>
> I'm on ArchLinux. My keys worked on v6.19.14, I first noticed them
> broken on v7.0.2.
>
> I bisected mainline and found the break is: "ACPI: scan: Use
> acpi_setup_gpe_for_wake() for buttons" <https://lore.kernel.org/
> all/2259694.irdbgypaU6@rafael.j.wysocki/>. That is,
> 57c31e6d620f132dcf610b2c52b4cdbd203c6f4a is bad and
> 88fad6ce090b395af4c654594a54589a386bf24b is good.
>
> #regzbot introduced: 57c31e6d620f132dcf610b2c52b4cdbd203c6f4a
>
> Maybe acpi_mark_gpe_for_wake was initializing something particular to
> Toshiba hardware?
>
> To reproduce, just boot and try to use the hotkeys. They won't work. For
> more detail, use libinput as follows.
>
> Here is a sample of pressing all the hotkeys in order on a working version:
>
> + libinput debug-events --show-keycodes
> -event2 DEVICE_ADDED Power Button seat0 default group1 cap:k
> -event4 DEVICE_ADDED Video Bus seat0 default group2 cap:k
> -event1 DEVICE_ADDED Power Button seat0 default group3 cap:k
> -event0 DEVICE_ADDED Lid Switch seat0 default group4 cap:S
> -event6 DEVICE_ADDED Toshiba input device seat0 default group5 cap:k
> -event12 DEVICE_ADDED Synaptics TM3322-002 seat0 default group6 cap:pg
> size 95x53mm tap (dl off) left scroll-nat scroll-2fg-edge click-
> buttonareas-clickfinger dwt-on dwtp-on
> -event3 DEVICE_ADDED AT Translated Set 2 keyboard seat0 default group7
> cap:k
> -event6 KEYBOARD_KEY +0.000s KEY_MUTE (113) pressed
> event6 KEYBOARD_KEY +0.000s KEY_MUTE (113) released
> event6 KEYBOARD_KEY +2.427s KEY_MUTE (113) pressed
> event6 KEYBOARD_KEY +2.427s KEY_MUTE (113) released
> event6 KEYBOARD_KEY +3.879s KEY_MUTE (113) pressed
> event6 KEYBOARD_KEY +3.879s KEY_MUTE (113) released
> event6 KEYBOARD_KEY +4.587s KEY_MUTE (113) pressed
> event6 KEYBOARD_KEY +4.587s KEY_MUTE (113) released
> event6 KEYBOARD_KEY +5.451s KEY_COFFEE (152) pressed
> event6 KEYBOARD_KEY +5.451s KEY_COFFEE (152) released
> event6 KEYBOARD_KEY +5.937s KEY_COFFEE (152) pressed
> event6 KEYBOARD_KEY +5.937s KEY_COFFEE (152) released
> event6 KEYBOARD_KEY +6.362s KEY_COFFEE (152) pressed
> event6 KEYBOARD_KEY +6.362s KEY_COFFEE (152) released
> event6 KEYBOARD_KEY +6.625s KEY_COFFEE (152) pressed
> event6 KEYBOARD_KEY +6.625s KEY_COFFEE (152) released
> event6 KEYBOARD_KEY +6.868s KEY_COFFEE (152) pressed
> event6 KEYBOARD_KEY +6.868s KEY_COFFEE (152) released
> event6 KEYBOARD_KEY +7.110s KEY_COFFEE (152) pressed
> event6 KEYBOARD_KEY +7.110s KEY_COFFEE (152) released
> event6 KEYBOARD_KEY +7.312s KEY_COFFEE (152) pressed
> event6 KEYBOARD_KEY +7.312s KEY_COFFEE (152) released
> event6 KEYBOARD_KEY +7.495s KEY_COFFEE (152) pressed
> event6 KEYBOARD_KEY +7.495s KEY_COFFEE (152) released
> event6 KEYBOARD_KEY +9.331s KEY_COFFEE (152) pressed
> event6 KEYBOARD_KEY +9.331s KEY_COFFEE (152) released
> event6 KEYBOARD_KEY +10.949s KEY_COFFEE (152) pressed
> event6 KEYBOARD_KEY +10.949s KEY_COFFEE (152) released
> event6 KEYBOARD_KEY +16.572s KEY_BATTERY (236) pressed
> event6 KEYBOARD_KEY +16.572s KEY_BATTERY (236) released
> event6 KEYBOARD_KEY +16.997s KEY_BATTERY (236) pressed
> event6 KEYBOARD_KEY +16.997s KEY_BATTERY (236) released
> event6 KEYBOARD_KEY +17.503s KEY_BATTERY (236) pressed
> event6 KEYBOARD_KEY +17.503s KEY_BATTERY (236) released
> event6 KEYBOARD_KEY +17.705s KEY_BATTERY (236) pressed
> event6 KEYBOARD_KEY +17.705s KEY_BATTERY (236) released
> event6 KEYBOARD_KEY +18.145s KEY_BATTERY (236) pressed
> event6 KEYBOARD_KEY +18.145s KEY_BATTERY (236) released
> event6 KEYBOARD_KEY +18.348s KEY_BATTERY (236) pressed
> event6 KEYBOARD_KEY +18.348s KEY_BATTERY (236) released
> event6 KEYBOARD_KEY +18.711s KEY_BATTERY (236) pressed
> event6 KEYBOARD_KEY +18.712s KEY_BATTERY (236) released
> event6 KEYBOARD_KEY +25.610s KEY_BATTERY (236) pressed
> event6 KEYBOARD_KEY +25.610s KEY_BATTERY (236) released
> event6 KEYBOARD_KEY +26.561s KEY_BATTERY (236) pressed
> event6 KEYBOARD_KEY +26.561s KEY_BATTERY (236) released
> event6 KEYBOARD_KEY +27.673s KEY_SLEEP (142) pressed
> event6 KEYBOARD_KEY +27.673s KEY_SLEEP (142) released
> event6 KEYBOARD_KEY +29.666s KEY_SLEEP (142) pressed
> event6 KEYBOARD_KEY +29.666s KEY_SLEEP (142) released
> event6 KEYBOARD_KEY +30.009s KEY_SLEEP (142) pressed
> event6 KEYBOARD_KEY +30.009s KEY_SLEEP (142) released
> event6 KEYBOARD_KEY +30.494s KEY_SLEEP (142) pressed
> event6 KEYBOARD_KEY +30.494s KEY_SLEEP (142) released
> event6 KEYBOARD_KEY +30.798s KEY_SLEEP (142) pressed
> event6 KEYBOARD_KEY +30.798s KEY_SLEEP (142) released
> event6 KEYBOARD_KEY +31.082s KEY_SLEEP (142) pressed
> event6 KEYBOARD_KEY +31.082s KEY_SLEEP (142) released
> event6 KEYBOARD_KEY +31.384s KEY_SLEEP (142) pressed
> event6 KEYBOARD_KEY +31.384s KEY_SLEEP (142) released
> event6 KEYBOARD_KEY +32.072s KEY_SLEEP (142) pressed
> event6 KEYBOARD_KEY +32.072s KEY_SLEEP (142) released
> event6 KEYBOARD_KEY +32.776s KEY_SLEEP (142) pressed
> event6 KEYBOARD_KEY +32.776s KEY_SLEEP (142) released
> event6 KEYBOARD_KEY +33.458s KEY_SLEEP (142) pressed
> event6 KEYBOARD_KEY +33.458s KEY_SLEEP (142) released
> event6 KEYBOARD_KEY +40.569s KEY_SUSPEND (205) pressed
> event6 KEYBOARD_KEY +40.569s KEY_SUSPEND (205) released
> event6 KEYBOARD_KEY +40.813s KEY_SUSPEND (205) pressed
> event6 KEYBOARD_KEY +40.813s KEY_SUSPEND (205) released
> event6 KEYBOARD_KEY +41.642s KEY_SUSPEND (205) pressed
> event6 KEYBOARD_KEY +41.642s KEY_SUSPEND (205) released
> event6 KEYBOARD_KEY +43.179s KEY_SUSPEND (205) pressed
> event6 KEYBOARD_KEY +43.179s KEY_SUSPEND (205) released
> event6 KEYBOARD_KEY +43.705s KEY_SUSPEND (205) pressed
> event6 KEYBOARD_KEY +43.705s KEY_SUSPEND (205) released
> event6 KEYBOARD_KEY +45.085s KEY_SUSPEND (205) pressed
> event6 KEYBOARD_KEY +45.085s KEY_SUSPEND (205) released
> event6 KEYBOARD_KEY +48.515s KEY_SWITCHVIDEOMODE (227) pressed
> event6 KEYBOARD_KEY +48.515s KEY_SWITCHVIDEOMODE (227) released
> event6 KEYBOARD_KEY +48.858s KEY_SWITCHVIDEOMODE (227) pressed
> event6 KEYBOARD_KEY +48.858s KEY_SWITCHVIDEOMODE (227) released
> event6 KEYBOARD_KEY +49.425s KEY_SWITCHVIDEOMODE (227) pressed
> event6 KEYBOARD_KEY +49.425s KEY_SWITCHVIDEOMODE (227) released
> event6 KEYBOARD_KEY +49.667s KEY_SWITCHVIDEOMODE (227) pressed
> event6 KEYBOARD_KEY +49.667s KEY_SWITCHVIDEOMODE (227) released
> event6 KEYBOARD_KEY +50.138s KEY_SWITCHVIDEOMODE (227) pressed
> event6 KEYBOARD_KEY +50.138s KEY_SWITCHVIDEOMODE (227) released
> event6 KEYBOARD_KEY +50.340s KEY_SWITCHVIDEOMODE (227) pressed
> event6 KEYBOARD_KEY +50.340s KEY_SWITCHVIDEOMODE (227) released
> event6 KEYBOARD_KEY +50.745s KEY_SWITCHVIDEOMODE (227) pressed
> event6 KEYBOARD_KEY +50.745s KEY_SWITCHVIDEOMODE (227) released
> event6 KEYBOARD_KEY +50.987s KEY_SWITCHVIDEOMODE (227) pressed
> event6 KEYBOARD_KEY +50.987s KEY_SWITCHVIDEOMODE (227) released
> event6 KEYBOARD_KEY +51.786s KEY_SWITCHVIDEOMODE (227) pressed
> event6 KEYBOARD_KEY +51.786s KEY_SWITCHVIDEOMODE (227) released
> event6 KEYBOARD_KEY +52.287s KEY_SWITCHVIDEOMODE (227) pressed
> event6 KEYBOARD_KEY +52.287s KEY_SWITCHVIDEOMODE (227) released
> event6 KEYBOARD_KEY +56.994s KEY_BRIGHTNESSDOWN (224) pressed
> event6 KEYBOARD_KEY +56.994s KEY_BRIGHTNESSDOWN (224) released
> event6 KEYBOARD_KEY +57.662s KEY_BRIGHTNESSDOWN (224) pressed
> event6 KEYBOARD_KEY +57.662s KEY_BRIGHTNESSDOWN (224) released
> event6 KEYBOARD_KEY +58.188s KEY_BRIGHTNESSDOWN (224) pressed
> event6 KEYBOARD_KEY +58.188s KEY_BRIGHTNESSDOWN (224) released
> event6 KEYBOARD_KEY +58.450s KEY_BRIGHTNESSDOWN (224) pressed
> event6 KEYBOARD_KEY +58.450s KEY_BRIGHTNESSDOWN (224) released
> event6 KEYBOARD_KEY +59.230s KEY_BRIGHTNESSDOWN (224) pressed
> event6 KEYBOARD_KEY +59.230s KEY_BRIGHTNESSDOWN (224) released
> event6 KEYBOARD_KEY +63.563s KEY_BRIGHTNESSUP (225) pressed
> event6 KEYBOARD_KEY +63.563s KEY_BRIGHTNESSUP (225) released
> event6 KEYBOARD_KEY +64.109s KEY_BRIGHTNESSUP (225) pressed
> event6 KEYBOARD_KEY +64.109s KEY_BRIGHTNESSUP (225) released
> event6 KEYBOARD_KEY +64.888s KEY_BRIGHTNESSUP (225) pressed
> event6 KEYBOARD_KEY +64.888s KEY_BRIGHTNESSUP (225) released
> event6 KEYBOARD_KEY +65.080s KEY_BRIGHTNESSUP (225) pressed
> event6 KEYBOARD_KEY +65.080s KEY_BRIGHTNESSUP (225) released
> event6 KEYBOARD_KEY +68.559s KEY_WLAN (238) pressed
> event6 KEYBOARD_KEY +68.559s KEY_WLAN (238) released
> event6 KEYBOARD_KEY +69.536s KEY_WLAN (238) pressed
> event6 KEYBOARD_KEY +69.536s KEY_WLAN (238) released
> event6 KEYBOARD_KEY +69.758s KEY_WLAN (238) pressed
> event6 KEYBOARD_KEY +69.758s KEY_WLAN (238) released
> event6 KEYBOARD_KEY +70.304s KEY_WLAN (238) pressed
> event6 KEYBOARD_KEY +70.304s KEY_WLAN (238) released
> event6 KEYBOARD_KEY +71.163s KEY_WLAN (238) pressed
> event6 KEYBOARD_KEY +71.163s KEY_WLAN (238) released
> event6 KEYBOARD_KEY +71.406s KEY_WLAN (238) pressed
> event6 KEYBOARD_KEY +71.406s KEY_WLAN (238) released
> event6 KEYBOARD_KEY +72.412s KEY_WLAN (238) pressed
> event6 KEYBOARD_KEY +72.412s KEY_WLAN (238) released
> -event3 KEYBOARD_KEY +78.318s KEY_LEFTCTRL (29) pressed
> event3 KEYBOARD_KEY +78.321s KEY_LEFTMETA (125) pressed
> event3 KEYBOARD_KEY +78.322s KEY_F24 (194) pressed
> event3 KEYBOARD_KEY +78.480s KEY_F24 (194) released
> event3 KEYBOARD_KEY +78.482s KEY_LEFTMETA (125) released
> event3 KEYBOARD_KEY +78.483s KEY_LEFTCTRL (29) released
> event3 KEYBOARD_KEY +83.436s KEY_LEFTCTRL (29) pressed
> event3 KEYBOARD_KEY +83.439s KEY_LEFTMETA (125) pressed
> event3 KEYBOARD_KEY +83.442s KEY_F24 (194) pressed
> event3 KEYBOARD_KEY +83.556s KEY_F24 (194) released
> event3 KEYBOARD_KEY +83.559s KEY_LEFTMETA (125) released
> event3 KEYBOARD_KEY +83.562s KEY_LEFTCTRL (29) released
> event3 KEYBOARD_KEY +84.578s KEY_LEFTCTRL (29) pressed
> event3 KEYBOARD_KEY +84.581s KEY_LEFTMETA (125) pressed
> event3 KEYBOARD_KEY +84.582s KEY_F24 (194) pressed
> event3 KEYBOARD_KEY +84.660s KEY_F24 (194) released
> event3 KEYBOARD_KEY +84.663s KEY_LEFTMETA (125) released
> event3 KEYBOARD_KEY +84.663s KEY_LEFTCTRL (29) released
> event3 KEYBOARD_KEY +84.821s KEY_LEFTCTRL (29) pressed
> event3 KEYBOARD_KEY +84.824s KEY_LEFTMETA (125) pressed
> event3 KEYBOARD_KEY +84.824s KEY_F24 (194) pressed
> event3 KEYBOARD_KEY +84.902s KEY_F24 (194) released
> event3 KEYBOARD_KEY +84.906s KEY_LEFTMETA (125) released
> event3 KEYBOARD_KEY +84.907s KEY_LEFTCTRL (29) released
> event3 KEYBOARD_KEY +86.505s KEY_NUMLOCK (69) pressed
> event3 KEYBOARD_KEY +86.626s KEY_NUMLOCK (69) released
> event3 KEYBOARD_KEY +87.613s KEY_F10 (68) pressed
> event3 KEYBOARD_KEY +87.754s KEY_F10 (68) released
> event3 KEYBOARD_KEY +93.300s KEY_NUMLOCK (69) pressed
> event3 KEYBOARD_KEY +93.462s KEY_NUMLOCK (69) released
> event3 KEYBOARD_KEY +100.823s KEY_SCROLLLOCK (70) pressed
> event3 KEYBOARD_KEY +100.985s KEY_SCROLLLOCK (70) released
> event3 KEYBOARD_KEY +101.288s KEY_SCROLLLOCK (70) pressed
> event3 KEYBOARD_KEY +101.430s KEY_SCROLLLOCK (70) released
> event3 KEYBOARD_KEY +102.442s KEY_SCROLLLOCK (70) pressed
> event3 KEYBOARD_KEY +102.563s KEY_SCROLLLOCK (70) released
> event3 KEYBOARD_KEY +102.704s KEY_SCROLLLOCK (70) pressed
> event3 KEYBOARD_KEY +102.866s KEY_SCROLLLOCK (70) released
>
> Here's the same test with a broken kernel -- it only starts responding
> when I get to the keys handled by 'event3':
>
> + libinput debug-events --show-keycodes
> -event6 DEVICE_ADDED Toshiba input device seat0 default group1 cap:k
> -event12 DEVICE_ADDED Synaptics TM3322-002 seat0 default group2 cap:pg
> size 95x53mm tap (dl off) left scroll-nat scroll-2fg-edge click-
> buttonareas-clickfinger dwt-on dwtp-on
> -event4 DEVICE_ADDED Video Bus seat0 default group3 cap:k
> -event2 DEVICE_ADDED Power Button seat0 default group4 cap:k
> -event1 DEVICE_ADDED Power Button seat0 default group5 cap:k
> -event0 DEVICE_ADDED Lid Switch seat0 default group6 cap:S
> -event3 DEVICE_ADDED AT Translated Set 2 keyboard seat0 default group7
> cap:k
> event3 KEYBOARD_KEY +0.000s KEY_LEFTCTRL (29) pressed
> event3 KEYBOARD_KEY +0.003s KEY_LEFTMETA (125) pressed
> event3 KEYBOARD_KEY +0.005s KEY_F24 (194) pressed
> event3 KEYBOARD_KEY +0.062s KEY_F24 (194) released
> event3 KEYBOARD_KEY +0.066s KEY_LEFTMETA (125) released
> event3 KEYBOARD_KEY +0.066s KEY_LEFTCTRL (29) released
> event3 KEYBOARD_KEY +1.448s KEY_LEFTCTRL (29) pressed
> event3 KEYBOARD_KEY +1.452s KEY_LEFTMETA (125) pressed
> event3 KEYBOARD_KEY +1.453s KEY_F24 (194) pressed
> event3 KEYBOARD_KEY +1.509s KEY_F24 (194) released
> event3 KEYBOARD_KEY +1.511s KEY_LEFTMETA (125) released
> event3 KEYBOARD_KEY +1.512s KEY_LEFTCTRL (29) released
> event3 KEYBOARD_KEY +1.630s KEY_LEFTCTRL (29) pressed
> event3 KEYBOARD_KEY +1.633s KEY_LEFTMETA (125) pressed
> event3 KEYBOARD_KEY +1.633s KEY_F24 (194) pressed
> event3 KEYBOARD_KEY +1.712s KEY_F24 (194) released
> event3 KEYBOARD_KEY +1.715s KEY_LEFTMETA (125) released
> event3 KEYBOARD_KEY +1.717s KEY_LEFTCTRL (29) released
> event3 KEYBOARD_KEY +1.813s KEY_LEFTCTRL (29) pressed
> event3 KEYBOARD_KEY +1.816s KEY_LEFTMETA (125) pressed
> event3 KEYBOARD_KEY +1.818s KEY_F24 (194) pressed
> event3 KEYBOARD_KEY +1.914s KEY_F24 (194) released
> event3 KEYBOARD_KEY +1.917s KEY_LEFTMETA (125) released
> event3 KEYBOARD_KEY +1.918s KEY_LEFTCTRL (29) released
> event3 KEYBOARD_KEY +3.645s KEY_NUMLOCK (69) pressed
> event3 KEYBOARD_KEY +3.705s KEY_NUMLOCK (69) released
> event3 KEYBOARD_KEY +5.745s KEY_SCROLLLOCK (70) pressed
> event3 KEYBOARD_KEY +5.805s KEY_SCROLLLOCK (70) released
> event3 KEYBOARD_KEY +7.430s KEY_SCROLLLOCK (70) pressed
> event3 KEYBOARD_KEY +7.552s KEY_SCROLLLOCK (70) released
> event3 KEYBOARD_KEY +7.957s KEY_SCROLLLOCK (70) pressed
> event3 KEYBOARD_KEY +8.058s KEY_SCROLLLOCK (70) released
> event3 KEYBOARD_KEY +8.402s KEY_SCROLLLOCK (70) pressed
> event3 KEYBOARD_KEY +8.443s KEY_SCROLLLOCK (70) released
> event3 KEYBOARD_KEY +8.604s KEY_SCROLLLOCK (70) pressed
> event3 KEYBOARD_KEY +8.685s KEY_SCROLLLOCK (70) released
> event3 KEYBOARD_KEY +8.928s KEY_SCROLLLOCK (70) pressed
> event3 KEYBOARD_KEY +8.968s KEY_SCROLLLOCK (70) released
>
>
> On a working system:
>
> + udevadm info /dev/input/event6
> P: /devices/LNXSYSTM:00/LNXSYBUS:00/TOS6208:00/input/input8/event6
> M: event6
> R: 6
> J: c13:70
> U: input
> D: c 13:70
> N: input/event6
> L: 0
> E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/TOS6208:00/input/input8/event6
> E: DEVNAME=/dev/input/event6
> E: MAJOR=13
> E: MINOR=70
> E: SUBSYSTEM=input
> E: USEC_INITIALIZED=8887326
> E: ID_INPUT=1
> E: ID_INPUT_KEY=1
> E: ID_BUS=acpi
> E: ID_PATH=acpi-TOS6208:00
> E: ID_PATH_TAG=acpi-TOS6208_00
> E: ID_INTEGRATION=internal
> E: LIBINPUT_DEVICE_GROUP=19/0/0:toshiba_acpi
> E: TAGS=:power-switch:
> E: CURRENT_TAGS=:power-switch:
>
> On a broken system, event6 is still MAJOR=13, MINOR=70 but it has been
> re-assigned to a speaker; meanwhile toshiba_acpi has moved to MAJOR=13
> MINOR=69 and event5:
>
> $ udevadm info /dev/input/event6 /dev/input/event5
> P: /devices/platform/pcspkr/input/input7/event6
> M: event6
> R: 6
> J: c13:70
> U: input
> D: c 13:70
> N: input/event6
> L: 0
> S: input/by-path/platform-pcspkr-event-spkr
> E: DEVPATH=/devices/platform/pcspkr/input/input7/event6
> E: DEVNAME=/dev/input/event6
> E: MAJOR=13
> E: MINOR=70
> E: SUBSYSTEM=input
> E: USEC_INITIALIZED=9257335
> E: ID_INPUT=1
> E: ID_BUS=platform
> E: ID_SERIAL=noserial
> E: ID_PATH=platform-pcspkr
> E: ID_PATH_TAG=platform-pcspkr
> E: ID_INTEGRATION=internal
> E: LIBINPUT_DEVICE_GROUP=10/1f/1:isa0061
> E: DEVLINKS=/dev/input/by-path/platform-pcspkr-event-spkr
>
> P: /devices/LNXSYSTM:00/LNXSYBUS:00/TOS6208:00/input/input6/event5
> M: event5
> R: 5
> J: c13:69
> U: input
> D: c 13:69
> N: input/event5
> L: 0
> E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/TOS6208:00/input/input6/event5
> E: DEVNAME=/dev/input/event5
> E: MAJOR=13
> E: MINOR=69
> E: SUBSYSTEM=input
> E: USEC_INITIALIZED=9014054
> E: ID_INPUT=1
> E: ID_INPUT_KEY=1
> E: ID_BUS=acpi
> E: ID_PATH=acpi-TOS6208:00
> E: ID_PATH_TAG=acpi-TOS6208_00
> E: ID_INTEGRATION=internal
> E: LIBINPUT_DEVICE_GROUP=19/0/0:toshiba_acpi
> E: TAGS=:power-switch:
> E: CURRENT_TAGS=:power-switch:
>
>
> Here's the .config I used while bisecting: https://gist.github.com/
> kousu/4c8b4b1dd35621bc287fd654179ce9fa/
> raw/321d86332f1c8e681fce99f2c23d6762cc185c9a/kernel%2520.config
>
> Here's my dmesg:
>
> - working: https://gist.githubusercontent.com/
> kousu/4c8b4b1dd35621bc287fd654179ce9fa/
> raw/6c577488c0477188cf187a04d71e455bc6488204/working.dmesg
> - broken: https://gist.github.com/
> kousu/4c8b4b1dd35621bc287fd654179ce9fa/
> raw/6c577488c0477188cf187a04d71e455bc6488204/broken.dmesg
>
> (note: it says "toshiba_acpi: Unable to query Hotkey Event Type" but
> that's a red-herring, both versions say that)
>
> Here is my dmidecode:
>
> + dmidecode -t system
> # dmidecode 3.7
> Getting SMBIOS data from sysfs.
> SMBIOS 3.1.0 present.
>
> Handle 0x001E, DMI type 15, 25 bytes
> System Event Log
> Area Length: 124 bytes
> Header Start Offset: 0x0000
> Data Start Offset: 0x0000
> Access Method: General-purpose non-volatile data functions
> Access Address: 0x0003
> Status: Valid, Not Full
> Change Token: 0x00000000
> Header Format: No Header
> Supported Log Type Descriptors: 0
>
> Handle 0x0025, DMI type 32, 11 bytes
> System Boot Information
> Status: No errors detected
>
> Handle 0x0013, DMI type 1, 27 bytes
> System Information
> Manufacturer: TOSHIBA
> Product Name: TECRA X40-E
> Version: PT482C-06D00UHQ
> Serial Number: [REDACTED]
> UUID: bffba9c3-e4c8-4d87-8665-b3172752031a
> Wake-up Type: Other
> SKU Number: PT482C
> Family: TECRA
>
> Handle 0x001C, DMI type 12, 5 bytes
> System Configuration Options
> Option 1: GSW:1000000000
>
> + dmidecode -t bios
> # dmidecode 3.7
> Getting SMBIOS data from sysfs.
> SMBIOS 3.1.0 present.
>
> Handle 0x0012, DMI type 0, 26 bytes
> Platform Firmware Information
> Vendor: TOSHIBA
> Version: Version 2.50
> Release Date: 10/19/2021
> ROM Size: 8 MiB
> Characteristics:
> PCI is supported
> Firmware is upgradeable
> Firmware shadowing is allowed
> Boot from CD is supported
> Selectable boot is supported
> EDD is supported
> Print screen service is supported (int 5h)
> 8042 keyboard services are supported (int 9h)
> Serial services are supported (int 14h)
> Printer services are supported (int 17h)
> ACPI is supported
> USB legacy is supported
> BIOS boot specification is supported
> Function key-initiated network boot is supported
> Targeted content distribution is supported
> UEFI is supported
> Platform Firmware Revision: 2.50
> Embedded Controller Firmware Revision: 1.40
>
> Handle 0x001D, DMI type 13, 22 bytes
> Firmware Language Information
> Language Description Format: Abbreviated
> Installable Languages: 2
> enUS
> frCA
> Currently Installed Language: enUS
>
>
> Please let me know if if I can provide any more information. I could
> provide acpidump if that's helpful.
>
> Thank you for your work :)
>
> - kousu
>
>
>
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: [REGRESSION] Toshiba Fn keys + lidswitch
2026-05-19 8:55 ` Thorsten Leemhuis
@ 2026-05-19 11:48 ` Rafael J. Wysocki
0 siblings, 0 replies; 13+ messages in thread
From: Rafael J. Wysocki @ 2026-05-19 11:48 UTC (permalink / raw)
To: Thorsten Leemhuis
Cc: Rafael J. Wysocki, Nick, regressions, linux-acpi, linux-kernel,
linux-pm, todd.e.brandt, xi.pardee, platform-driver-x86, stable,
Azael Avalos
On Tue, May 19, 2026 at 10:56 AM Thorsten Leemhuis
<regressions@leemhuis.info> wrote:
>
> [CCing Azael, just in case]
>
> On 5/12/26 18:49, Nick wrote:
> > My Toshiba Tecra X40 laptop's function keys no longer send events.
>
> Rafael, have you seen that this regression seems to be caused by a
> change of yours? Namely 57c31e6d620f13 ("ACPI: scan: Use
> acpi_setup_gpe_for_wake() for buttons") [v7.0-rc1]
Yes, I have.
> No complains, just wondering, as it was easy to miss. Ciao, Thorsten
Sure, thanks for pointing this out.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [REGRESSION] Toshiba Fn keys + lidswitch
2026-05-12 16:49 [REGRESSION] Toshiba Fn keys + lidswitch Nick
2026-05-19 8:55 ` Thorsten Leemhuis
@ 2026-05-19 14:08 ` Rafael J. Wysocki
2026-05-19 17:15 ` Rafael J. Wysocki
2026-05-30 12:19 ` John Veness
1 sibling, 2 replies; 13+ messages in thread
From: Rafael J. Wysocki @ 2026-05-19 14:08 UTC (permalink / raw)
To: Nick
Cc: Rafael J. Wysocki, regressions, linux-acpi, linux-kernel,
linux-pm, todd.e.brandt, xi.pardee, platform-driver-x86, stable
On Tue, May 12, 2026 at 7:16 PM Nick <nick@kousu.ca> wrote:
>
> My Toshiba Tecra X40 laptop's function keys no longer send events.
>
> Specifically the mute ("KEY_MUTE"), lock ("KEY_COFFEE"), "power plan"
> ("KEY_BATTERY"), sleep ("KEY_SLEEP"), mic mute (for some reason this
> reads as "KEY_SUSPEND"), screen switch ("KEY_SWITCHVIDEOMODE"),
> brightness ("KEY_BRIGHTNESSDOWN" and "KEY_BRIGHTNESSUP"), and rfkill
> ("KEY_WLAN") hotkeys -- these are the Fn-shifted versions of Esc, F1,
> F2, F3, F4, F5, F6, F7 and F8 -- keys no longer work. Neither does the
> lid-switch.
>
> Fn+F9, Fn+10, Fn+F11 and Fn+12 still work; those show up on
> /dev/input/event3 like the rest of my keyboard, but the hotkeys show up
> on /dev/input/event6.
>
> I'm on ArchLinux. My keys worked on v6.19.14, I first noticed them
> broken on v7.0.2.
>
> I bisected mainline and found the break is: "ACPI: scan: Use
> acpi_setup_gpe_for_wake() for buttons"
> <https://lore.kernel.org/all/2259694.irdbgypaU6@rafael.j.wysocki/>.
> That is, 57c31e6d620f132dcf610b2c52b4cdbd203c6f4a is bad and
> 88fad6ce090b395af4c654594a54589a386bf24b is good.
>
> #regzbot introduced: 57c31e6d620f132dcf610b2c52b4cdbd203c6f4a
>
> Maybe acpi_mark_gpe_for_wake was initializing something particular to
> Toshiba hardware?
Thanks for reporting!
I think that the problem is acpi_setup_gpe_for_wake() doing too much,
I'll send you a patch to test later today.
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: [REGRESSION] Toshiba Fn keys + lidswitch
2026-05-19 14:08 ` Rafael J. Wysocki
@ 2026-05-19 17:15 ` Rafael J. Wysocki
2026-05-19 17:26 ` Nick
2026-05-31 15:25 ` John Veness
2026-05-30 12:19 ` John Veness
1 sibling, 2 replies; 13+ messages in thread
From: Rafael J. Wysocki @ 2026-05-19 17:15 UTC (permalink / raw)
To: Nick; +Cc: Rafael J. Wysocki, regressions, linux-acpi, linux-kernel,
linux-pm
On Tuesday, May 19, 2026 4:08:36 PM CEST Rafael J. Wysocki wrote:
> On Tue, May 12, 2026 at 7:16 PM Nick <nick@kousu.ca> wrote:
> >
> > My Toshiba Tecra X40 laptop's function keys no longer send events.
> >
> > Specifically the mute ("KEY_MUTE"), lock ("KEY_COFFEE"), "power plan"
> > ("KEY_BATTERY"), sleep ("KEY_SLEEP"), mic mute (for some reason this
> > reads as "KEY_SUSPEND"), screen switch ("KEY_SWITCHVIDEOMODE"),
> > brightness ("KEY_BRIGHTNESSDOWN" and "KEY_BRIGHTNESSUP"), and rfkill
> > ("KEY_WLAN") hotkeys -- these are the Fn-shifted versions of Esc, F1,
> > F2, F3, F4, F5, F6, F7 and F8 -- keys no longer work. Neither does the
> > lid-switch.
> >
> > Fn+F9, Fn+10, Fn+F11 and Fn+12 still work; those show up on
> > /dev/input/event3 like the rest of my keyboard, but the hotkeys show up
> > on /dev/input/event6.
> >
> > I'm on ArchLinux. My keys worked on v6.19.14, I first noticed them
> > broken on v7.0.2.
> >
> > I bisected mainline and found the break is: "ACPI: scan: Use
> > acpi_setup_gpe_for_wake() for buttons"
> > <https://lore.kernel.org/all/2259694.irdbgypaU6@rafael.j.wysocki/>.
> > That is, 57c31e6d620f132dcf610b2c52b4cdbd203c6f4a is bad and
> > 88fad6ce090b395af4c654594a54589a386bf24b is good.
> >
> > #regzbot introduced: 57c31e6d620f132dcf610b2c52b4cdbd203c6f4a
> >
> > Maybe acpi_mark_gpe_for_wake was initializing something particular to
> > Toshiba hardware?
>
> Thanks for reporting!
>
> I think that the problem is acpi_setup_gpe_for_wake() doing too much,
> I'll send you a patch to test later today.
So please let me know if the patch below fixes the problem for you.
In either case, please grep the dmesg output for "ACPI GPE" and let me know
the result.
Thanks!
---
drivers/acpi/scan.c | 25 +++++++++++++++++++++----
1 file changed, 21 insertions(+), 4 deletions(-)
--- a/drivers/acpi/scan.c
+++ b/drivers/acpi/scan.c
@@ -1000,11 +1000,15 @@ static int acpi_bus_extract_wakeup_devic
return err;
}
+/* Do not use a button for S5 wakeup */
+#define ACPI_AVOID_WAKE_FROM_S5 BIT(0)
+
static bool acpi_wakeup_gpe_init(struct acpi_device *device)
{
static const struct acpi_device_id button_device_ids[] = {
- {"PNP0C0D", 0}, /* Lid */
- {"PNP0C0E", 0}, /* Sleep button */
+ {"PNP0C0C", 0}, /* Power button */
+ {"PNP0C0D", ACPI_AVOID_WAKE_FROM_S5}, /* Lid */
+ {"PNP0C0E", ACPI_AVOID_WAKE_FROM_S5}, /* Sleep button */
{"", 0},
};
struct acpi_device_wakeup *wakeup = &device->wakeup;
@@ -1014,8 +1018,21 @@ static bool acpi_wakeup_gpe_init(struct
wakeup->flags.notifier_present = 0;
match = acpi_match_acpi_device(button_device_ids, device);
- if (match && wakeup->sleep_state == ACPI_STATE_S5)
- wakeup->sleep_state = ACPI_STATE_S4;
+ if (match) {
+ acpi_event_status gpe_status = 0;
+
+ if (wakeup->sleep_state == ACPI_STATE_S5 &&
+ match->driver_data == ACPI_AVOID_WAKE_FROM_S5)
+ wakeup->sleep_state = ACPI_STATE_S4;
+
+ acpi_get_gpe_status(wakeup->gpe_device, wakeup->gpe_number,
+ &gpe_status);
+ if (gpe_status & ACPI_EVENT_FLAG_ENABLE_SET) {
+ acpi_enable_gpe(wakeup->gpe_device, wakeup->gpe_number);
+ dev_info(&device->dev, "ACPI GPE enabled for %s\n",
+ (char *)match->id);
+ }
+ }
status = acpi_setup_gpe_for_wake(device->handle, wakeup->gpe_device,
wakeup->gpe_number);
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: [REGRESSION] Toshiba Fn keys + lidswitch
2026-05-19 17:15 ` Rafael J. Wysocki
@ 2026-05-19 17:26 ` Nick
2026-05-31 15:25 ` John Veness
1 sibling, 0 replies; 13+ messages in thread
From: Nick @ 2026-05-19 17:26 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Rafael J. Wysocki, regressions, linux-acpi, linux-kernel,
linux-pm
On May 19, 2026 5:15:13 p.m. UTC, "Rafael J. Wysocki" <rafael@kernel.org> wrote:
>On Tuesday, May 19, 2026 4:08:36 PM CEST Rafael J. Wysocki wrote:
>> On Tue, May 12, 2026 at 7:16 PM Nick <nick@kousu.ca> wrote:
>> >
>> > My Toshiba Tecra X40 laptop's function keys no longer send events.
>> >
>> > #regzbot introduced: 57c31e6d620f132dcf610b2c52b4cdbd203c6f4a
>> >
>> > Maybe acpi_mark_gpe_for_wake was initializing something particular to
>> > Toshiba hardware?
>>
>> Thanks for reporting!
>>
>> I think that the problem is acpi_setup_gpe_for_wake() doing too much,
>> I'll send you a patch to test later today.
>
>So please let me know if the patch below fixes the problem for you.
Excellent! Thank you, I'll be able to try it soon, just as soon as I don't need my laptop functional.
- kousu
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [REGRESSION] Toshiba Fn keys + lidswitch
2026-05-19 17:15 ` Rafael J. Wysocki
2026-05-19 17:26 ` Nick
@ 2026-05-31 15:25 ` John Veness
1 sibling, 0 replies; 13+ messages in thread
From: John Veness @ 2026-05-31 15:25 UTC (permalink / raw)
To: Rafael J. Wysocki, Nick
Cc: Rafael J. Wysocki, regressions, linux-acpi, linux-kernel,
linux-pm, platform-driver-x86
On 19/05/2026 18:15, Rafael J. Wysocki wrote:
> So please let me know if the patch below fixes the problem for you.
>
> In either case, please grep the dmesg output for "ACPI GPE" and let me know
> the result.
>
> Thanks!
Hi Rafael, thanks for the quick patch! I'm not Nick, but I have tested
the patch here on my old Toshiba Tecra Z50-A and it seems to have worked
- I now have Fn+keys working fine, after losing them in a recent kernel
update (apart from Fn+3 for volume down, and Fn+4 for volume up, which
for some reason continued to work when the others didn't).
dmesg|grep "ACPI GPE" since applying the patch gives:
[ 0.197248] [ T1] acpi (null): ACPI GPE enabled for PNP0C0C
John
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [REGRESSION] Toshiba Fn keys + lidswitch
2026-05-19 14:08 ` Rafael J. Wysocki
2026-05-19 17:15 ` Rafael J. Wysocki
@ 2026-05-30 12:19 ` John Veness
2026-05-30 13:34 ` johannes.goede
1 sibling, 1 reply; 13+ messages in thread
From: John Veness @ 2026-05-30 12:19 UTC (permalink / raw)
To: Rafael J. Wysocki, Nick
Cc: Rafael J. Wysocki, regressions, linux-acpi, linux-kernel,
linux-pm, todd.e.brandt, xi.pardee, platform-driver-x86, stable
On 19/05/2026 15:08, Rafael J. Wysocki wrote:
> Thanks for reporting!
>
> I think that the problem is acpi_setup_gpe_for_wake() doing too much,
> I'll send you a patch to test later today.
Hi, can you release the test patch publicly? I'd like to test it here,
as I have several Toshiba laptops whose Fn+keys don't work (apart from
vol+/vol-).
John
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [REGRESSION] Toshiba Fn keys + lidswitch
2026-05-30 12:19 ` John Veness
@ 2026-05-30 13:34 ` johannes.goede
2026-05-31 15:17 ` John Veness
0 siblings, 1 reply; 13+ messages in thread
From: johannes.goede @ 2026-05-30 13:34 UTC (permalink / raw)
To: John Veness, Rafael J. Wysocki, Nick
Cc: Rafael J. Wysocki, regressions, linux-acpi, linux-kernel,
linux-pm, todd.e.brandt, xi.pardee, platform-driver-x86, stable
Hi John,
On 30-May-26 14:19, John Veness wrote:
> On 19/05/2026 15:08, Rafael J. Wysocki wrote:
>> Thanks for reporting!
>>
>> I think that the problem is acpi_setup_gpe_for_wake() doing too much,
>> I'll send you a patch to test later today.
>
> Hi, can you release the test patch publicly? I'd like to test it here,
> as I have several Toshiba laptops whose Fn+keys don't work (apart from
> vol+/vol-).
In case you've not seen it yet, Rafael send out the test patch
publicly later that day in another email in this thread:
https://lore.kernel.org/linux-acpi/12896447.O9o76ZdvQC@rafael.j.wysocki/
Regards,
Hans
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [REGRESSION] Toshiba Fn keys + lidswitch
2026-05-30 13:34 ` johannes.goede
@ 2026-05-31 15:17 ` John Veness
2026-05-31 20:29 ` Nick
0 siblings, 1 reply; 13+ messages in thread
From: John Veness @ 2026-05-31 15:17 UTC (permalink / raw)
To: johannes.goede, Rafael J. Wysocki, Nick
Cc: Rafael J. Wysocki, regressions, linux-acpi, linux-kernel,
linux-pm, todd.e.brandt, xi.pardee, platform-driver-x86, stable
On 30/05/2026 14:34, johannes.goede@oss.qualcomm.com wrote:
> In case you've not seen it yet, Rafael send out the test patch
> publicly later that day in another email in this thread:
>
> https://lore.kernel.org/linux-acpi/12896447.O9o76ZdvQC@rafael.j.wysocki/
>
> Regards,
>
> Hans
Thanks for the pointer, and sorry for missing that! I had only been
looking in the archives of platform-driver-x86@vger.kernel.org which for
some reason didn't receive the patch.
John
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [REGRESSION] Toshiba Fn keys + lidswitch
2026-05-31 15:17 ` John Veness
@ 2026-05-31 20:29 ` Nick
2026-06-01 12:12 ` Rafael J. Wysocki
0 siblings, 1 reply; 13+ messages in thread
From: Nick @ 2026-05-31 20:29 UTC (permalink / raw)
To: linux-acpi
Cc: johannes.goede, Rafael J. Wysocki, Rafael J. Wysocki, regressions,
John Veness, linux-kernel, linux-pm, platform-driver-x86, stable
On 2026-05-31 11:17, John Veness wrote:
> On 30/05/2026 14:34, johannes.goede@oss.qualcomm.com wrote:
>> In case you've not seen it yet, Rafael send out the test patch
>> publicly later that day in another email in this thread:
>>
>> https://lore.kernel.org/linux-acpi/12896447.O9o76ZdvQC@rafael.j.wysocki/
>>
>> Regards,
>>
>> Hans
>
> Thanks for the pointer, and sorry for missing that! I had only been
> looking in the archives of platform-driver-x86@vger.kernel.org which
> for
> some reason didn't receive the patch.
>
> John
On 2026-05-31 11:25, John Veness wrote:
> I'm not Nick, but I have tested the patch here on my old Toshiba Tecra
> Z50-A
> and it seems to have worked - I now have Fn+keys working fine, after
> losing them
> in a recent kernel update (apart from Fn+3 for volume down, and Fn+4
> for volume up,
> which for some reason continued to work when the others didn't).
>
> John
Same here. All my Fn keys work except for Esc through F8. Glad Rafael's
patch worked for you too! There's a newer copy of it at
https://lore.kernel.org/linux-acpi/2046403.PYKUYFuaPT@rafael.j.wysocki/T/#t
by the way.
- Nick
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [REGRESSION] Toshiba Fn keys + lidswitch
2026-05-31 20:29 ` Nick
@ 2026-06-01 12:12 ` Rafael J. Wysocki
2026-06-02 18:21 ` Sasha Levin
0 siblings, 1 reply; 13+ messages in thread
From: Rafael J. Wysocki @ 2026-06-01 12:12 UTC (permalink / raw)
To: Nick, John Veness
Cc: linux-acpi, johannes.goede, Rafael J. Wysocki, regressions,
linux-kernel, linux-pm, platform-driver-x86, stable
On Sun, May 31, 2026 at 10:35 PM Nick <nick@kousu.ca> wrote:
>
> On 2026-05-31 11:17, John Veness wrote:
> > On 30/05/2026 14:34, johannes.goede@oss.qualcomm.com wrote:
> >> In case you've not seen it yet, Rafael send out the test patch
> >> publicly later that day in another email in this thread:
> >>
> >> https://lore.kernel.org/linux-acpi/12896447.O9o76ZdvQC@rafael.j.wysocki/
> >>
> >> Regards,
> >>
> >> Hans
> >
> > Thanks for the pointer, and sorry for missing that! I had only been
> > looking in the archives of platform-driver-x86@vger.kernel.org which
> > for
> > some reason didn't receive the patch.
> >
> > John
>
> On 2026-05-31 11:25, John Veness wrote:
> > I'm not Nick, but I have tested the patch here on my old Toshiba Tecra
> > Z50-A
> > and it seems to have worked - I now have Fn+keys working fine, after
> > losing them
> > in a recent kernel update (apart from Fn+3 for volume down, and Fn+4
> > for volume up,
> > which for some reason continued to work when the others didn't).
> >
> > John
>
> Same here. All my Fn keys work except for Esc through F8. Glad Rafael's
> patch worked for you too! There's a newer copy of it at
> https://lore.kernel.org/linux-acpi/2046403.PYKUYFuaPT@rafael.j.wysocki/T/#t
> by the way.
Thank you both for testing!
The patch is there in 7.1-rc6, so it should propagate to -stable
kernels over time.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [REGRESSION] Toshiba Fn keys + lidswitch
2026-06-01 12:12 ` Rafael J. Wysocki
@ 2026-06-02 18:21 ` Sasha Levin
0 siblings, 0 replies; 13+ messages in thread
From: Sasha Levin @ 2026-06-02 18:21 UTC (permalink / raw)
To: Nick, John Veness, Rafael J. Wysocki
Cc: Sasha Levin, linux-acpi, johannes.goede, Rafael J. Wysocki,
regressions, linux-kernel, linux-pm, platform-driver-x86, stable
On Mon, Jun 01, 2026 at 02:12:50PM +0200, Rafael J. Wysocki wrote:
> The patch is there in 7.1-rc6, so it should propagate to -stable kernels
> over time.
I've queued the fix for 7.0.y now rather than waiting:
a004b8f0d3bc5d ("ACPI: button: Enable wakeup GPEs for ACPI buttons at probe time")
along with its prerequisite:
fe80251152fed5 ("ACPI: button: Fix ACPI GPE handler leak during removal")
--
Thanks,
Sasha
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2026-06-02 18:21 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-05-12 16:49 [REGRESSION] Toshiba Fn keys + lidswitch Nick
2026-05-19 8:55 ` Thorsten Leemhuis
2026-05-19 11:48 ` Rafael J. Wysocki
2026-05-19 14:08 ` Rafael J. Wysocki
2026-05-19 17:15 ` Rafael J. Wysocki
2026-05-19 17:26 ` Nick
2026-05-31 15:25 ` John Veness
2026-05-30 12:19 ` John Veness
2026-05-30 13:34 ` johannes.goede
2026-05-31 15:17 ` John Veness
2026-05-31 20:29 ` Nick
2026-06-01 12:12 ` Rafael J. Wysocki
2026-06-02 18:21 ` Sasha Levin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox