[Bug 221383] ideapad_laptop: Fn hotkeys stop emitting after s2idle resume on IdeaPad Slim 3 14ARP10 (Ryzen 7735HS)

[bugzilla-daemon@kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=221383

--- Comment #22 from Daniel Gibson (metalcaedes@gmail.com) ---
Alright, thanks :)

So here a longer post about what I'm seeing on my machine.
Note that unlike Sindre I see these issues even if the laptop has only been
suspended for a few seconds (I always wait until an indicator LED on the side
starts flashing instead of being on constantly).

After booting or rebooting the system, everything works as expected: The F-keys
do their thing (mute audio or whatever), when combining them with Fn they
behave like normal F1, F2 and so on and the lid switch also works, so when
closing the laptop it suspends (when configured that way).

However after suspend+resume, the keyboard doesn't work anymore, and neither
does the lid switch.
Running `echo i8042 | sudo tee /sys/bus/platform/drivers/i8042/unbind`
and then `echo i8042 | sudo tee /sys/bus/platform/drivers/i8042/bind`
makes the keyboard mostly work again, except that the Fn keys don't work as
intended (pressing F1 and Fn+F1 both report plain F1, not Mute) and the lid
switch still doesn't work.

Adding "i8042.nopnp" to the kernel commandline helps a bit: When it's set the
keyboard works after suspend+resume without unbinding/rebinding it, but the
Fn-keys and the lid switch are broken after resuming, just like before.


In dmesg I noticed a message "ACPI BIOS Error (bug): Could not resolve symbol
[\_SB.PC00.LPCB.EC0.SNTM], AE_NOT_FOUND (20230628/psargs-330)" during wakeup.
After decompiling the ACPI tables the I saw that this indeed doesn't exist, but
"\_SB.PCI0.LPC0.EC0.SNTM" does, so I patched the call accordingly. Didn't seem
to make a difference, though, apart from getting rid of that ACPI BIOS Error. 


When I tried to run `amd-s2idle test`, it refused because "GPIO interrupt is
not served" It suggests loading the i2c-hid-acpi kernel module, but it was
already loaded.
So I checked `/sys/kernel/debug/gpio` and it contained the line

> #89   🔥 😷|     ↓|  level|    |   |     |  |    |  ↓ |input  ↓|        
> |0x10240b00

Apparently that fire emoji means that this GPIO interrupt is not served (it's
the only line with fire).
`gpioset -c gpiochip0 -p 2m 89=1` makes that issue temporarily go away and
allows running amd-s2idle.

GPIO Line 89 seems to belong to the touchpad, when setting dyndbg='module
pinctrl_amd +p' I get lots of lines like
[   25.273930] GPIO 9 is active: 0x10141b00
[   25.273967] GPIO 89 is active: 0x10240b00
[   25.280561] GPIO 9 is active: 0x10141b00
[   25.280585] GPIO 89 is active: 0x10240b00
in dmesg whenever I touch the touchpad.


Rarely they keys and lid switch still work after resume, usually in that case
there's a message like
[   54.421557] amd_pmc AMDI0005:00: Last suspend didn't reach deepest state
in dmesg. When that happens the next suspends behave the same (and still yield
the message), until rebooting.

Once or twice things "worked" without showing that "didn't reach deepest state"
message; unfortunately in those cases I didn't check power consumption on the
wattmeter the laptop's power adapter is plugged into, so I can't say if it was
a proper suspend or not.

I attached a lot of stuff, run with Kernel 7.0 from Ubuntu's mainline repo (my
own build has lots of changes for additional debugprints by now) and mostly
with unpatched (original) ACPI tables, except for
dg-16ABR8-dmesg_patched_acpi.txt and lshw which are with the patched ACPI table
to get rid of the aforementioned "ACPI BIOS Error".
dg-16ABR8-ssdt14-mod.dsl is the source of the modified ACPI table.


Is there any more information I can provide, or things I could try?

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.