Freeze after wake from suspend

Ask Fedora
, ,
1

Hi there,

in two out of three cases my laptop does not wake from suspend. there are two different symptoms: I wake the device and the screen stays black or the login prompt appears, but I can not move the mouse or use the keyboard and the time of the moment I put it to suspend shows.

I have onboard graphics from intel so it is no nvidia issue.
I tried changing /sys/power/mem_sleep from deep to s2idle, but could not change the file even using su.

I have read about using acpitool and test disabling all the devices. But since there are seven of them and the issue does not occur on every wake up, I dont really like that approach.

I am running Fedora 36 KDE, Kernel 5.19.7-200.

2

  1. Do you have the problem as well when you boot with 5.19.6 and 5.19.4 ? You should have both in your grub menu at booting.
    → If the issue does not appear on 5.19.6, you can consider to stick with 5.19.6 until there is a new release. So, “jump over” 5.19.7 → the update from 5.19.6 to 5.19.7 is not security critical, and it is likely that there will be acpi-relevant changes in the next kernel.

  2. What is the output of cat /proc/sys/kernel/tainted ? This tells us if there are modifications on your kernel. The output is just a number. An unmodified kernel is 0.

  3. What is the output of lsmod | grep asus ? I would like to exclude that this is linked to the current issue we have with an asus module that is not yet fixed but will be soon. If that will be the case, we have a workaround for that, but let’s check first.

→ if 5.19.6 works fine and if you are ok with waiting for the next kernel, or if “lsmod | grep asus” outputs anything, you can wait with the next steps and just let us know what you have so far. Otherwise:

  1. Create a boot that is only dedicated to create relevant logs. So, boot your 5.19.7 kernel and after booting, just log in, provoke the problem, and once your system got stuck, force reset and at the next boot, let us know the output of sudo journalctl --boot=-1 → this shows the logs of the last boot (which is then the affected boot). Feel free to randomize data if you consider something contained as private (e.g., MAC address, user name). Also, it would be helpful if you could let us know the very time when you suspended (that helps when reading the logs) and what exact symptoms you had at this occurrence.

  2. If you don’t mind installing inxi (it is contained in the default repo of Fedora), inxi -Fz would be valuable complementary information (“-F” = all system information, “-z” = keep private information hidden). Feel free to check if there is anything left you consider private, but let us know if you change the output of it.

  3. acpitool can be helpful to identify the exact device that causes the problem (if one specific device is responsible), which can help to identify a driver/module/code that could be changed/modified to solve the issue. So disabling them one by one (so, always just one disabled), and each time testing if the problem can be provoked. This might safe time.

3

Hi @py0xc3,
thx for the support!

  1. I am experiencing the freeze problem for weeks now and always hoped the next Kernel would solve the issue, but did not. It makes no difference whether I am on 5.19.7, 5.19.6 or 5.19.4.

  2. The output of cat /proc/sys/kernel/tainted is 12288

  3. The output of lsmod | grep asus is empty

3.b

output of journalctl --boot=-1

https://zerobin.net/?8242342a5656670d#tm8Tba+9ovCBoHwvdDtpukbH/xLjoCufhUBisuV8ims=

I suspended at 3 in the morning (line 3631) right after I started the thread.

output of inxi -Fz

inxi -Fz - Pastebin.com

  1. not yet tested.
4

Well, your kernel is modified in multiple ways (“An out-of-tree module has been loaded” + “An unsigned module has been loaded in a kernel supporting module signature”): stuff that has not undergone our testing and quality assurance. So our starting point is the same as with nvidia, if not worse because with nvidia, many people are testing it and we can reproduce/replace much. Just updating does not change the underlying condition if it is the cause of your problem. This is complemented by services that do not belong to Fedora, such as tccd.service.

At first glance, I see two things in your logs that could be indicative:

...
Sep 10 14:29:11 ralf systemd[1]: tccd.service: Deactivated successfully.
Sep 10 14:29:11 ralf systemd[1]: Stopped tccd.service - TUXEDO Control Center Service.
...
Sep 10 14:29:11 ralf systemd[1]: tccd.service: Consumed 2min 4.821s CPU time.

This service does not belong to Fedora, but it seems to be involved in the suspending.

