Bug 2080742

Summary: Cannot wake from sleep with laptop internal keyboard and power button.
Product: [Fedora] Fedora Reporter: ho121 <3548216>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 35CC: acaringi, adscvr, airlied, alciregi, bskeggs, hdegoede, hpa, jarodwilson, jglisse, jonathan, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, ptalbert, richard, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-13 17:53:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
journalctl --no-hostname -k > dmesg.txt none

Description ho121 2022-05-01 13:12:35 UTC 
Created attachment 1876330 [details]
journalctl --no-hostname -k > dmesg.txt

1. Please describe the problem:

Cannot wake from sleep with laptop internal keyboard and power button.
But can wake from sleep by plugging or unplugging the power cable.

2. What is the Version-Release number of the kernel:

`5.17.4-200.fc35.x86_64`

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

Yes, it did work. I don't remember exactly when this issue starts happening.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

It produces every time.

First, suspend the machine, either by `Suspend` button in the GNOME UI, or by `systemctl suspend`.

Second, try to wake. Keyboard and power button don't work, and the power light is still flashing.
But plugging or unplugging the power cable can wake the machine normally.

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

Sorry, I'm not able to test that.

6. Are you running any modules that not shipped with directly Fedora's kernel?:

Perhaps no. I don't have nvidia.

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

See attachments.

And I think these things may help:

# cat /proc/acpi/wakeup
Device	S-state	 Status   Sysfs node
GPP0	 S4	*disabled
GPP1	 S4	*disabled
GP17	 S4	*enabled   pci:0000:00:08.1
Comment 1 ho121 2022-05-02 11:00:11 UTC 
I tested an earlier version kernel. Kernel 5.16.18-200.fc35.x86_64 doesn't have this issue.
Comment 2 Richard Connon 2022-05-02 11:45:38 UTC 
I have experienced the same issue.

I'm on a ThinkPad T14 Gen 2a

For me the issue did not occur with kernel 5.16.19-200.fc35 and began occuring with 5.17.4-200.fc35
It does not occur with the latest rawhide kernel 5.18.0-0.rc4.20220429git38d741cb70b3074.37.fc37
I also tested some kernels from the kernel-vanilla-fedora repo, and experienced the issue with vmlinuz-5.17.4-250.vanilla.1.fc35 but not with vmlinuz-5.17.5-250.vanilla.1.fc35

It seems likely, based on this, that this is an upstream regression in 5.17 that has a fix in 5.18 and 5.17.5
Comment 3 Ben Cotton 2022-11-29 18:51:02 UTC 
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.
Comment 4 Ben Cotton 2022-12-13 17:53:22 UTC 
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.