You are not logged in.

#1 2023-12-17 00:01:19

danherbert
Member
Registered: 2022-08-23
Posts: 7

[SOLVED] System occasionally suspending every ~10 seconds in loop

Roughly every other day at some point, my laptop gets stuck in a state where it thinks it must suspend while I'm using it. In this state, I seem to be able to continue typing even without visual feedback so it's possible the screen is just going blank and everything is otherwise working fine.

Once the system suspends (or blanks the screen), it will not come back (mouse/keyboard will not wake it) unless I close my laptop lid, wait about 30-60 seconds (not sure of the exact timing), and then open the lid and unlock my DE. When I do this, I only have about 10 seconds before it repeats itself and suspends again. The only way I've found to break this loop and go back to normal is to reboot the laptop.

I'm running a Framework 12th Gen laptop on the latest kernel (6.6.7) with Gnome on Wayland. I've noticed this for at least a month or 2, so the exact kernel version doesn't seem significant. What kind of logs can I check to diagnose this? The dmesg output shows suspend happening, but I don't see anything obviously wrong in those logs. dmesg snippet below below begins from waking the device in one of the loops, then forcing itself to sleep, and then me waking it again.

[  +0.008127] PM: suspend exit
[  +1.357634] usb 3-9: reset full-speed USB device number 2 using xhci_hcd
[  +0.309848] usb 3-9: reset full-speed USB device number 2 using xhci_hcd
[  +1.775243] wlp166s0: authenticate with 3c:bd:c5:62:66:58
[  +0.017416] wlp166s0: send auth to 3c:bd:c5:62:66:58 (try 1/3)
[  +0.034760] wlp166s0: authenticated
[  +0.001928] wlp166s0: associate with 3c:bd:c5:62:66:58 (try 1/3)
[  +0.002481] wlp166s0: RX AssocResp from 3c:bd:c5:62:66:58 (capab=0x1011 status=0 aid=8)
[  +0.022610] wlp166s0: associated
[  +0.087988] wlp166s0: Limiting TX power to 24 (24 - 0) dBm as advertised by 3c:bd:c5:62:66:58
[  +7.343329] wlp166s0: deauthenticating from 3c:bd:c5:62:66:58 by local choice (Reason: 3=DEAUTH_LEAVING)
[  +0.984375] PM: suspend entry (s2idle)
[  +0.021315] Filesystems sync: 0.021 seconds
[  +0.003647] Freezing user space processes
[  +0.002442] Freezing user space processes completed (elapsed 0.002 seconds)
[  +0.000004] OOM killer disabled.
[  +0.000001] Freezing remaining freezable tasks
[  +0.001673] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
[  +0.000003] printk: Suspending console(s) (use no_console_suspend to debug)
[  +0.292041] ACPI: EC: interrupt blocked
[Dec17 09:27] ACPI: EC: interrupt unblocked
[  +0.192416] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.13.1
[  +0.000005] i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
[  +0.002539] iwlwifi 0000:a6:00.0: WRT: Invalid buffer destination
[  +0.011973] i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads
[  +0.000817] i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
[  +0.000003] i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
[  +0.000616] i915 0000:00:02.0: [drm] GT0: GUC: RC enabled
[  +0.009797] nvme nvme0: 20/0/0 default/read/poll queues
[  +0.136920] iwlwifi 0000:a6:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
[  +0.000036] iwlwifi 0000:a6:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[  +0.000027] iwlwifi 0000:a6:00.0: WFPM_AUTH_KEY_0: 0x90
[  +0.000024] iwlwifi 0000:a6:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0
[  +0.128940] OOM killer enabled.
[  +0.000004] Restarting tasks ...
[  +0.005150] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
[  +0.002834] done.
[  +0.000011] random: crng reseeded on system resumption
[  +0.001133] mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
[  +0.011035] PM: suspend exit
[  +1.290477] usb 3-9: reset full-speed USB device number 2 using xhci_hcd
[  +0.303331] usb 3-9: reset full-speed USB device number 2 using xhci_hcd
[  +1.840490] wlp166s0: authenticate with 3c:bd:c5:62:66:58
[  +0.018209] wlp166s0: send auth to 3c:bd:c5:62:66:58 (try 1/3)
[  +0.035175] wlp166s0: authenticated
[  +0.005423] wlp166s0: associate with 3c:bd:c5:62:66:58 (try 1/3)
[  +0.002125] wlp166s0: RX AssocResp from 3c:bd:c5:62:66:58 (capab=0x1011 status=0 aid=12)
[  +0.022206] wlp166s0: associated
[  +0.156221] wlp166s0: Limiting TX power to 24 (24 - 0) dBm as advertised by 3c:bd:c5:62:66:58

Last edited by danherbert (2023-12-18 13:35:27)

Offline

#2 2023-12-17 02:05:37

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,804

Re: [SOLVED] System occasionally suspending every ~10 seconds in loop

After rebooting, post the output of:

journalctl -b | curl -F 'file=@-' 0x0.st

This will post a copy of the of the journal of your last boot (the one that had the weirdness) to a pastebin site and provide you with a link that we can use to see that journal.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#3 2023-12-17 16:59:23

seth
Member
Registered: 2012-09-03
Posts: 51,826

Re: [SOLVED] System occasionally suspending every ~10 seconds in loop

I seem to be able to continue typing even without visual feedback so it's possible the screen is just going blank and everything is otherwise working fine.

There's no input during a S3, so you're probably not sleeping (but the journal will tell)
Can you switch the VT and get an output (ctrl+alt+f1,f2,f3,…)?

Gnome on Wayland

Try to cause this with an X11 session, preferably just openbox or icewm - gnome, if you really must (since apparently this takes a while to trigger)

Offline

#4 2023-12-18 13:34:47

danherbert
Member
Registered: 2022-08-23
Posts: 7

Re: [SOLVED] System occasionally suspending every ~10 seconds in loop

From reviewing the journal logs, it looks like the problem was a bogus option flag in a few SSHFS mounts in my /etc/fstab file. That flag would sometimes end up in a retry loop if the mount was unreachable, which slowed down things long enough that it was causing the gnome-shell to panic, hence the screen blackout.

Closing my laptop lid for long enough was causing my system to suspend, and when it would wake, the gnome-shell would try to remount those sshfs mounts in the background and the shell would remain usable only long enough for the mounts to retry until the shell crashed again.

Offline

Board footer

Powered by FluxBB