My suggestion would be to test disabling the service and check if this helps. As I do not know the impact of this service, my suggestion is also to prepare a Fedora live usb stick or such in advance, so that you can revert the change.

Does disabling with systemctl work? → sudo systemctl disable tccd.service; sudo systemctl enable tccd.service; sudo systemctl disable tccd.service → check & store the exact output of this command and let us know! I suggest “disable → enable → disable” to get all information at a glance that you would need in case you had to revert manually from a live system. Then, do not just use “–now” but reboot. Then: try. Feel free to check in advance the background of this service.

  1. If 1) doesn’t help:

Sep 10 14:29:11 ralf bluetoothd[838]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)

Looks like there is an issue with bluetooth at this stage. My suggestion: disable all bluetooth including the service and try again. If it does not work, check the logs to ensure that there is really nothing of bluetooth left.

Beyond, it would be interesting if you have the problem also with a default Fedora. Maybe install one on an external stick or such, boot it, update it to the recent kernel, reboot, and check if it works. Alternatively, identify and unload tainting modules (if this is possible) until the output of the tainted file is 0, and test again. And the suggestion to test disabling acpi devices one by one remains as well.

Supplement: it might be also worth to test it once without wpa_supplicant. So disable it, and then test. I don’t think it is the cause but as this one can be tested quickly anyway, we can exclude (or identify) it from the beginning.

→ My guesses for the cause are tccd.service, or an interaction of a tainting module/driver with bluetoothd.

5

Additionally to the post above: I read that the Tuxedo Control Center (related to the tccd.service) also goes along with installing drivers. I assume these are the modules that tainted your kernel, or at least some of them. Maybe you try it once completely without the TCC, so disabling the service and also ensure to unload (or blacklist) the modules temporarily. lsmod may be indicative about this.

Of course we do not yet know for sure if this is the cause of the problem (tainted does not automatically imply a problem or so), but since it has never undergone our testing/qa, and because it is related to the suspending, it is the first thing I would consider.

6

I would start with disabling tcc as well. But not using that software means the laptop sounds like an helicopter.

For now: is it enough to uninstall tcc, or do i have to reinstall the Kernel as well?

7

You don’t need to reinstall the kernel. May I ask for your output of lsmod? Before and after? And check the tainted status of your kernel after that.

Well, first we have to identify where the problem has its cause. Then, we can try to find a workaround. E.g., if there are multiple modules of TCC (one of the reasons why I ask for lsmod), there is a chance that the module that regulates your “helicopter” fan is not the same module that creates the problem.

8

lsmod before

