[SOLVED] Power off when lid closed

Gabriel_Brown · July 4, 2023, 4:24am

I have been plagued by random power downs/shut downs/power offs on lid close for at least four months now. I still cannot reliably trigger this issue, but it is more than frequent enough to be bothersome (about 50% of the time)

I use systemctl suspend to manually suspend before closing, but very often I find that when I take my laptop out of my bag (after about 30 minutes) it has shut off (not hibernated, etc.) and still has almost full battery after boot.

My logind.conf is completely stock (all commented out), so I haven’t changed lid close behavior or anything like that.

I have included a journalctl log that seems to show something like entering suspend mode and then the next entry is the first part of a boot. I’ve marked the shutdown time with <--- reboot happens below ---> so it can be found easily. The first log in this post is another example of such a case, but the log wouldn’t fit here.

I use TLP for some power management, but it doesn’t even seem to have lid settings anyhow.

System Info
OS: EndeavourOS
Framework version: 11th generation

Log 1

Apr 25 10:54:19 schur kernel: Freezing user space processes
Apr 25 10:54:19 schur kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Apr 25 10:54:19 schur kernel: OOM killer disabled.
Apr 25 10:54:19 schur kernel: Freezing remaining freezable tasks
Apr 25 10:54:19 schur kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Apr 25 10:54:19 schur kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Apr 25 10:54:19 schur kernel: ACPI: EC: interrupt blocked
Apr 25 10:54:19 schur kernel: ACPI: EC: interrupt unblocked
Apr 25 10:54:19 schur kernel: nvme nvme0: 8/0/0 default/read/poll queues
Apr 25 10:54:19 schur kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
Apr 25 10:54:19 schur kernel: OOM killer enabled.
Apr 25 10:54:19 schur kernel: Restarting tasks ... 
Apr 25 10:54:19 schur kernel: usb 3-3: USB disconnect, device number 16
Apr 25 10:54:19 schur kernel: mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
Apr 25 10:54:19 schur rtkit-daemon[1332]: The canary thread is apparently starving. Taking action.
Apr 25 10:54:19 schur kernel: usb 3-4: USB disconnect, device number 9
Apr 25 10:54:19 schur kernel: done.
Apr 25 10:54:19 schur kernel: random: crng reseeded on system resumption
Apr 25 10:54:19 schur systemd-logind[506]: Lid closed.
Apr 25 10:54:19 schur syncthing[1150]: [LT2WM] INFO: Connection to IDG44HJ-YXXQGO7-52IAKYX-GJC5LYQ-IQW2WGD-SMQAWN3-ONG7SYY-2HTYEQF at 192.168.0.103:22000-192.168.0.101:22000/quic-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256 closed: reading length: INTERNAL_ERROR (local): write udp [::]:22000->192.168.0.101:22000: sendmsg: network is unreachable
Apr 25 10:54:19 schur rtkit-daemon[1332]: Demoting known real-time threads.
Apr 25 10:54:19 schur systemd[1140]: Starting EOS update notifier service...
Apr 25 10:54:19 schur rtkit-daemon[1332]: Successfully demoted thread 564101 of process 3568.
Apr 25 10:54:19 schur systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Apr 25 10:54:19 schur rtkit-daemon[1332]: Successfully demoted thread 220107 of process 219958.
Apr 25 10:54:19 schur (notifier)[2120444]: eos-update-notifier.service: Failed to locate executable /usr/bin/eos-update-notifier: No such file or directory
Apr 25 10:54:19 schur rtkit-daemon[1332]: Successfully demoted thread 2935 of process 2792.
Apr 25 10:54:19 schur (notifier)[2120444]: eos-update-notifier.service: Failed at step EXEC spawning /usr/bin/eos-update-notifier: No such file or directory
Apr 25 10:54:19 schur rtkit-daemon[1332]: Successfully demoted thread 1376 of process 1306.
Apr 25 10:54:19 schur systemd[1140]: eos-update-notifier.service: Main process exited, code=exited, status=203/EXEC
Apr 25 10:54:19 schur rtkit-daemon[1332]: Successfully demoted thread 1306 of process 1306.
Apr 25 10:54:19 schur systemd[1140]: eos-update-notifier.service: Failed with result 'exit-code'.
Apr 25 10:54:19 schur rtkit-daemon[1332]: Successfully demoted thread 1369 of process 1308.
Apr 25 10:54:19 schur systemd[1140]: Failed to start EOS update notifier service.
Apr 25 10:54:19 schur rtkit-daemon[1332]: Successfully demoted thread 1308 of process 1308.
Apr 25 10:54:19 schur rtkit-daemon[1332]: Successfully demoted thread 1373 of process 1311.
Apr 25 10:54:19 schur rtkit-daemon[1332]: Successfully demoted thread 1311 of process 1311.
Apr 25 10:54:19 schur rtkit-daemon[1332]: Demoted 9 threads.
Apr 25 10:54:19 schur systemd[1]: Rotate log files was skipped because of an unmet condition check (ConditionACPower=true).
Apr 25 10:54:19 schur systemd[1]: Daily man-db regeneration was skipped because of an unmet condition check (ConditionACPower=true).
Apr 25 10:54:19 schur systemd[1]: Started Verify integrity of password and group files.
Apr 25 10:54:19 schur systemd[1]: Starting Update locate database...
Apr 25 10:54:19 schur systemd-sleep[2120322]: System returned from sleep state.
Apr 25 10:54:19 schur bluetoothd[853]: Controller resume with wake event 0x0
Apr 25 10:54:19 schur kernel: PM: suspend exit
Apr 25 10:54:19 schur systemd[1]: shadow.service: Deactivated successfully.
Apr 25 10:54:19 schur tlp[2120507]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Apr 25 10:54:19 schur tlp[2120504]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Apr 25 10:54:19 schur tlp[2120507]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Apr 25 10:54:19 schur tlp[2120504]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Apr 25 10:54:19 schur tlp[2120507]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Apr 25 10:54:19 schur tlp[2120507]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Apr 25 10:54:19 schur tlp[2120504]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Apr 25 10:54:19 schur tlp[2120504]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Apr 25 10:54:19 schur tlp[2120600]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Apr 25 10:54:19 schur tlp[2120600]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Apr 25 10:54:19 schur tlp[2120600]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Apr 25 10:54:19 schur tlp[2120600]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Apr 25 10:54:20 schur tlp[2120628]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Apr 25 10:54:20 schur tlp[2120628]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Apr 25 10:54:20 schur tlp[2120628]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Apr 25 10:54:20 schur tlp[2120628]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Apr 25 10:54:20 schur tlp[2120709]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Apr 25 10:54:20 schur tlp[2120709]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Apr 25 10:54:20 schur tlp[2120709]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Apr 25 10:54:20 schur tlp[2120709]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Apr 25 10:54:20 schur systemd[1]: systemd-suspend.service: Deactivated successfully.
Apr 25 10:54:20 schur systemd[1]: Finished System Suspend.
Apr 25 10:54:20 schur systemd[1]: Stopped target Sleep.
Apr 25 10:54:20 schur systemd[1]: Reached target Suspend.
Apr 25 10:54:20 schur systemd[1]: Stopped target Suspend.
Apr 25 10:54:20 schur systemd-logind[506]: Operation 'sleep' finished.
Apr 25 10:54:20 schur NetworkManager[512]: <info>  [1682438060.2423] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Apr 25 10:54:20 schur NetworkManager[512]: <info>  [1682438060.2424] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Apr 25 10:54:20 schur NetworkManager[512]: <info>  [1682438060.2890] device (wlan0): set-hw-addr: set MAC address to A2:04:A5:E2:93:4A (scanning)
Apr 25 10:54:20 schur tlp[2120794]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Apr 25 10:54:20 schur tlp[2120794]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Apr 25 10:54:20 schur tlp[2120794]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Apr 25 10:54:20 schur tlp[2120794]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Apr 25 10:54:20 schur systemd[1]: updatedb.service: Deactivated successfully.
Apr 25 10:54:20 schur systemd[1]: Finished Update locate database.
Apr 25 10:54:20 schur tlp[2120829]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Apr 25 10:54:20 schur tlp[2120829]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Apr 25 10:54:20 schur tlp[2120829]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Apr 25 10:54:20 schur tlp[2120829]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Apr 25 10:54:20 schur NetworkManager[512]: <info>  [1682438060.5532] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Apr 25 10:54:20 schur NetworkManager[512]: <info>  [1682438060.5540] manager: NetworkManager state is now CONNECTED_LOCAL
Apr 25 10:54:20 schur NetworkManager[512]: <info>  [1682438060.5994] device (wlan0): supplicant interface state: internal-starting -> disconnected
Apr 25 10:54:20 schur NetworkManager[512]: <info>  [1682438060.5995] device (p2p-dev-wlan0): state change: unavailable -> unmanaged (reason 'removed', sys-iface-state: 'removed')
Apr 25 10:54:20 schur NetworkManager[512]: <info>  [1682438060.6002] Wi-Fi P2P device controlled by interface wlan0 created
Apr 25 10:54:20 schur NetworkManager[512]: <info>  [1682438060.6007] manager: (p2p-dev-wlan0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/8)
Apr 25 10:54:20 schur NetworkManager[512]: <info>  [1682438060.6011] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Apr 25 10:54:20 schur NetworkManager[512]: <info>  [1682438060.6018] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Apr 25 10:54:20 schur NetworkManager[512]: <info>  [1682438060.6025] device (p2p-dev-wlan0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Apr 25 10:54:20 schur tlp[2120863]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Apr 25 10:54:20 schur tlp[2120863]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Apr 25 10:54:20 schur tlp[2120863]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Apr 25 10:54:20 schur tlp[2120863]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Apr 25 10:54:20 schur tlp[2120895]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Apr 25 10:54:20 schur tlp[2120895]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Apr 25 10:54:20 schur tlp[2120895]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Apr 25 10:54:20 schur tlp[2120895]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Apr 25 10:54:20 schur tlp[2120927]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Apr 25 10:54:20 schur tlp[2120927]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Apr 25 10:54:20 schur tlp[2120927]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Apr 25 10:54:20 schur tlp[2120927]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Apr 25 10:54:23 schur wpa_supplicant[755]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=US
Apr 25 10:54:36 schur systemd-logind[506]: Suspending...
Apr 25 10:54:36 schur NetworkManager[512]: <info>  [1682438076.1579] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Apr 25 10:54:36 schur NetworkManager[512]: <info>  [1682438076.1580] device (wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Apr 25 10:54:36 schur NetworkManager[512]: <info>  [1682438076.2094] device (wlan0): set-hw-addr: reset MAC address to E4:A4:71:56:AB:D0 (unmanage)
Apr 25 10:54:36 schur NetworkManager[512]: <info>  [1682438076.2209] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Apr 25 10:54:36 schur NetworkManager[512]: <info>  [1682438076.2212] manager: NetworkManager state is now ASLEEP
Apr 25 10:54:36 schur systemd[1]: Reached target Sleep.
Apr 25 10:54:36 schur wpa_supplicant[755]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Apr 25 10:54:36 schur wpa_supplicant[755]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Apr 25 10:54:36 schur wpa_supplicant[755]: nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0
Apr 25 10:54:36 schur systemd[1]: Starting System Suspend...
Apr 25 10:54:36 schur wpa_supplicant[755]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Apr 25 10:54:36 schur systemd-sleep[2121259]: Entering sleep state 'suspend'...
<--- reboot happens below --->
Apr 25 11:20:48 schur kernel: microcode: microcode updated early to revision 0xa6, date = 2022-06-28
Apr 25 11:20:48 schur kernel: Linux version 6.2.11-arch1-1 (linux@archlinux) (gcc (GCC) 12.2.1 20230201, GNU ld (GNU Binutils) 2.40) #1 SMP PREEMPT_DYNAMIC Thu, 13 Apr 2023 16:59:24 +0000
Apr 25 11:20:48 schur kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=2a9459e2-9fde-4f0a-858d-7ed6f395a894 rw resume=UUID=15d901db-b4ce-46e9-a731-7c3e8a90dba0 resume_offset=31760384 quiet loglevel=3 nowatchdog nvme_load=YES
Apr 25 11:20:48 schur kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
Apr 25 11:20:48 schur kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Apr 25 11:20:48 schur kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Apr 25 11:20:48 schur kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Apr 25 11:20:48 schur kernel: x86/fpu: Supporting XSAVE feature 0x020: 'AVX-512 opmask'
Apr 25 11:20:48 schur kernel: x86/fpu: Supporting XSAVE feature 0x040: 'AVX-512 Hi256'
Apr 25 11:20:48 schur kernel: x86/fpu: Supporting XSAVE feature 0x080: 'AVX-512 ZMM_Hi256'
Apr 25 11:20:48 schur kernel: x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers'
Apr 25 11:20:48 schur kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Apr 25 11:20:48 schur kernel: x86/fpu: xstate_offset[5]:  832, xstate_sizes[5]:   64
Apr 25 11:20:48 schur kernel: x86/fpu: xstate_offset[6]:  896, xstate_sizes[6]:  512
Apr 25 11:20:48 schur kernel: x86/fpu: xstate_offset[7]: 1408, xstate_sizes[7]: 1024
Apr 25 11:20:48 schur kernel: x86/fpu: xstate_offset[9]: 2432, xstate_sizes[9]:    8
Apr 25 11:20:48 schur kernel: x86/fpu: Enabled xstate features 0x2e7, context size is 2440 bytes, using 'compacted' format.
Apr 25 11:20:48 schur kernel: signal: max sigframe size: 3632
Apr 25 11:20:48 schur kernel: BIOS-provided physical RAM map:
Apr 25 11:20:48 schur kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Apr 25 11:20:48 schur kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
Apr 25 11:20:48 schur kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000039f98fff] usable
Apr 25 11:20:48 schur kernel: BIOS-e820: [mem 0x0000000039f99000-0x000000003a898fff] reserved
Apr 25 11:20:48 schur kernel: BIOS-e820: [mem 0x000000003a899000-0x00000000434aefff] usable
Apr 25 11:20:48 schur kernel: BIOS-e820: [mem 0x00000000434af000-0x000000004387efff] type 20
Apr 25 11:20:48 schur kernel: BIOS-e820: [mem 0x000000004387f000-0x00000000452fefff] reserved
Apr 25 11:20:48 schur kernel: BIOS-e820: [mem 0x00000000452ff000-0x0000000045b2efff] ACPI NVS
Apr 25 11:20:48 schur kernel: BIOS-e820: [mem 0x0000000045b2f000-0x0000000045bfefff] ACPI data
Apr 25 11:20:48 schur kernel: BIOS-e820: [mem 0x0000000045bff000-0x0000000045bfffff] usable
Apr 25 11:20:48 schur kernel: BIOS-e820: [mem 0x0000000045c00000-0x0000000049ffffff] reserved
Apr 25 11:20:48 schur kernel: BIOS-e820: [mem 0x000000004a200000-0x000000004a3fffff] reserved
Apr 25 11:20:48 schur kernel: BIOS-e820: [mem 0x000000004b000000-0x00000000503fffff] reserved
Apr 25 11:20:48 schur kernel: BIOS-e820: [mem 0x00000000c0000000-0x00000000cfffffff] reserved
Apr 25 11:20:48 schur kernel: BIOS-e820: [mem 0x00000000fe010000-0x00000000fe010fff] reserved
Apr 25 11:20:48 schur kernel: BIOS-e820: [mem 0x00000000fed20000-0x00000000fed7ffff] reserved
Apr 25 11:20:48 schur kernel: BIOS-e820: [mem 0x00000000ff400000-0x00000000ffffffff] reserved
Apr 25 11:20:48 schur kernel: BIOS-e820: [mem 0x0000000100000000-0x00000005afbfffff] usable
Apr 25 11:20:48 schur kernel: NX (Execute Disable) protection: active
Apr 25 11:20:48 schur kernel: efi: EFI v2.70 by INSYDE Corp.
Apr 25 11:20:48 schur kernel: efi: ACPI=0x45bfe000 ACPI 2.0=0x45bfe014 TPMFinalLog=0x45ac5000 SMBIOS=0x439e3000 SMBIOS 3.0=0x439e1000 MEMATTR=0x3f931018 ESRT=0x3fba7818 
Apr 25 11:20:48 schur kernel: efi: Remove mem75: MMIO range=[0xc0000000-0xcfffffff] (256MB) from e820 map
Apr 25 11:20:48 schur kernel: e820: remove [mem 0xc0000000-0xcfffffff] reserved
Apr 25 11:20:48 schur kernel: efi: Not removing mem76: MMIO range=[0xfe010000-0xfe010fff] (4KB) from e820 map
Apr 25 11:20:48 schur kernel: efi: Remove mem78: MMIO range=[0xff400000-0xffffffff] (12MB) from e820 map
Apr 25 11:20:48 schur kernel: e820: remove [mem 0xff400000-0xffffffff] reserved
Apr 25 11:20:48 schur kernel: SMBIOS 3.3.0 present.
Apr 25 11:20:48 schur kernel: DMI: Framework Laptop/FRANBMCP0A, BIOS 03.07 12/14/2021
Apr 25 11:20:48 schur kernel: tsc: Detected 2400.000 MHz processor
Apr 25 11:20:48 schur kernel: tsc: Detected 2419.200 MHz TSC
Apr 25 11:20:48 schur kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Apr 25 11:20:48 schur kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Apr 25 11:20:48 schur kernel: last_pfn = 0x5afc00 max_arch_pfn = 0x400000000
Apr 25 11:20:48 schur kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
Apr 25 11:20:48 schur kernel: last_pfn = 0x45c00 max_arch_pfn = 0x400000000
Apr 25 11:20:48 schur kernel: esrt: Reserving ESRT space from 0x000000003fba7818 to 0x000000003fba78a0.
Apr 25 11:20:48 schur kernel: e820: update [mem 0x3fba7000-0x3fba7fff] usable ==> reserved
Apr 25 11:20:48 schur kernel: Using GB pages for direct mapping
Apr 25 11:20:48 schur kernel: Secure boot disabled
Apr 25 11:20:48 schur kernel: RAMDISK: [mem 0x36061000-0x37027fff]
Apr 25 11:20:48 schur kernel: ACPI: Early table checksum verification disabled
Apr 25 11:20:48 schur kernel: ACPI: RSDP 0x0000000045BFE014 000024 (v02 INSYDE)
Apr 25 11:20:48 schur kernel: ACPI: XSDT 0x0000000045BD1188 000104 (v01 INSYDE TGL-ULT  00000002      01000013)
Apr 25 11:20:48 schur kernel: ACPI: FACP 0x0000000045BD3000 00010C (v06 INSYDE TGL-ULT  00000002 ACPI 00040000)
Apr 25 11:20:48 schur kernel: ACPI: DSDT 0x0000000045B79000 056BD7 (v02 INSYDE TGL-ULT  00000002 ACPI 00040000)
Apr 25 11:20:48 schur kernel: ACPI: FACS 0x0000000045AA1000 000040
Apr 25 11:20:48 schur kernel: ACPI: UEFI 0x0000000045B2E000 000236 (v01 INSYDE TGL-ULT  00000001 ACPI 00040000)
Apr 25 11:20:48 schur kernel: ACPI: SSDT 0x0000000045BFA000 00255C (v02 CpuRef CpuSsdt  00003000 INTL 20160422)
Apr 25 11:20:48 schur kernel: ACPI: SSDT 0x0000000045BF6000 0033A6 (v02 DptfTb DptfTabl 00001000 INTL 20160422)
Apr 25 11:20:48 schur kernel: ACPI: SSDT 0x0000000045BF2000 003034 (v02 SaSsdt SaSsdt   00003000 INTL 20160422)
Apr 25 11:20:48 schur kernel: ACPI: SSDT 0x0000000045BEE000 003300 (v02 INTEL  IgfxSsdt 00003000 INTL 20160422)
Apr 25 11:20:48 schur kernel: ACPI: SSDT 0x0000000045BE2000 00B30D (v02 INTEL  TcssSsdt 00001000 INTL 20160422)
Apr 25 11:20:48 schur kernel: ACPI: SSDT 0x0000000045BE1000 00077B (v02 INSYDE Tpm2Tabl 00001000 INTL 20160422)
Apr 25 11:20:48 schur kernel: ACPI: TPM2 0x0000000045BE0000 00004C (v04 INSYDE TGL-ULT  00000002 ACPI 00040000)
Apr 25 11:20:48 schur kernel: ACPI: SSDT 0x0000000045BDE000 0008C1 (v02 INTEL  xh_tudd4 00000000 INTL 20160422)
Apr 25 11:20:48 schur kernel: ACPI: NHLT 0x0000000045BDD000 00002D (v00 INSYDE TGL-ULT  00000002 ACPI 00040000)
Apr 25 11:20:48 schur kernel: ACPI: SSDT 0x0000000045BDB000 0011C3 (v02 INSYDE UsbCTabl 00001000 INTL 20160422)
Apr 25 11:20:48 schur kernel: ACPI: LPIT 0x0000000045BDA000 0000CC (v01 INSYDE TGL-ULT  00000002 ACPI 00040000)
Apr 25 11:20:48 schur kernel: ACPI: WSMT 0x0000000045BD9000 000028 (v01 INSYDE TGL-ULT  00000002 ACPI 00040000)
Apr 25 11:20:48 schur kernel: ACPI: SSDT 0x0000000045BD8000 000B2E (v02 INSYDE PtidDevc 00001000 INTL 20160422)
Apr 25 11:20:48 schur kernel: ACPI: SSDT 0x0000000045BD7000 00012A (v02 INSYDE TbtTypeC 00000000 INTL 20160422)
Apr 25 11:20:48 schur kernel: ACPI: DBGP 0x0000000045BD6000 000034 (v01 INSYDE TGL-ULT  00000002 ACPI 00040000)
Apr 25 11:20:48 schur kernel: ACPI: DBG2 0x0000000045BD5000 000054 (v00 INSYDE TGL-ULT  00000002 ACPI 00040000)
Apr 25 11:20:48 schur kernel: ACPI: ECDT 0x0000000045BD4000 000069 (v01 INSYDE TGL-ULT  00000002 ACPI 00040000)
Apr 25 11:20:48 schur kernel: ACPI: HPET 0x0000000045BD2000 000038 (v01 INSYDE TGL-ULT  00000002 ACPI 00040000)
Apr 25 11:20:48 schur kernel: ACPI: APIC 0x0000000045BFD000 00012C (v03 INSYDE TGL-ULT  00000002 ACPI 00040000)
Apr 25 11:20:48 schur kernel: ACPI: MCFG 0x0000000045BD0000 00003C (v01 INSYDE TGL-ULT  00000002 ACPI 00040000)
Apr 25 11:20:48 schur kernel: ACPI: SSDT 0x0000000045B72000 00661F (v02 INSYDE TGL-ULT  00000002      01000013)
Apr 25 11:20:48 schur kernel: ACPI: DMAR 0x0000000045B71000 0000E8 (v02 INSYDE TGL-ULT  00000002 ACPI 00040000)
Apr 25 11:20:48 schur kernel: ACPI: SSDT 0x0000000045B70000 0000F8 (v01 INSYDE PcdTabl  00001000 INTL 20160422)
Apr 25 11:20:48 schur kernel: ACPI: FPDT 0x0000000045B6F000 000044 (v01 INSYDE TGL-ULT  00000002 ACPI 00040000)
Apr 25 11:20:48 schur kernel: ACPI: PTDT 0x0000000045B6D000 000CFE (v00 INSYDE TGL-ULT  00000005 ACPI 00040000)
Apr 25 11:20:48 schur kernel: ACPI: BGRT 0x0000000045B6E000 000038 (v01 INSYDE TGL-ULT  00000001 ACPI 00040000)
Apr 25 11:20:48 schur kernel: ACPI: Reserving FACP table memory at [mem 0x45bd3000-0x45bd310b]
Apr 25 11:20:48 schur kernel: ACPI: Reserving DSDT table memory at [mem 0x45b79000-0x45bcfbd6]
Apr 25 11:20:48 schur kernel: ACPI: Reserving FACS table memory at [mem 0x45aa1000-0x45aa103f]
Apr 25 11:20:48 schur kernel: ACPI: Reserving UEFI table memory at [mem 0x45b2e000-0x45b2e235]
Apr 25 11:20:48 schur kernel: ACPI: Reserving SSDT table memory at [mem 0x45bfa000-0x45bfc55b]
Apr 25 11:20:48 schur kernel: ACPI: Reserving SSDT table memory at [mem 0x45bf6000-0x45bf93a5]
Apr 25 11:20:48 schur kernel: ACPI: Reserving SSDT table memory at [mem 0x45bf2000-0x45bf5033]
Apr 25 11:20:48 schur kernel: ACPI: Reserving SSDT table memory at [mem 0x45bee000-0x45bf12ff]
Apr 25 11:20:48 schur kernel: ACPI: Reserving SSDT table memory at [mem 0x45be2000-0x45bed30c]
Apr 25 11:20:48 schur kernel: ACPI: Reserving SSDT table memory at [mem 0x45be1000-0x45be177a]
Apr 25 11:20:48 schur kernel: ACPI: Reserving TPM2 table memory at [mem 0x45be0000-0x45be004b]
Apr 25 11:20:48 schur kernel: ACPI: Reserving SSDT table memory at [mem 0x45bde000-0x45bde8c0]
Apr 25 11:20:48 schur kernel: ACPI: Reserving NHLT table memory at [mem 0x45bdd000-0x45bdd02c]
Apr 25 11:20:48 schur kernel: ACPI: Reserving SSDT table memory at [mem 0x45bdb000-0x45bdc1c2]
Apr 25 11:20:48 schur kernel: ACPI: Reserving LPIT table memory at [mem 0x45bda000-0x45bda0cb]
Apr 25 11:20:48 schur kernel: ACPI: Reserving WSMT table memory at [mem 0x45bd9000-0x45bd9027]
Apr 25 11:20:48 schur kernel: ACPI: Reserving SSDT table memory at [mem 0x45bd8000-0x45bd8b2d]
Apr 25 11:20:48 schur kernel: ACPI: Reserving SSDT table memory at [mem 0x45bd7000-0x45bd7129]
Apr 25 11:20:48 schur kernel: ACPI: Reserving DBGP table memory at [mem 0x45bd6000-0x45bd6033]
Apr 25 11:20:48 schur kernel: ACPI: Reserving DBG2 table memory at [mem 0x45bd5000-0x45bd5053]
Apr 25 11:20:48 schur kernel: ACPI: Reserving ECDT table memory at [mem 0x45bd4000-0x45bd4068]
Apr 25 11:20:48 schur kernel: ACPI: Reserving HPET table memory at [mem 0x45bd2000-0x45bd2037]
Apr 25 11:20:48 schur kernel: ACPI: Reserving APIC table memory at [mem 0x45bfd000-0x45bfd12b]
Apr 25 11:20:48 schur kernel: ACPI: Reserving MCFG table memory at [mem 0x45bd0000-0x45bd003b]
Apr 25 11:20:48 schur kernel: ACPI: Reserving SSDT table memory at [mem 0x45b72000-0x45b7861e]
Apr 25 11:20:48 schur kernel: ACPI: Reserving DMAR table memory at [mem 0x45b71000-0x45b710e7]
Apr 25 11:20:48 schur kernel: ACPI: Reserving SSDT table memory at [mem 0x45b70000-0x45b700f7]
Apr 25 11:20:48 schur kernel: ACPI: Reserving FPDT table memory at [mem 0x45b6f000-0x45b6f043]
Apr 25 11:20:48 schur kernel: ACPI: Reserving PTDT table memory at [mem 0x45b6d000-0x45b6dcfd]
Apr 25 11:20:48 schur kernel: ACPI: Reserving BGRT table memory at [mem 0x45b6e000-0x45b6e037]
Apr 25 11:20:48 schur kernel: No NUMA configuration found
Apr 25 11:20:48 schur kernel: Faking a node at [mem 0x0000000000000000-0x00000005afbfffff]
Apr 25 11:20:48 schur kernel: NODE_DATA(0) allocated [mem 0x5afbfb000-0x5afbfffff]
Apr 25 11:20:48 schur kernel: Zone ranges:
Apr 25 11:20:48 schur kernel:   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
Apr 25 11:20:48 schur kernel:   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
Apr 25 11:20:48 schur kernel:   Normal   [mem 0x0000000100000000-0x00000005afbfffff]
Apr 25 11:20:48 schur kernel:   Device   empty
Apr 25 11:20:48 schur kernel: Movable zone start for each node
Apr 25 11:20:48 schur kernel: Early memory node ranges
Apr 25 11:20:48 schur kernel:   node   0: [mem 0x0000000000001000-0x000000000009efff]
Apr 25 11:20:48 schur kernel:   node   0: [mem 0x0000000000100000-0x0000000039f98fff]
Apr 25 11:20:48 schur kernel:   node   0: [mem 0x000000003a899000-0x00000000434aefff]
Apr 25 11:20:48 schur kernel:   node   0: [mem 0x0000000045bff000-0x0000000045bfffff]
Apr 25 11:20:48 schur kernel:   node   0: [mem 0x0000000100000000-0x00000005afbfffff]
Apr 25 11:20:48 schur kernel: Initmem setup node 0 [mem 0x0000000000001000-0x00000005afbfffff]
Apr 25 11:20:48 schur kernel: On node 0, zone DMA: 1 pages in unavailable ranges
Apr 25 11:20:48 schur kernel: On node 0, zone DMA: 97 pages in unavailable ranges
Apr 25 11:20:48 schur kernel: On node 0, zone DMA32: 2304 pages in unavailable ranges
Apr 25 11:20:48 schur kernel: On node 0, zone DMA32: 10064 pages in unavailable ranges
Apr 25 11:20:48 schur kernel: On node 0, zone Normal: 9216 pages in unavailable ranges
Apr 25 11:20:48 schur kernel: On node 0, zone Normal: 1024 pages in unavailable ranges
Apr 25 11:20:48 schur kernel: Reserving Intel graphics memory at [mem 0x4c800000-0x503fffff]
Apr 25 11:20:48 schur kernel: ACPI: PM-Timer IO Port: 0x1808
Apr 25 11:20:48 schur kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Apr 25 11:20:48 schur kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Apr 25 11:20:48 schur kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Apr 25 11:20:48 schur kernel: ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
Apr 25 11:20:48 schur kernel: ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1])
Apr 25 11:20:48 schur kernel: ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1])
Apr 25 11:20:48 schur kernel: ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1])
Apr 25 11:20:48 schur kernel: ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Apr 25 11:20:48 schur kernel: ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Apr 25 11:20:48 schur kernel: ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Apr 25 11:20:48 schur kernel: ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Apr 25 11:20:48 schur kernel: ACPI: LAPIC_NMI (acpi_id[0x0c] high edge lint[0x1])
Apr 25 11:20:48 schur kernel: ACPI: LAPIC_NMI (acpi_id[0x0d] high edge lint[0x1])
Apr 25 11:20:48 schur kernel: ACPI: LAPIC_NMI (acpi_id[0x0e] high edge lint[0x1])
Apr 25 11:20:48 schur kernel: ACPI: LAPIC_NMI (acpi_id[0x0f] high edge lint[0x1])
Apr 25 11:20:48 schur kernel: ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Apr 25 11:20:48 schur kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119
Apr 25 11:20:48 schur kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Apr 25 11:20:48 schur kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Apr 25 11:20:48 schur kernel: ACPI: Using ACPI (MADT) for SMP configuration information
Apr 25 11:20:48 schur kernel: ACPI: HPET id: 0x8086a201 base: 0xfed00000
Apr 25 11:20:48 schur kernel: e820: update [mem 0x3f932000-0x3f980fff] usable ==> reserved
Apr 25 11:20:48 schur kernel: TSC deadline timer available
Apr 25 11:20:48 schur kernel: smpboot: Allowing 8 CPUs, 0 hotplug CPUs
Apr 25 11:20:48 schur kernel: PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
Apr 25 11:20:48 schur kernel: PM: hibernation: Registered nosave memory: [mem 0x0009f000-0x000fffff]
Apr 25 11:20:48 schur kernel: PM: hibernation: Registered nosave memory: [mem 0x39f99000-0x3a898fff]
Apr 25 11:20:48 schur kernel: PM: hibernation: Registered nosave memory: [mem 0x3f932000-0x3f980fff]
Apr 25 11:20:48 schur kernel: PM: hibernation: Registered nosave memory: [mem 0x3fba7000-0x3fba7fff]
Apr 25 11:20:48 schur kernel: PM: hibernation: Registered nosave memory: [mem 0x434af000-0x4387efff]
Apr 25 11:20:48 schur kernel: PM: hibernation: Registered nosave memory: [mem 0x4387f000-0x452fefff]
Apr 25 11:20:48 schur kernel: PM: hibernation: Registered nosave memory: [mem 0x452ff000-0x45b2efff]
Apr 25 11:20:48 schur kernel: PM: hibernation: Registered nosave memory: [mem 0x45b2f000-0x45bfefff]
Apr 25 11:20:48 schur kernel: PM: hibernation: Registered nosave memory: [mem 0x45c00000-0x49ffffff]
Apr 25 11:20:48 schur kernel: PM: hibernation: Registered nosave memory: [mem 0x4a000000-0x4a1fffff]
Apr 25 11:20:48 schur kernel: PM: hibernation: Registered nosave memory: [mem 0x4a200000-0x4a3fffff]
Apr 25 11:20:48 schur kernel: PM: hibernation: Registered nosave memory: [mem 0x4a400000-0x4affffff]
Apr 25 11:20:48 schur kernel: PM: hibernation: Registered nosave memory: [mem 0x4b000000-0x503fffff]
Apr 25 11:20:48 schur kernel: PM: hibernation: Registered nosave memory: [mem 0x50400000-0xfe00ffff]
Apr 25 11:20:48 schur kernel: PM: hibernation: Registered nosave memory: [mem 0xfe010000-0xfe010fff]
Apr 25 11:20:48 schur kernel: PM: hibernation: Registered nosave memory: [mem 0xfe011000-0xfed1ffff]
Apr 25 11:20:48 schur kernel: PM: hibernation: Registered nosave memory: [mem 0xfed20000-0xfed7ffff]
Apr 25 11:20:48 schur kernel: PM: hibernation: Registered nosave memory: [mem 0xfed80000-0xffffffff]
Apr 25 11:20:48 schur kernel: [mem 0x50400000-0xfe00ffff] available for PCI devices
Apr 25 11:20:48 schur kernel: Booting paravirtualized kernel on bare hardware

