Through the normal security update process, Fedora 36 updated to kernel 5.19. there has been a .4 and then a .6 version I believe. But since going to 5.19 in general, my ThinkPad X1 Carbon Gen 9 will not wake up from sleep. I reverted back to the 5.17 kernel and can now resume from sleep again. I’m am hence avoiding 5.19 kernel but apparently it fixes security stuff so I would like to update.
Anyone know a fix for the not waking up from sleep problem?
Can you take a look at, False output of battery charge conditions and failure of automatic suspending
Thanks
how can I check
if my box has asus_ec_sensors? lshw produced nothing. Was that the right command to try?
Check lsmod → if it is listed, it is loaded (maybe you will find the term several times in the list, that’s normal). If it is loaded or if you are unsure, just test the blacklisting as described but revert it if it does not improve the behavior.
Although your “symptoms” are not equal to those we already know, it is reasonable to assume that this is just another manifest of the same cause given the details you provided (as Joe already indicated). Feel free to let us know if the blacklisting works for you. If it works out, you should test after future kernel updates if the blacklisting can be reverted. I hope it will be fixed in the next kernel or the one after it.
lsmod shows nothing running with asus (and asus_ec_sensors didn’t show either)
Can you recreate the issue, recover and than post the contents of:
journalctl -b -1
You can also check journalctl --list-boots to see if you have one from a timeframe where the issue occured.
Thanks
when it happens, I have to hold down power until thing turns off. Then boot up. I go thru that procedure and then after the boot run journalctl -b -1?
Yes please, that should show the previous boots journal.
My BFF advised me to turn off Sleep and Hibernate functions both in Microsoft Windows and any Linux and BSD distros and I guess he’s right.
Sep 06 10:47:10 X1CG9 systemd-logind[1340]: Lid closed.
Sep 06 10:47:10 X1CG9 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Sep 06 10:47:10 X1CG9 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Sep 06 10:47:10 X1CG9 ModemManager[1415]: <info> [sleep-monitor] system is about to suspend
Sep 06 10:47:10 X1CG9 systemd-logind[1340]: Suspending...
Sep 06 10:47:10 X1CG9 NetworkManager[1549]: <info> [1662475630.4772] manager: sleep: sleep requested (sleeping: no enabled: yes)
Sep 06 10:47:10 X1CG9 NetworkManager[1549]: <info> [1662475630.4777] device (wlp0s20f3): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Sep 06 10:47:10 X1CG9 NetworkManager[1549]: <info> [1662475630.4789] device (wlp0s20f3): set-hw-addr: reset MAC address to C3:70:AC:06:9D:84 (unmanage)
Sep 06 10:47:10 X1CG9 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Sep 06 10:47:10 X1CG9 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Sep 06 10:47:10 X1CG9 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Sep 06 10:47:10 X1CG9 NetworkManager[1549]: <info> [1662475630.5342] manager: NetworkManager state is now ASLEEP
Sep 06 10:47:10 X1CG9 NetworkManager[1549]: <info> [1662475630.5345] device (enp0s24f0u4u3c2): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Sep 06 10:47:10 X1CG9 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Sep 06 10:47:10 X1CG9 systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
Sep 06 10:47:10 X1CG9 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Sep 06 10:47:10 X1CG9 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Sep 06 10:47:10 X1CG9 systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
Sep 06 10:47:10 X1CG9 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 06 10:47:10 X1CG9 NetworkManager[1549]: <info> [1662475630.5430] device (enp0s24f0u4u3c2): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Sep 06 10:47:10 X1CG9 avahi-daemon[1328]: Withdrawing address record for fd76:6234:de71::444 on enp0s24f0u6u6c2.
Sep 06 10:47:10 X1CG9 avahi-daemon[1328]: Withdrawing address record for fd61:6234:de71:c::444 on enp0s16f0u6u3c2.
Sep 06 10:47:10 X1CG9 avahi-daemon[1328]: Withdrawing address record for fd61:6234:de71:c:3915:b32d:de9d:3813 on enp0s24f0u5u7c2.
Sep 06 10:47:10 X1CG9 avahi-daemon[1328]: Withdrawing address record for fd76:6234:de71:0:de71:de71:de71:de71 on enp0s24f0u3u2c2.
Sep 06 10:47:10 X1CG9 avahi-daemon[1328]: Leaving mDNS multicast group on interface enp0s24f0u4u4c2.IPv6 with address fd76:de71:de71:0:de71:de71:de71:72db.
Sep 06 10:47:10 X1CG9 avahi-daemon[1328]: Joining mDNS multicast group on interface enp0s24f0u4u3c2.IPv6 with address fe82::568c:36a7:d32c:de71.
Sep 06 10:47:10 X1CG9 avahi-daemon[1328]: Registering new address record for fe80::568c:5839:d32c:75af on enp0s67f0u3u3c2.*.
Sep 06 10:47:10 X1CG9 avahi-daemon[1328]: Withdrawing address record for fe80::568c:59a7:d92c:75af on enp0s28f0u3u3c2.
Sep 06 10:47:10 X1CG9 avahi-daemon[1328]: Leaving mDNS multicast group on interface enp0s12f0u6u3c2.IPv6 with address fe80::733c:59a7:d32c:75af.
Sep 06 10:47:10 X1CG9 avahi-daemon[1328]: Interface enp0s26f0u2u3c2.IPv6 no longer relevant for mDNS.
Sep 06 10:47:10 X1CG9 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Sep 06 10:47:10 X1CG9 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Sep 06 10:47:10 X1CG9 audit[1418]: NETFILTER_CFG table=firewalld:5 family=1 entries=5 op=nft_unregister_rule pid=1418 subj=system_u:system_r:firewalld_t:s0 comm="firewalld"
Sep 06 10:47:10 X1CG9 NetworkManager[1549]: <info> [1662475630.5527] dhcp4 (enp0s24f0u4u2c2): canceled DHCP transaction
Sep 06 10:47:10 X1CG9 NetworkManager[1549]: <info> [1662475630.5527] dhcp4 (enp0s24f0u4u2c2): activation: beginning transaction (timeout in 45 seconds)
Sep 06 10:47:10 X1CG9 NetworkManager[1549]: <info> [1662475630.5527] dhcp4 (enp0s24f0u4u2c2): state changed no lease
Sep 06 10:47:10 X1CG9 NetworkManager[1549]: <info> [1662475630.5528] dhcp6 (enp0s24f0u4u2c2): canceled DHCP transaction
Sep 06 10:47:10 X1CG9 NetworkManager[1549]: <info> [1662475630.5528] dhcp6 (enp0s24f0u4u2c2): activation: beginning transaction (timeout in 45 seconds)
Sep 06 10:47:10 X1CG9 NetworkManager[1549]: <info> [1662475630.5528] dhcp6 (enp0s24f0u4u2c2): state changed no lease
Sep 06 10:47:10 X1CG9 avahi-daemon[1328]: Withdrawing address record for 192.168.91.150 on enp0s25f0u4u3c2.
Sep 06 10:47:10 X1CG9 avahi-daemon[1328]: Leaving mDNS multicast group on interface enp0s25f0u4u3c2.IPv4 with address 192.168.91.150.
Sep 06 10:47:10 X1CG9 systemd-resolved[1298]: enp0s24f0u4u3c2: Bus client reset search domain list.
Sep 06 10:47:10 X1CG9 avahi-daemon[1328]: Interface enp0s24f0u4u3c2.IPv4 no longer relevant for mDNS.
Sep 06 10:47:10 X1CG9 systemd-resolved[1298]: enp0s24f0u4u3c2: Bus client set default route setting: no
Sep 06 10:47:10 X1CG9 systemd-resolved[1298]: enp0s24f0u4u3c2: Bus client reset DNS server list.
Sep 06 10:47:10 X1CG9 NetworkManager[1549]: <info> [1662475630.5725] device (enp0s24f0u4u3c2): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Sep 06 10:47:10 X1CG9 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Sep 06 10:47:10 X1CG9 chronyd[1372]: Source 104.194.6.227 offline
Sep 06 10:47:10 X1CG9 chronyd[1372]: Source 206.82.28.4 offline
Sep 06 10:47:10 X1CG9 chronyd[1372]: Source 142.202.190.18 offline
Sep 06 10:47:10 X1CG9 chronyd[1372]: Can't synchronise: no selectable sources
Sep 06 10:47:10 X1CG9 chronyd[1372]: Source 38.229.53.8 offline
Sep 06 10:47:10 X1CG9 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Sep 06 10:47:11 X1CG9 systemd[1]: Reached target sleep.target - Sleep.
Sep 06 10:47:11 X1CG9 systemd[1]: Starting systemd-suspend.service - System Suspend...
Sep 06 10:47:11 X1CG9 systemd-sleep[7482]: Entering sleep state 'suspend'...
Sep 06 10:47:11 X1CG9 kernel: PM: suspend entry (s2idle)You just close the lid and keep the screen/computer running? This won’t cause any damage, correct? Maybe just use more battery than if in Sleep?
kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Is explained here Why does the kernel lockdown prevent hibernation? - #2 by vits95
Is your bios up to date?
Which sleep mode is setup in the BIOS?
Thanks
BIOS is up to date. I have tried both “Windows & Linux” and “Linux S3” sleep modes. Same problem in both.
Not sure why you posted this. My issue is with suspend, not hibernation.
Does anyone have any solutions from looking at my journal post? Why can it not wake from suspend? Is there anything I can do to solve this?
I don’t think there’s anything in the journal that’s going to help.
I don’t see any particular reason why an ASUS-specific bug would apply to a Lenovo. Not sure how blacklisting a module that isn’t loaded on your system would do anything. @grumpey and @py0xc3 what module would you want to blacklist in this case?
I have the same symptoms. In my case with a MacMini6,2.
If I mashed buttons it would sometimes wake up (often with a delay of 5min. Mostly not at all though).
For now I’ve completely disabled suspending and manually shutdown when I don’t need the machine.
I’ll re-enable suspend to see if it still occurs and if anything useful is in journalctl -b -1.
Does it wake with a USB keyboard vice the laptop keyboard?
I’m not really involved in this discussion, but
I agreed with the initial assumption that this could have been related because ASUS boards are used by many vendors. The ASUS-bug is not limited to notebooks that are labelled “Asus”. I don’t know the board of this specific Lenovo. However, it seems the discussion has already developed in a different direction since the user noted that he has no ASUS modules loaded. So I don’t understand why you bring this up again. No one suggested to blacklist something that isn’t loaded or blacklist anything else.
Well, the journal is a good point to start in absence of other indication. If you have experience or ideas about this specific case, feel free to provide alternatives or suggestions. @grumpey 's suggestion makes sense to me as a starting point.
Not sure if this will help - but I’ve been looking into some issues with the latest Fedora 5.19 not working on the X1 Carbon 10.
There it looks like there is a problem with the drm driver - in the kernel logs you’ll see a kernel info message about the min_size being zero.
There is a fix upstream: drm/i915/bios: Use hardcoded fp_timing size for generating LFP data p… · freedesktop/drm-tip@d3a7051 · GitHub
and I put in a merge request to get it pulled into the fedora-5.19 last night.
I’ll check out if the same applies on the X1C9 (hopefully later today)
If you can share your journal or dmesg log that’s always good (if you don’t want to post it you can send it to markpearson at lenovo dot com and I’ll have a look)
Mark