Module                  Size  Used by
tls                   118784  0
uinput                 20480  1
rfcomm                 90112  7
snd_seq_dummy          16384  0
snd_hrtimer            16384  1
nft_objref             16384  1
nf_conntrack_netbios_ns    16384  1
nf_conntrack_broadcast    16384  1 nf_conntrack_netbios_ns
nft_fib_inet           16384  1
nft_fib_ipv4           16384  1 nft_fib_inet
nft_fib_ipv6           16384  1 nft_fib_inet
nft_fib                16384  3 nft_fib_ipv6,nft_fib_ipv4,nft_fib_inet
nft_reject_inet        16384  6
nf_reject_ipv4         16384  1 nft_reject_inet
nf_reject_ipv6         20480  1 nft_reject_inet
nft_reject             16384  1 nft_reject_inet
nft_ct                 20480  16
nft_chain_nat          16384  2
nf_nat                 57344  1 nft_chain_nat
nf_conntrack          167936  4 nf_nat,nft_ct,nf_conntrack_netbios_ns,nf_conntrack_broadcast
nf_defrag_ipv6         24576  1 nf_conntrack
nf_defrag_ipv4         16384  1 nf_conntrack
ip_set                 61440  0
nf_tables             278528  232 nft_ct,nft_reject_inet,nft_fib_ipv6,nft_objref,nft_fib_ipv4,nft_chain_nat,nft_reject,nft_fib,nft_fib_inet
nfnetlink              20480  3 nf_tables,ip_set
qrtr                   45056  4
bnep                   28672  2
sunrpc                655360  1
binfmt_misc            28672  1
vfat                   20480  1
fat                    86016  1 vfat
snd_sof_pci_intel_cnl    16384  0
snd_sof_intel_hda_common   122880  1 snd_sof_pci_intel_cnl
soundwire_intel        45056  1 snd_sof_intel_hda_common
soundwire_generic_allocation    16384  1 soundwire_intel
soundwire_cadence      36864  1 soundwire_intel
snd_sof_intel_hda      20480  1 snd_sof_intel_hda_common
snd_sof_pci            24576  2 snd_sof_intel_hda_common,snd_sof_pci_intel_cnl
snd_sof_xtensa_dsp     16384  1 snd_sof_intel_hda_common
snd_sof               204800  2 snd_sof_pci,snd_sof_intel_hda_common
snd_sof_utils          20480  1 snd_sof
soundwire_bus          94208  3 soundwire_intel,soundwire_generic_allocation,soundwire_cadence
snd_soc_skl           176128  0
snd_hda_codec_hdmi     77824  1
snd_soc_hdac_hda       24576  2 snd_sof_intel_hda_common,snd_soc_skl
snd_hda_ext_core       36864  4 snd_sof_intel_hda_common,snd_soc_hdac_hda,snd_soc_skl,snd_sof_intel_hda
snd_soc_sst_ipc        20480  1 snd_soc_skl
snd_soc_sst_dsp        36864  1 snd_soc_skl
snd_soc_acpi_intel_match    69632  3 snd_sof_intel_hda_common,snd_soc_skl,snd_sof_pci_intel_cnl
snd_soc_acpi           16384  3 snd_soc_acpi_intel_match,snd_sof_intel_hda_common,snd_soc_skl
snd_soc_core          344064  5 soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hda,snd_soc_skl
snd_hda_codec_realtek   167936  1
snd_hda_codec_generic    98304  1 snd_hda_codec_realtek
snd_compress           28672  1 snd_soc_core
ledtrig_audio          16384  1 snd_hda_codec_generic
ac97_bus               16384  1 snd_soc_core
intel_tcc_cooling      16384  0
snd_pcm_dmaengine      16384  1 snd_soc_core
x86_pkg_temp_thermal    20480  0
intel_powerclamp       20480  0
snd_hda_intel          57344  2
coretemp               20480  0
snd_intel_dspcfg       32768  3 snd_hda_intel,snd_sof_intel_hda_common,snd_soc_skl
snd_intel_sdw_acpi     20480  2 snd_sof_intel_hda_common,snd_intel_dspcfg
snd_hda_codec         176128  5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek,snd_soc_hdac_hda
kvm_intel             368640  0
iwlmvm                524288  0
snd_hda_core          110592  10 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_hda_codec_realtek,snd_sof_intel_hda_common,snd_soc_hdac_hda,snd_soc_skl,snd_sof_intel_hda
kvm                  1085440  1 kvm_intel
iTCO_wdt               16384  0
intel_pmc_bxt          16384  1 iTCO_wdt
mac80211             1204224  1 iwlmvm
iTCO_vendor_support    16384  1 iTCO_wdt
snd_hwdep              16384  1 snd_hda_codec
mei_hdcp               24576  0
mei_pxp                20480  0
intel_rapl_msr         20480  0
irqbypass              16384  1 kvm
snd_seq                90112  7 snd_seq_dummy
libarc4                16384  1 mac80211
snd_seq_device         16384  1 snd_seq
rapl                   20480  0
snd_pcm               151552  12 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_compress,snd_soc_core,snd_sof_utils,snd_soc_skl,snd_hda_core,snd_pcm_dmaengine
intel_cstate           20480  0
btusb                  65536  0
uvcvideo              131072  0
intel_uncore          212992  0
snd_timer              49152  3 snd_seq,snd_hrtimer,snd_pcm
btrtl                  28672  1 btusb
iwlwifi               413696  1 iwlmvm
snd                   114688  19 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_sof,snd_timer,snd_compress,snd_soc_core,snd_pcm
pcspkr                 16384  0
btbcm                  20480  1 btusb
iwlmei                 40960  2 iwlmvm,iwlwifi
videobuf2_vmalloc      20480  1 uvcvideo
i2c_i801               36864  0
videobuf2_memops       20480  1 videobuf2_vmalloc
intel_wmi_thunderbolt    20480  0
clevo_wmi              20480  0
i2c_smbus              20480  1 i2c_i801
btintel                49152  1 btusb
soundcore              16384  1 snd
videobuf2_v4l2         36864  1 uvcvideo
btmtk                  16384  1 btusb
cfg80211             1056768  4 iwlmvm,iwlmei,iwlwifi,mac80211
mei_me                 45056  2
videobuf2_common       69632  4 videobuf2_vmalloc,videobuf2_v4l2,uvcvideo,videobuf2_memops
bluetooth             806912  44 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm
mei                   151552  6 mei_hdcp,iwlmei,mei_pxp,mei_me
processor_thermal_device_pci_legacy    16384  0
videodev              274432  3 videobuf2_v4l2,uvcvideo,videobuf2_common
joydev                 28672  0
processor_thermal_device    20480  1 processor_thermal_device_pci_legacy
processor_thermal_rfim    16384  1 processor_thermal_device
processor_thermal_mbox    16384  2 processor_thermal_rfim,processor_thermal_device
processor_thermal_rapl    20480  1 processor_thermal_device
intel_rapl_common      28672  2 intel_rapl_msr,processor_thermal_rapl
rfkill                 36864  10 iwlmvm,bluetooth,cfg80211
mc                     69632  4 videodev,videobuf2_v4l2,uvcvideo,videobuf2_common
idma64                 20480  0
intel_pch_thermal      20480  0
intel_soc_dts_iosf     20480  1 processor_thermal_device_pci_legacy
int3403_thermal        20480  0
int340x_thermal_zone    20480  2 int3403_thermal,processor_thermal_device
clevo_acpi             20480  0
tuxedo_io              20480  0
int3400_thermal        20480  0
tuxedo_keyboard        49152  3 clevo_acpi,tuxedo_io,clevo_wmi
intel_hid              28672  0
acpi_thermal_rel       16384  1 int3400_thermal
acpi_pad              184320  0
sparse_keymap          16384  2 intel_hid,tuxedo_keyboard
zram                   32768  2
i915                 2945024  62
drm_buddy              20480  1 i915
drm_display_helper    172032  1 i915
rtsx_pci_sdmmc         32768  0
crct10dif_pclmul       16384  1
crc32_pclmul           16384  0
crc32c_intel           24576  1
hid_multitouch         32768  0
mmc_core              196608  1 rtsx_pci_sdmmc
nvme                   53248  2
cec                    73728  2 drm_display_helper,i915
ghash_clmulni_intel    16384  0
nvme_core             147456  3 nvme
rtsx_pci              110592  1 rtsx_pci_sdmmc
serio_raw              20480  0
ttm                    90112  1 i915
wmi                    32768  2 intel_wmi_thunderbolt,clevo_wmi
i2c_hid_acpi           16384  0
i2c_hid                32768  1 i2c_hid_acpi
video                  61440  1 i915
pinctrl_cannonlake     36864  0
fuse                  172032  3
9