Loell_Framework · July 4, 2023, 3:03pm

Hi @Gabriel_Brown , welcome back to the forums.

can you show the journalctl --list-boots

and point out the frequency of the shutdowns on the list?

Gabriel_Brown · July 4, 2023, 3:52pm

Sure! I’ve only marked the ones I am confident are due to this issue, but I would guess there are at least a few more.

None of the very rapid reboots (less than 5 minutes) are due to this issue.

Boot list

IDX BOOT ID                          FIRST ENTRY                 LAST ENTRY
-36 ee8078bd6e9a44ad8818467b2b3edc67 Sat 2023-03-25 15:08:18 CDT Sat 2023-04-01 10:13:17 CDT
-35 bbdc8a46b2a64f7c85bbdc03c087e52c Sat 2023-04-01 15:45:00 CDT Sun 2023-04-02 09:12:00 CDT
-34 0317d1a918b641249cdf255d7d4fdd0e Sun 2023-04-02 09:28:51 CDT Mon 2023-04-03 13:14:05 CDT
<issue here>
-33 345200fe2879448f82f40854d73f95ef Mon 2023-04-03 13:41:49 CDT Mon 2023-04-10 02:02:42 CDT
-32 85b84eb05fce4c64b0aff66858b2e6e0 Mon 2023-04-10 02:02:57 CDT Tue 2023-04-11 21:01:14 CDT
-31 69261dbe13b24c1bac1136a991e04c40 Tue 2023-04-11 23:28:53 CDT Thu 2023-04-20 16:43:08 CDT
<issue here>
-30 099d878899df4b1998851d3687c9ff34 Thu 2023-04-20 17:21:16 CDT Thu 2023-04-20 19:14:35 CDT
-29 8ed0ce94ac2b4ff497d33eeffa25ae0f Fri 2023-04-21 07:52:39 CDT Sat 2023-04-22 11:36:34 CDT
-28 c6b80bb95d034b558122cfafd61408c8 Sat 2023-04-22 12:10:17 CDT Sun 2023-04-23 10:28:59 CDT
-27 cf85007051484818b58307825ec05861 Sun 2023-04-23 12:20:38 CDT Tue 2023-04-25 10:54:36 CDT
<issue here>
-26 223323c7ea36473c8db697ca81970725 Tue 2023-04-25 11:20:48 CDT Sat 2023-05-06 10:35:45 CDT
-25 69cfbbb484494584846b655d9de57e59 Sat 2023-05-06 10:49:32 CDT Thu 2023-05-11 19:53:59 CDT
-24 d852758adbd14ec7b1f141d976204bef Thu 2023-05-11 23:28:41 CDT Fri 2023-05-12 08:51:31 CDT
-23 c398728cb02248ae8d8c02b6968a08b3 Fri 2023-05-12 13:41:09 CDT Fri 2023-05-12 20:52:04 CDT
-22 e13e26050884491a8e14f6eae1773af7 Fri 2023-05-12 20:54:01 CDT Mon 2023-05-15 16:36:28 CDT
-21 10a17962ae4747f58be5b9297b044565 Mon 2023-05-15 16:36:43 CDT Tue 2023-05-16 04:18:31 CDT
-20 0a7549c4a5a04ad2acf568697a104946 Tue 2023-05-16 13:23:42 CDT Wed 2023-05-17 13:13:01 CDT
-19 a84babf2981a487a8dc7b842cfd32227 Wed 2023-05-17 13:13:17 CDT Sun 2023-05-21 18:52:40 CDT
-18 1d14d682dc034735a3c03213f0230c05 Sun 2023-05-21 19:12:56 CDT Tue 2023-05-23 15:44:06 CDT
-17 8557a6e62ff04c1cb8cbaae9b131b603 Tue 2023-05-23 15:44:21 CDT Wed 2023-05-24 03:28:01 CDT
-16 03adbeafc401494dbbdb79c58f8a51e5 Wed 2023-05-24 10:11:26 CDT Tue 2023-05-30 17:10:18 CDT
-15 570a35d825824e4380540e47a151d2e0 Tue 2023-05-30 17:10:34 CDT Thu 2023-06-01 10:03:11 CDT
<issue here>
-14 e80879ac656844ca9fc41d7587c58c23 Thu 2023-06-01 10:30:52 CDT Thu 2023-06-08 23:38:57 CDT
-13 1daef06b1324452fa72adc30ede8fd70 Fri 2023-06-09 08:50:09 CDT Fri 2023-06-09 21:32:44 CDT
-12 f31f432e52ee420eb9fc12305da3c566 Sat 2023-06-10 08:58:10 CDT Sat 2023-06-10 13:55:11 CDT
-11 8ba464857ddf4327ad8f58f3e1fe88d1 Sat 2023-06-10 14:47:48 CDT Mon 2023-06-12 20:24:12 CDT
-10 3efde4006bd94e2e8725cf2e157eeaf3 Tue 2023-06-13 09:51:57 CDT Tue 2023-06-13 14:45:36 CDT
<issue here>
 -9 6e46a9de7b9f413c97e8c0092f2be3b7 Tue 2023-06-13 15:25:17 CDT Thu 2023-06-15 01:01:23 CDT
 -8 cb9667e96d504151972524863b8e7ac1 Thu 2023-06-15 11:00:12 CDT Tue 2023-06-20 20:16:20 CDT
 -7 569da8eaa08746e68a5433b360d4d542 Tue 2023-06-20 20:16:34 CDT Fri 2023-06-23 13:59:12 CDT