For output and such, please use the </> button in future :wink:

10

There are four tuxedo modules as far as I read it, plus the tccd.service. You can try to blacklist the modules for testing. Might be easier than uninstalling.

You can test it one by one. So first blacklist one by one tuxedo_io, clevo_acpi and clevo_wmi (always only one of them) - but not tuxedo_keyboard, which is a dependency of the other three. Maybe you are lucky and the fan-controllung module is not the problem-causing module. The last possibility is blacklisting all four at once, including tuxedo_keyboard.

If it does not work, you may try the blacklisting possibilities again but with disabling the service tccd.service in advance, and of course vice versa: just disabling tccd.service without blacklisting the modules.

11

Since I dont know how to blacklist something I removed tcc and tc keyboard. keyboard is necessary for tcc anyway. have not tried suspend yet. stay tuned.

edit: suspend still does not work.

Module                  Size  Used by
tls                   118784  0
uinput                 20480  1
rfcomm                 90112  7
snd_seq_dummy          16384  0
snd_hrtimer            16384  1
nft_objref             16384  1
nf_conntrack_netbios_ns    16384  1
nf_conntrack_broadcast    16384  1 nf_conntrack_netbios_ns
nft_fib_inet           16384  1
nft_fib_ipv4           16384  1 nft_fib_inet
nft_fib_ipv6           16384  1 nft_fib_inet
nft_fib                16384  3 nft_fib_ipv6,nft_fib_ipv4,nft_fib_inet
nft_reject_inet        16384  6
nf_reject_ipv4         16384  1 nft_reject_inet
nf_reject_ipv6         20480  1 nft_reject_inet
nft_reject             16384  1 nft_reject_inet
nft_ct                 20480  16
nft_chain_nat          16384  2
nf_nat                 57344  1 nft_chain_nat
nf_conntrack          167936  4 nf_nat,nft_ct,nf_conntrack_netbios_ns,nf_conntrack_broadcast
nf_defrag_ipv6         24576  1 nf_conntrack
nf_defrag_ipv4         16384  1 nf_conntrack
ip_set                 61440  0
nf_tables             278528  232 nft_ct,nft_reject_inet,nft_fib_ipv6,nft_objref,nft_fib_ipv4,nft_chain_nat,nft_reject,nft_fib,nft_fib_inet
nfnetlink              20480  3 nf_tables,ip_set
qrtr                   45056  4
bnep                   28672  2
sunrpc                655360  1
binfmt_misc            28672  1
vfat                   20480  1
fat                    86016  1 vfat
snd_sof_pci_intel_cnl    16384  0
snd_sof_intel_hda_common   122880  1 snd_sof_pci_intel_cnl
soundwire_intel        45056  1 snd_sof_intel_hda_common
soundwire_generic_allocation    16384  1 soundwire_intel
soundwire_cadence      36864  1 soundwire_intel
snd_sof_intel_hda      20480  1 snd_sof_intel_hda_common
snd_sof_pci            24576  2 snd_sof_intel_hda_common,snd_sof_pci_intel_cnl
snd_sof_xtensa_dsp     16384  1 snd_sof_intel_hda_common
snd_sof               204800  2 snd_sof_pci,snd_sof_intel_hda_common
snd_sof_utils          20480  1 snd_sof
soundwire_bus          94208  3 soundwire_intel,soundwire_generic_allocation,soundwire_cadence
snd_soc_skl           176128  0
snd_soc_hdac_hda       24576  2 snd_sof_intel_hda_common,snd_soc_skl
snd_hda_codec_hdmi     77824  1
snd_hda_ext_core       36864  4 snd_sof_intel_hda_common,snd_soc_hdac_hda,snd_soc_skl,snd_sof_intel_hda
snd_soc_sst_ipc        20480  1 snd_soc_skl
snd_soc_sst_dsp        36864  1 snd_soc_skl
snd_soc_acpi_intel_match    69632  3 snd_sof_intel_hda_common,snd_soc_skl,snd_sof_pci_intel_cnl
snd_soc_acpi           16384  3 snd_soc_acpi_intel_match,snd_sof_intel_hda_common,snd_soc_skl
intel_tcc_cooling      16384  0
x86_pkg_temp_thermal    20480  0
snd_soc_core          344064  5 soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hda,snd_soc_skl
snd_hda_codec_realtek   167936  1
intel_powerclamp       20480  0
snd_hda_codec_generic    98304  1 snd_hda_codec_realtek
iwlmvm                524288  0
snd_compress           28672  1 snd_soc_core
ledtrig_audio          16384  1 snd_hda_codec_generic
ac97_bus               16384  1 snd_soc_core
coretemp               20480  0
snd_pcm_dmaengine      16384  1 snd_soc_core
kvm_intel             368640  0
snd_hda_intel          57344  2
mac80211             1204224  1 iwlmvm
snd_intel_dspcfg       32768  3 snd_hda_intel,snd_sof_intel_hda_common,snd_soc_skl
iTCO_wdt               16384  0
snd_intel_sdw_acpi     20480  2 snd_sof_intel_hda_common,snd_intel_dspcfg
intel_pmc_bxt          16384  1 iTCO_wdt
libarc4                16384  1 mac80211
mei_hdcp               24576  0
mei_pxp                20480  0
iTCO_vendor_support    16384  1 iTCO_wdt
kvm                  1085440  1 kvm_intel
snd_hda_codec         176128  5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek,snd_soc_hdac_hda
intel_rapl_msr         20480  0
irqbypass              16384  1 kvm
snd_hda_core          110592  10 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_hda_codec_realtek,snd_sof_intel_hda_common,snd_soc_hdac_hda,snd_soc_skl,snd_sof_intel_hda
snd_hwdep              16384  1 snd_hda_codec
rapl                   20480  0
snd_seq                90112  7 snd_seq_dummy
iwlwifi               413696  1 iwlmvm
snd_seq_device         16384  1 snd_seq
intel_cstate           20480  0
btusb                  65536  0
intel_uncore          212992  0
snd_pcm               151552  12 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_compress,snd_soc_core,snd_sof_utils,snd_soc_skl,snd_hda_core,snd_pcm_dmaengine
uvcvideo              131072  0
iwlmei                 40960  2 iwlmvm,iwlwifi
btrtl                  28672  1 btusb
pcspkr                 16384  0
intel_wmi_thunderbolt    20480  0
btbcm                  20480  1 btusb
snd_timer              49152  3 snd_seq,snd_hrtimer,snd_pcm
videobuf2_vmalloc      20480  1 uvcvideo
videobuf2_memops       20480  1 videobuf2_vmalloc
btintel                49152  1 btusb
i2c_i801               36864  0
cfg80211             1056768  4 iwlmvm,iwlmei,iwlwifi,mac80211
snd                   114688  19 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_sof,snd_timer,snd_compress,snd_soc_core,snd_pcm
btmtk                  16384  1 btusb
videobuf2_v4l2         36864  1 uvcvideo
i2c_smbus              20480  1 i2c_i801
soundcore              16384  1 snd
videobuf2_common       69632  4 videobuf2_vmalloc,videobuf2_v4l2,uvcvideo,videobuf2_memops
mei_me                 45056  2
bluetooth             806912  44 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm
mei                   151552  6 mei_hdcp,iwlmei,mei_pxp,mei_me
processor_thermal_device_pci_legacy    16384  0
videodev              274432  3 videobuf2_v4l2,uvcvideo,videobuf2_common
joydev                 28672  0
processor_thermal_device    20480  1 processor_thermal_device_pci_legacy
processor_thermal_rfim    16384  1 processor_thermal_device
processor_thermal_mbox    16384  2 processor_thermal_rfim,processor_thermal_device
processor_thermal_rapl    20480  1 processor_thermal_device
mc                     69632  4 videodev,videobuf2_v4l2,uvcvideo,videobuf2_common
rfkill                 36864  10 iwlmvm,bluetooth,cfg80211
intel_rapl_common      28672  2 intel_rapl_msr,processor_thermal_rapl
idma64                 20480  0
intel_pch_thermal      20480  0
intel_soc_dts_iosf     20480  1 processor_thermal_device_pci_legacy
int3403_thermal        20480  0
int340x_thermal_zone    20480  2 int3403_thermal,processor_thermal_device
intel_hid              28672  0
sparse_keymap          16384  1 intel_hid
acpi_pad              184320  0
int3400_thermal        20480  0
acpi_thermal_rel       16384  1 int3400_thermal
zram                   32768  2
i915                 2945024  45
drm_buddy              20480  1 i915
rtsx_pci_sdmmc         32768  0
crct10dif_pclmul       16384  1
crc32_pclmul           16384  0
drm_display_helper    172032  1 i915
crc32c_intel           24576  1
mmc_core              196608  1 rtsx_pci_sdmmc
nvme                   53248  2
cec                    73728  2 drm_display_helper,i915
hid_multitouch         32768  0
ghash_clmulni_intel    16384  0
nvme_core             147456  3 nvme
serio_raw              20480  0
rtsx_pci              110592  1 rtsx_pci_sdmmc
i2c_hid_acpi           16384  0
ttm                    90112  1 i915
wmi                    32768  1 intel_wmi_thunderbolt
i2c_hid                32768  1 i2c_hid_acpi
video                  61440  1 i915
pinctrl_cannonlake     36864  0
fuse                  172032  1
12