<issue here>
 -6 5d5e7bd00cdf48e4b00cbf591c89053c Fri 2023-06-23 18:09:31 CDT Mon 2023-06-26 12:14:15 CDT
<issue here>
 -5 45f471f7a36f45c98939f9fa5f1ea45f Mon 2023-06-26 12:37:44 CDT Thu 2023-06-29 04:20:05 CDT
 -4 5ad3443a123e45ec86ab1341dcc65c36 Thu 2023-06-29 11:04:32 CDT Thu 2023-06-29 11:32:37 CDT
<issue here>
 -3 85aabb7c8797462db2b5ed558ec78aba Thu 2023-06-29 12:50:32 CDT Mon 2023-07-03 09:39:27 CDT
<issue here>
 -2 abecc5b8012745cc8b3c8dad111f49a6 Mon 2023-07-03 10:17:10 CDT Mon 2023-07-03 19:06:11 CDT
<issue here>
 -1 4bfb777dc9fa4d158fa85333004b1b02 Mon 2023-07-03 20:28:14 CDT Mon 2023-07-03 22:37:53 CDT
  0 633b6c24d9394cc9b8d9ec8086dcea77 Mon 2023-07-03 22:43:58 CDT Tue 2023-07-04 10:29:26 CDT

Gabriel_Brown · July 5, 2023, 4:41pm

I’m not sure the best way to continue reporting these issues as they occur since I can’t edit messages, but for what it’s worth the issue has occurred twice already this morning.

Gabriel_Brown · July 10, 2023, 4:46pm

Hi, @Loell_Framework, have you had a chance to look into this?

I am happy to provide more information if needed.

Loell_Framework · July 10, 2023, 9:33pm

Hi @Gabriel_Brown , sorry bit busy with tickets these past few days,
that does seem frequently shut off, can you get the whole journal?

journal > journald.txt

Gabriel_Brown · July 12, 2023, 6:19pm

@Loell_Framework
Sure, I’d be happy to. However, I don’t think I can post a message with that many characters, and no text-like extension types are supported for upload. Is there an email to which I can send my log?

Edit: I almost got around this by changing the extension type, but apparently new users can’t add attachments.

Fraoch · July 12, 2023, 6:41pm

Try it now.

Gabriel_Brown · July 12, 2023, 7:10pm

Thanks. Unfortunately, due to file size limitations I’ve had to split the journal into pieces, and I’ve only been able to include logs since 2023-06-11.

journal0.stl (4.0 MB)
journal1.stl (4.0 MB)
journal2.stl (4.0 MB)
journal3.stl (3.0 MB)

Gabriel_Brown · July 25, 2023, 12:30am