In case you want to try it later with testing the modules individually, see https://discussion.fedoraproject.org/t/battery-charge-indicator-broken-on-certain-asus-motherboards-automatic-suspend-doesnt-work/77252
→ this link refers to a different problem, but it explains how to blacklist individual modules, and how to revert blacklisting. So remove asus_ec_sensors from the commands and add the module names of Tuxedo, and also adjust the .conf file names.

13

ok, thank you. Since suspend still does not work. does that mean I can reinstall tcc?

14

Before reinstalling, can you check again cat /proc/sys/kernel/tainted ? And can you check the journalctl log files again? So again as described in https://discussion.fedoraproject.org/t/freeze-after-wake-from-suspend/68954/2

After that, especially if the kernel was no longer tainted in the recent test, I suggest to focus on the other possibilities I elaborated above: https://discussion.fedoraproject.org/t/freeze-after-wake-from-suspend/68954/4

15

ok ,tainted is now 0

sudo journalctl --boot=-1

inxi -Fz

System:
  Kernel: 5.19.7-200.fc36.x86_64 arch: x86_64 bits: 64 Desktop: KDE Plasma
    v: 5.25.4 Distro: Fedora release 36 (Thirty Six)
Machine:
  Type: Laptop System: TUXEDO product: InfinityBook S 14 v5 v: N/A
    serial: <superuser required>
  Mobo: TUXEDO model: L140CU serial: <superuser required> UEFI: INSYDE
    v: 1.07.09RTR1 date: 07/28/2020