@Loell_Framework Just pinging you again on this now that it’s been a few weeks and my logs are up. I understand you probably have many tickets to work on.

I have noticed that if I simply close the lid (which is configured to suspend by default), I do not experience power-off issues. Note that this is not a solution, simply a workaround that I hope to use temporarily, especially since (as set up) it means I can’t lock+suspend+close my laptop, only suspend+close.

Matt_Hartley · July 27, 2023, 1:47am

Hi @Gabriel_Brown.

I have looked through the logs and nothing is really standing out as to a cause. EndeavourOS isn’t a distro we test with, so there may be something going on in that space.

Would be interesting to rule out hardware here by testing a tested distribution like Fedora to see if happens there as well.

Gabriel_Brown · July 27, 2023, 1:55am

@Matt_Hartley
I see, is this something I could test with a live image, or would I have to do a full install? Does it matter what desktop environment I use?

Matt_Hartley · July 27, 2023, 2:12am

I’d start with a live USB, then if that works for you and you have a spare hard drive, test on it as well.

Gabriel_Brown · October 31, 2023, 5:35pm

A live Fedora USB with same window manager (i3) did not seem to exhibit any issues, but I did not try with an actual disk install.

For what it’s worth, the issues have seemed to disappear entirely since I switched to deep sleep/suspend from s2idle on Linux.