Battery:
  ID-1: BAT0 charge: 21.0 Wh (33.4%) condition: 62.8/73.9 Wh (85.0%)
    volts: 8.0 min: 7.7
CPU:
  Info: quad core model: Intel Core i7-10510U bits: 64 type: MT MCP cache:
    L2: 1024 KiB
  Speed (MHz): avg: 1675 min/max: 400/4900 cores: 1: 2300 2: 1300 3: 1300
    4: 2300 5: 1300 6: 2300 7: 1300 8: 1300
Graphics:
  Device-1: Intel CometLake-U GT2 [UHD Graphics] driver: i915 v: kernel
  Device-2: Chicony USB2.0 Camera type: USB driver: uvcvideo
  Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 22.1.3 driver: X:
    loaded: modesetting unloaded: fbdev,vesa gpu: i915
    resolution: 1920x1080~60Hz
  OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 22.1.7
Audio:
  Device-1: Intel Comet Lake PCH-LP cAVS driver: snd_hda_intel
  Sound Server-1: ALSA v: k5.19.7-200.fc36.x86_64 running: yes
  Sound Server-2: PipeWire v: 0.3.57 running: yes
Network:
  Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi
  IF: wlp2s0 state: up mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb
  Report: rfkill ID: hci0 state: up address: see --recommends