Matt_Hartley · October 31, 2023, 6:10pm

Gotcha. I’ll mark as user resolved.

Maxr1998 · June 26, 2024, 10:11am

Apologies for bumping this old thread, but I’m experiencing the same now. I’m on an AMD 7840 Framework 13, so the deep suspend mode isn’t available for me as a solution. So far, it has only happened twice, but I think it’s related to a BIOS change I did shortly before the problem arose.

The other day, I wanted to look into tuning the battery life on my Framework Laptop. As part of this process, I also ran the amd_s2idle.py script. Because of the script’s output (see below), I checked the BIOS for the mentioned modern standby setting (which I didn’t find).

script output

$ sudo ./amd_s2idle.py
Location of log file (default s2idle_report-2024-06-26.txt)? 
Debugging script for s2idle on AMD systems
💻 Framework Laptop 13 (AMD Ryzen 7040Series) (Laptop) running BIOS 3.5 (03.05) released 03/29/2024 and EC unknown
🐧 Arch Linux
🐧 Kernel 6.9.6-arch1-1
🔋 Battery BAT1 (NVT FRANGWA) is operating at 98.70% of design
Checking prerequisites for s2idle
✅ Logs are provided via systemd
✅ AMD Ryzen 7 7840U w/ Radeon  780M Graphics (family 19 model 74)
✅ SMT enabled
✅ LPS0 _DSM enabled
✅ ACPI FADT supports Low-power S0 idle
✅ HSMP driver `amd_hsmp` not detected (blocked: False)
✅ PMC driver `amd_pmc` loaded (Program 0 Firmware 76.82.0)
✅ USB4 driver `thunderbolt` bound to 0000:c3:00.5
✅ USB4 driver `thunderbolt` bound to 0000:c3:00.6
✅ GPU driver `amdgpu` bound to 0000:c1:00.0
❌ System isn't configured for s2idle in firmware setup
✅ NVME Samsung Electronics Co Ltd NVMe SSD Controller S4LV008[Pascal] is configured for s2idle in BIOS
✅ GPIO driver `pinctrl_amd` available
Your system does not meet s2idle prerequisites!
Explanations for your system
🚦 The system hasn't been configured for Modern Standby in BIOS setup
	AMD systems must be configured for Modern Standby in BIOS setup
	for s2idle to function properly in Linux.
	On some OEM systems this is referred to as 'Windows' sleep mode.
	If the BIOS is configured for S3 and you manually select s2idle
	in /sys/power/mem_sleep, the system will not enter the deepest hardware state.
$ cat /sys/power/mem_sleep
s2idle

While I was in the BIOS, I also changed the iGPU memory to the gaming mode. The issue has only been occurring since I made this change. I now reverted it and will monitor whether it happens again. Could this setting cause the described problem in the first place?

Update: doesn’t seem to have been the issue, I set it back to Auto and rebooted earlier today, but just now I got the issue again. When opening the lid, the keyboard lighting and screen turned on (black but backlight active), and after a few seconds, the boot manager popped up. My laptop was plugged in all that time, so it’s definitely not the battery.