Drives:
  Local Storage: total: 1.36 TiB used: 174.4 GiB (12.5%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 1TB
    size: 931.51 GiB
  ID-2: /dev/sda vendor: Samsung model: SSD 860 EVO M.2 500GB
    size: 465.76 GiB
Partition:
  ID-1: / size: 931.01 GiB used: 174.38 GiB (18.7%) fs: btrfs
    dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 511 MiB used: 14 MiB (2.7%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-3: /home size: 931.01 GiB used: 174.38 GiB (18.7%) fs: btrfs
    dev: /dev/nvme0n1p2
  ID-4: /opt size: 931.01 GiB used: 174.38 GiB (18.7%) fs: btrfs
    dev: /dev/nvme0n1p2
  ID-5: /tmp size: 931.01 GiB used: 174.38 GiB (18.7%) fs: btrfs
    dev: /dev/nvme0n1p2
  ID-6: /var size: 931.01 GiB used: 174.38 GiB (18.7%) fs: btrfs
    dev: /dev/nvme0n1p2
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 44.0 C pch: 39.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 303 Uptime: 18m Memory: 15.36 GiB used: 2.81 GiB (18.3%)
  Shell: Zsh inxi: 3.3.19
16

I disabled bluetooth service and went to suspend and back three times without any freezing. That is a good sign, right? but I use my bluetooth to connect to my headphones a lot and disabling this service before suspend every time is a little cumbersome.

edit:
another good sign: I reinstalled tcc and suspend still works great with disabled bluetooth service.

17

First, I suggest to try it a bit more than three times, just to ensure that it really is something that is somehow linked to the bluetoothd service. However, it can also be an interaction that occurs at some point WITH the service.

So, to ensure that this is on the long term as least invasive as possible without banning any bluetooth, I suggest:

→ I have no time remaining today, but you can already investigate org_kde_powerdevil and kscreenlocker_greet; Maybe try it without them! Especially org_kde_powerdevil (“powerdevil”) makes me suspicious in the recent logs you posted.

→ checkout which bluetooth controller you have (should be shown with lsusb | grep uetooth or lspci | grep uetooth → checkout both, and check if there are known issues with your controller.

→ turn off the bluetooth devices you have, check that they are really no longer connected, and then test. I assume that no individual bluetooth device, such as headphones, is the cause but let’s exclude it quickly.

→ use the acpitool method you already identified, and that has already been elaborated in other threads. Do not focus only on bluetooth! Test everything! Especially things with wakeup capability (acpitool -w)! Maybe we can identify the cause more precisely…

→ still checkout the remaining possibilities of above, if not already done.

Feel free to let us know what you found out.

Some past topics I found in my history that you might want to review (also containing but not limited to information about acpitool) are:
https://discussion.fedoraproject.org/t/suspend-exits-immediately-after-installation-of-m2-ssd-nvme/75621/4
https://discussion.fedoraproject.org/t/fedora-freezes-after-suspend/72765/2
https://discussion.fedoraproject.org/t/fedora-freezes-after-suspend/72765/4
https://discussion.fedoraproject.org/t/fedora-34-freeze-at-boot/69800/14

The topics also contain further links. Of course you are not limited to these topics.

18

org_kde_powerdevil: wake up fails, but I see the desktop with all windows, no lock screen, no mouse movement or keyboard activity

kscreenlocker_greet: no running process or service

lsusb | grep uetooth: Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth

lspci | grep uetooth: empty

disconnected bt-head phones: no difference

I observed that using the terminal to go to suspend works, but closing the lid or choosing suspend from the starter menu (mostly) does not.

19

I don’t have time this week, but for now:

This sounds a bit like the problem is in the user space (maybe related to the desktop environment, or an interaction WITH it). You can compare the live images: do you also have the issue if you use the default KDE live image? If so, do you have it also with Workstation/GNOME or lxqt? If the latter two work but the first not, you can maybe identify and replace suspend- and/or bluetooth-related packages (I suggest to start with bluetooth related packages and tools; might be easier). Compare the live images only to each other but not to your current system since they are not up to date (this is why I ask to checkout the KDE live image as well; to see if the KDE live image also has the problem → if not, we know the problem has been introduced later to the KDE spin, and it also tells us that working live images of GNOME/lxqt does not mean that they will also work when updated). However, replacing bluetooth packages and tools with some alternatives is worth a try in any case!

What had helped in the past a few users to bypass such bugs: replace sddm with gdm. As far as I know, KDE works properly with gdm, although gdm is less efficient. If you want to try: install gdm with dnf, and then disable sddm with systemctl, enable gdm, reboot, test (to keep it short and simple, don’t use systemctl with “–now” for now). To revert it, do the same vice versa. If there is any issue with gdm, you can always use a terminal/tty to switch again with systemctl disable/enable + reboot.

I assume this is what happened after you disabled org_kde_powerdevil. However, this information is too abstract to draw something from it. Have you compared logs?

Well, even if you don’t like it, the approach with using acpitool to test disabling different devices one by one might be the remaining alternative if you cannot make much more with the other possibilities. Maybe it can identify that you just have to disable something you don’t use anyway. Or we can at least identify much more precisely where the cause is and find an explicit alternative for it.

Quite sure you can check this out yourself with your preferred search engine :wink:

Also, check the above links. There are some directions you can play with. Feel free to play a bit with the possibilities and develop them.

Btw, also checkout if there are firmware updates for your tuxedo!

20

I removed a second SSD that was installed but not used and now suspend works again.