Crash whenever I close my laptop

samtell · 2020-07-23 01:29:13

Hi, so I've been running into this issue whenever I close my laptop lid. What happens is that when I open it up, things work as normal for a minute or two but then something crashes and the computer goes to sleep. I press the power button and it comes back online, but it inevitable crashes again. This will just keep hapening untill I reboot. I'm still very new here and I'm at a bit of a loss of where to begin investigating. Below is the output of journalctl -n -p 3 imediately following one of these crashes. To be perfectly frank, its gibberish to me. I'd really like to know more about what's going on. Any guidance from the community would be greatly appreciated. Thanks in advance

-- Logs begin at Wed 2020-07-15 19:43:10 EDT, end at Wed 2020-07-22 21:10:22 EDT. --
Jul 22 21:09:39 marchbk kernel: ACPI Error: Aborting method \_SB.PCI0.LPCB.EC0.RTEC due to previous error (AE_NOT_EXIST) (20200326/psparse-529)
Jul 22 21:09:39 marchbk kernel: ACPI Error: Aborting method \RWAK due to previous error (AE_NOT_EXIST) (20200326/psparse-529)
Jul 22 21:09:39 marchbk kernel: ACPI Error: Aborting method \_WAK due to previous error (AE_NOT_EXIST) (20200326/psparse-529)
Jul 22 21:09:39 marchbk kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK (20200326/hwesleep-47)
Jul 22 21:10:14 marchbk kernel: ACPI Error: No handler for Region [VRTC] (00000000928d3521) [SystemCMOS] (20200326/evregion-127)

ondoho · 2020-07-23 08:29:14

Well, it clearly is some sort of ACPI error.
Are you sure it actually crashes? Your description sounds like it might be just going down to sleep and waking up again, endlessly?

samtell wrote:

journalctl -n -p 3

Don't use -n here, it defaults to 10 lines which might not be enough.
Also more than just error messages might be required. I'd just post the whole portion of the journal relevant to the time when the problem occurs.

There's also relevant settings in DE & systemd we need to know about.

samtell · 2020-07-24 00:17:34

Hi, Thanks for your reply.

I'm using i3-gaps. That's pretty much it. I'm using lightdm as a display manager, but I still have the issue if I start i3 with startx /bin/i3. I had been using plasma before trying out i3. It doesn't happen in plasma, so i3 must be the culprit, or at least implicated... Here is the full sudo journalctl imediately following one of these "crashes." (Looking at it, I think you're right. It just spontaneously susspends itself, nothing crashes, though I won't presume to interpret it..)

Jul 23 19:43:33 marchbk systemd-logind[464]: Lid closed.
Jul 23 19:43:33 marchbk systemd-logind[464]: Suspending...
Jul 23 19:43:33 marchbk systemd[1]: Reached target Sleep.
Jul 23 19:43:33 marchbk systemd[1]: Starting Suspend...
Jul 23 19:43:33 marchbk systemd-sleep[1067]: Suspending system...
Jul 23 19:43:33 marchbk kernel: PM: suspend entry (deep)
Jul 23 19:43:56 marchbk kernel: Filesystems sync: 0.001 seconds
Jul 23 19:43:56 marchbk kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Jul 23 19:43:56 marchbk kernel: OOM killer disabled.
Jul 23 19:43:56 marchbk kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Jul 23 19:43:56 marchbk kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jul 23 19:43:56 marchbk kernel: wlo1: deauthenticating from 38:17:c3:71:42:10 by local choice (Reason: 3=DEAUTH_LEAVING)
Jul 23 19:43:56 marchbk kernel: ACPI: EC: interrupt blocked
Jul 23 19:43:56 marchbk kernel: ACPI: Preparing to enter system sleep state S3
Jul 23 19:43:56 marchbk kernel: ACPI: EC: event blocked
Jul 23 19:43:56 marchbk kernel: ACPI: EC: EC stopped
Jul 23 19:43:56 marchbk kernel: PM: Saving platform NVS memory
Jul 23 19:43:56 marchbk kernel: Disabling non-boot CPUs ...
Jul 23 19:43:56 marchbk kernel: IRQ 166: no longer affine to CPU1
Jul 23 19:43:56 marchbk kernel: smpboot: CPU 1 is now offline
Jul 23 19:43:56 marchbk kernel: IRQ 167: no longer affine to CPU2
Jul 23 19:43:56 marchbk kernel: smpboot: CPU 2 is now offline
Jul 23 19:43:56 marchbk kernel: IRQ 168: no longer affine to CPU3
Jul 23 19:43:56 marchbk kernel: smpboot: CPU 3 is now offline
Jul 23 19:43:56 marchbk kernel: IRQ 169: no longer affine to CPU4
Jul 23 19:43:56 marchbk kernel: smpboot: CPU 4 is now offline
Jul 23 19:43:56 marchbk kernel: IRQ 170: no longer affine to CPU5
Jul 23 19:43:56 marchbk kernel: smpboot: CPU 5 is now offline
Jul 23 19:43:56 marchbk kernel: IRQ 171: no longer affine to CPU6
Jul 23 19:43:56 marchbk kernel: smpboot: CPU 6 is now offline
Jul 23 19:43:56 marchbk kernel: IRQ 172: no longer affine to CPU7
Jul 23 19:43:56 marchbk kernel: smpboot: CPU 7 is now offline
Jul 23 19:43:56 marchbk kernel: IRQ 173: no longer affine to CPU8
Jul 23 19:43:56 marchbk kernel: smpboot: CPU 8 is now offline
Jul 23 19:43:56 marchbk kernel: IRQ 174: no longer affine to CPU9
Jul 23 19:43:56 marchbk kernel: smpboot: CPU 9 is now offline
Jul 23 19:43:56 marchbk kernel: IRQ 175: no longer affine to CPU10
Jul 23 19:43:56 marchbk kernel: smpboot: CPU 10 is now offline
Jul 23 19:43:56 marchbk kernel: smpboot: CPU 11 is now offline
Jul 23 19:43:56 marchbk kernel: ACPI: Low-level resume complete
Jul 23 19:43:56 marchbk kernel: ACPI: EC: EC started
Jul 23 19:43:56 marchbk kernel: PM: Restoring platform NVS memory
Jul 23 19:43:56 marchbk kernel: Enabling non-boot CPUs ...
Jul 23 19:43:56 marchbk kernel: x86: Booting SMP configuration:
Jul 23 19:43:56 marchbk kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Jul 23 19:43:56 marchbk kernel: unchecked MSR access error: RDMSR from 0x123 at rIP: 0xffffffff8c671b34 (native_read_msr+0x4/0x30)
Jul 23 19:43:56 marchbk kernel: Call Trace:
Jul 23 19:43:56 marchbk kernel:  update_srbds_msr+0x34/0x70
Jul 23 19:43:56 marchbk kernel:  smp_store_cpu_info+0x45/0x50
Jul 23 19:43:56 marchbk kernel:  start_secondary+0x79/0x1e0
Jul 23 19:43:56 marchbk kernel:  secondary_startup_64+0xb6/0xc0
Jul 23 19:43:56 marchbk kernel: unchecked MSR access error: WRMSR to 0x123 (tried to write 0x0000000000000000) at rIP: 0xffffffff8c671d34 (native_write_msr+0x4/0x20)
Jul 23 19:43:56 marchbk kernel: Call Trace:
Jul 23 19:43:56 marchbk kernel:  update_srbds_msr+0x5d/0x70
Jul 23 19:43:56 marchbk kernel:  smp_store_cpu_info+0x45/0x50
Jul 23 19:43:56 marchbk kernel:  start_secondary+0x79/0x1e0
Jul 23 19:43:56 marchbk kernel:  secondary_startup_64+0xb6/0xc0
Jul 23 19:43:56 marchbk kernel: microcode: sig=0x906ea, pf=0x20, revision=0xb4
Jul 23 19:43:56 marchbk kernel: intel_pstate: Disabling energy efficiency optimization
Jul 23 19:43:56 marchbk kernel: CPU1 is up
Jul 23 19:43:56 marchbk kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Jul 23 19:43:56 marchbk kernel: CPU2 is up
Jul 23 19:43:56 marchbk kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Jul 23 19:43:56 marchbk kernel: CPU3 is up
Jul 23 19:43:56 marchbk kernel: smpboot: Booting Node 0 Processor 4 APIC 0x8
Jul 23 19:43:56 marchbk kernel: CPU4 is up
Jul 23 19:43:56 marchbk kernel: smpboot: Booting Node 0 Processor 5 APIC 0xa
Jul 23 19:43:56 marchbk kernel: CPU5 is up
Jul 23 19:43:56 marchbk kernel: smpboot: Booting Node 0 Processor 6 APIC 0x1
Jul 23 19:43:56 marchbk kernel: microcode: sig=0x906ea, pf=0x20, revision=0xd6
Jul 23 19:43:56 marchbk kernel: CPU6 is up
Jul 23 19:43:56 marchbk kernel: smpboot: Booting Node 0 Processor 7 APIC 0x3
Jul 23 19:43:56 marchbk kernel: CPU7 is up
Jul 23 19:43:56 marchbk kernel: smpboot: Booting Node 0 Processor 8 APIC 0x5
Jul 23 19:43:56 marchbk kernel: CPU8 is up
Jul 23 19:43:56 marchbk kernel: smpboot: Booting Node 0 Processor 9 APIC 0x7
Jul 23 19:43:56 marchbk kernel: CPU9 is up
Jul 23 19:43:56 marchbk kernel: smpboot: Booting Node 0 Processor 10 APIC 0x9
Jul 23 19:43:56 marchbk kernel: CPU10 is up
Jul 23 19:43:56 marchbk kernel: smpboot: Booting Node 0 Processor 11 APIC 0xb
Jul 23 19:43:56 marchbk kernel: CPU11 is up
Jul 23 19:43:56 marchbk kernel: ACPI: Waking up from system sleep state S3
Jul 23 19:43:56 marchbk kernel: ACPI Error: No handler for Region [VRTC] (0000000051a21870) [SystemCMOS] (20200326/evregion-127)
Jul 23 19:43:56 marchbk kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler (20200326/exfldio-261)
Jul 23 19:43:56 marchbk kernel: ACPI Error: Aborting method \_SB.PCI0.LPCB.EC0.RTEC due to previous error (AE_NOT_EXIST) (20200326/psparse-529)
Jul 23 19:43:56 marchbk kernel: ACPI Error: Aborting method \RWAK due to previous error (AE_NOT_EXIST) (20200326/psparse-529)
Jul 23 19:43:56 marchbk kernel: ACPI Error: Aborting method \_WAK due to previous error (AE_NOT_EXIST) (20200326/psparse-529)
Jul 23 19:43:56 marchbk kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK (20200326/hwesleep-47)
Jul 23 19:43:56 marchbk kernel: ACPI: EC: interrupt unblocked
Jul 23 19:43:56 marchbk kernel: ACPI: EC: event unblocked
Jul 23 19:43:56 marchbk kernel: usb usb3: root hub lost power or was reset
Jul 23 19:43:56 marchbk kernel: usb usb4: root hub lost power or was reset
Jul 23 19:43:56 marchbk kernel: nvme nvme0: 12/0/0 default/read/poll queues
Jul 23 19:43:56 marchbk kernel: usb 1-7: reset high-speed USB device number 2 using xhci_hcd
Jul 23 19:43:56 marchbk kernel: ata5: SATA link down (SStatus 4 SControl 300)
Jul 23 19:43:56 marchbk kernel: acpi LNXPOWER:06: Turning OFF
Jul 23 19:43:56 marchbk kernel: acpi LNXPOWER:02: Turning OFF
Jul 23 19:43:56 marchbk kernel: OOM killer enabled.
Jul 23 19:43:56 marchbk kernel: Restarting tasks ... done.
Jul 23 19:43:56 marchbk kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
Jul 23 19:43:56 marchbk dhcpcd[1190]: sending signal TERM to pid 1031
Jul 23 19:43:56 marchbk dhcpcd[1190]: waiting for pid 1031 to exit
Jul 23 19:43:56 marchbk dhcpcd[1031]: received SIGTERM, stopping
Jul 23 19:43:56 marchbk dhcpcd[1031]: wlo1: removing interface
Jul 23 19:43:56 marchbk dhcpcd[1031]: dhcpcd exited
Jul 23 19:43:56 marchbk systemd-sleep[1067]: System resumed.
Jul 23 19:43:56 marchbk kernel: PM: suspend exit
Jul 23 19:43:56 marchbk systemd[1]: systemd-suspend.service: Succeeded.
Jul 23 19:43:56 marchbk systemd[1]: Finished Suspend.
Jul 23 19:43:56 marchbk audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 23 19:43:56 marchbk audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 23 19:43:56 marchbk systemd[1]: Stopped target Sleep.
Jul 23 19:43:56 marchbk systemd[1]: Reached target Suspend.
Jul 23 19:43:56 marchbk systemd[1]: Stopped target Suspend.
Jul 23 19:43:56 marchbk kernel: audit: type=1130 audit(1595547836.863:92): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 23 19:43:56 marchbk kernel: audit: type=1131 audit(1595547836.863:93): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 23 19:43:56 marchbk systemd-logind[464]: Operation 'sleep' finished.
Jul 23 19:44:00 marchbk kernel: wlo1: authenticate with 38:17:c3:72:64:10
Jul 23 19:44:00 marchbk kernel: wlo1: send auth to 38:17:c3:72:64:10 (try 1/3)
Jul 23 19:44:00 marchbk kernel: wlo1: authenticated
Jul 23 19:44:00 marchbk kernel: wlo1: associate with 38:17:c3:72:64:10 (try 1/3)
Jul 23 19:44:00 marchbk kernel: wlo1: RX AssocResp from 38:17:c3:72:64:10 (capab=0x411 status=0 aid=2)
Jul 23 19:44:00 marchbk kernel: wlo1: associated
Jul 23 19:44:00 marchbk dhcpcd[1207]: dhcpcd-9.1.4 starting
Jul 23 19:44:00 marchbk dhcpcd[1209]: DUID 00:04:34:66:38:31:31:36:35:65:32:39:63:30:34:34:38:39
Jul 23 19:44:00 marchbk dhcpcd[1209]: wlo1: connected to Access Point `TELLHOME'
Jul 23 19:44:00 marchbk dhcpcd[1209]: wlo1: IAID a6:6f:7d:18
Jul 23 19:44:01 marchbk dhcpcd[1209]: wlo1: rebinding lease of 192.168.1.4
Jul 23 19:44:01 marchbk dhcpcd[1209]: wlo1: probing address 192.168.1.4/24
Jul 23 19:44:06 marchbk dhcpcd[1209]: wlo1: leased 192.168.1.4 for 86400 seconds
Jul 23 19:44:06 marchbk dhcpcd[1209]: wlo1: adding route to 192.168.1.0/24
Jul 23 19:44:06 marchbk dhcpcd[1209]: wlo1: adding default route via 192.168.1.1
Jul 23 19:44:15 marchbk audit[1232]: USER_ACCT pid=1232 uid=1000 auid=1000 ses=4 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="samtell" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jul 23 19:44:15 marchbk audit[1232]: CRED_REFR pid=1232 uid=0 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_unix,pam_permit,pam_env acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jul 23 19:44:15 marchbk audit[1232]: USER_START pid=1232 uid=0 auid=1000 ses=4 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jul 23 19:44:15 marchbk sudo[1232]:  samtell : TTY=pts/0 ; PWD=/home/samtell ; USER=root ; COMMAND=/usr/bin/journalctl
Jul 23 19:44:15 marchbk kernel: audit: type=1101 audit(1595547855.193:94): pid=1232 uid=1000 auid=1000 ses=4 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="samtell" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jul 23 19:44:15 marchbk kernel: audit: type=1110 audit(1595547855.193:95): pid=1232 uid=0 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_unix,pam_permit,pam_env acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jul 23 19:44:15 marchbk kernel: audit: type=1105 audit(1595547855.193:96): pid=1232 uid=0 auid=1000 ses=4 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jul 23 19:44:15 marchbk sudo[1232]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jul 23 19:44:16 marchbk sudo[1232]: pam_unix(sudo:session): session closed for user root
Jul 23 19:44:16 marchbk audit[1232]: USER_END pid=1232 uid=0 auid=1000 ses=4 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jul 23 19:44:16 marchbk audit[1232]: CRED_DISP pid=1232 uid=0 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_unix,pam_permit,pam_env acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jul 23 19:44:16 marchbk kernel: audit: type=1106 audit(1595547856.940:97): pid=1232 uid=0 auid=1000 ses=4 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jul 23 19:44:16 marchbk kernel: audit: type=1104 audit(1595547856.940:98): pid=1232 uid=0 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_unix,pam_permit,pam_env acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jul 23 19:44:24 marchbk systemd-logind[464]: Suspending...
Jul 23 19:44:24 marchbk systemd[1]: Reached target Sleep.
Jul 23 19:44:24 marchbk systemd[1]: Starting Suspend...
Jul 23 19:44:24 marchbk systemd-sleep[1234]: Suspending system...
Jul 23 19:44:24 marchbk kernel: PM: suspend entry (deep)
Jul 23 19:44:30 marchbk kernel: Filesystems sync: 0.037 seconds
Jul 23 19:44:30 marchbk kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Jul 23 19:44:30 marchbk kernel: OOM killer disabled.
Jul 23 19:44:30 marchbk kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Jul 23 19:44:30 marchbk kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jul 23 19:44:30 marchbk kernel: wlo1: deauthenticating from 38:17:c3:72:64:10 by local choice (Reason: 3=DEAUTH_LEAVING)
Jul 23 19:44:30 marchbk kernel: ACPI: EC: interrupt blocked
Jul 23 19:44:30 marchbk kernel: ACPI: Preparing to enter system sleep state S3
Jul 23 19:44:30 marchbk kernel: ACPI: EC: event blocked
Jul 23 19:44:30 marchbk kernel: ACPI: EC: EC stopped
Jul 23 19:44:30 marchbk kernel: PM: Saving platform NVS memory
Jul 23 19:44:30 marchbk kernel: Disabling non-boot CPUs ...
Jul 23 19:44:30 marchbk kernel: smpboot: CPU 1 is now offline
Jul 23 19:44:30 marchbk kernel: smpboot: CPU 2 is now offline
Jul 23 19:44:30 marchbk kernel: smpboot: CPU 3 is now offline
Jul 23 19:44:30 marchbk kernel: smpboot: CPU 4 is now offline
Jul 23 19:44:30 marchbk kernel: smpboot: CPU 5 is now offline
Jul 23 19:44:30 marchbk kernel: smpboot: CPU 6 is now offline
Jul 23 19:44:30 marchbk kernel: smpboot: CPU 7 is now offline
Jul 23 19:44:30 marchbk kernel: smpboot: CPU 8 is now offline
Jul 23 19:44:30 marchbk kernel: smpboot: CPU 9 is now offline
Jul 23 19:44:30 marchbk kernel: smpboot: CPU 10 is now offline
Jul 23 19:44:30 marchbk kernel: smpboot: CPU 11 is now offline
Jul 23 19:44:30 marchbk kernel: ACPI: Low-level resume complete
Jul 23 19:44:30 marchbk kernel: ACPI: EC: EC started
Jul 23 19:44:30 marchbk kernel: PM: Restoring platform NVS memory
Jul 23 19:44:30 marchbk kernel: Enabling non-boot CPUs ...
Jul 23 19:44:30 marchbk kernel: x86: Booting SMP configuration:
Jul 23 19:44:30 marchbk kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Jul 23 19:44:30 marchbk kernel: microcode: sig=0x906ea, pf=0x20, revision=0xb4
Jul 23 19:44:30 marchbk kernel: intel_pstate: Disabling energy efficiency optimization
Jul 23 19:44:30 marchbk kernel: CPU1 is up
Jul 23 19:44:30 marchbk kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Jul 23 19:44:30 marchbk kernel: CPU2 is up
Jul 23 19:44:30 marchbk kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Jul 23 19:44:30 marchbk kernel: CPU3 is up
Jul 23 19:44:30 marchbk kernel: smpboot: Booting Node 0 Processor 4 APIC 0x8
Jul 23 19:44:30 marchbk kernel: CPU4 is up
Jul 23 19:44:30 marchbk kernel: smpboot: Booting Node 0 Processor 5 APIC 0xa
Jul 23 19:44:30 marchbk kernel: CPU5 is up
Jul 23 19:44:30 marchbk kernel: smpboot: Booting Node 0 Processor 6 APIC 0x1
Jul 23 19:44:30 marchbk kernel: microcode: sig=0x906ea, pf=0x20, revision=0xd6
Jul 23 19:44:30 marchbk kernel: CPU6 is up
Jul 23 19:44:30 marchbk kernel: smpboot: Booting Node 0 Processor 7 APIC 0x3
Jul 23 19:44:30 marchbk kernel: CPU7 is up
Jul 23 19:44:30 marchbk kernel: smpboot: Booting Node 0 Processor 8 APIC 0x5
Jul 23 19:44:30 marchbk kernel: CPU8 is up
Jul 23 19:44:30 marchbk kernel: smpboot: Booting Node 0 Processor 9 APIC 0x7
Jul 23 19:44:30 marchbk kernel: CPU9 is up
Jul 23 19:44:30 marchbk kernel: smpboot: Booting Node 0 Processor 10 APIC 0x9
Jul 23 19:44:30 marchbk kernel: CPU10 is up
Jul 23 19:44:30 marchbk kernel: smpboot: Booting Node 0 Processor 11 APIC 0xb
Jul 23 19:44:30 marchbk kernel: CPU11 is up
Jul 23 19:44:30 marchbk kernel: ACPI: Waking up from system sleep state S3
Jul 23 19:44:30 marchbk kernel: ACPI Error: No handler for Region [VRTC] (0000000051a21870) [SystemCMOS] (20200326/evregion-127)
Jul 23 19:44:30 marchbk kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler (20200326/exfldio-261)
Jul 23 19:44:30 marchbk kernel: ACPI Error: Aborting method \_SB.PCI0.LPCB.EC0.RTEC due to previous error (AE_NOT_EXIST) (20200326/psparse-529)
Jul 23 19:44:30 marchbk kernel: ACPI Error: Aborting method \RWAK due to previous error (AE_NOT_EXIST) (20200326/psparse-529)
Jul 23 19:44:30 marchbk kernel: ACPI Error: Aborting method \_WAK due to previous error (AE_NOT_EXIST) (20200326/psparse-529)
Jul 23 19:44:30 marchbk kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK (20200326/hwesleep-47)
Jul 23 19:44:30 marchbk kernel: ACPI: EC: interrupt unblocked
Jul 23 19:44:30 marchbk kernel: ACPI: EC: event unblocked
Jul 23 19:44:30 marchbk kernel: usb usb3: root hub lost power or was reset
Jul 23 19:44:30 marchbk kernel: usb usb4: root hub lost power or was reset
Jul 23 19:44:30 marchbk kernel: nvme nvme0: 12/0/0 default/read/poll queues
Jul 23 19:44:30 marchbk kernel: usb 1-7: reset high-speed USB device number 2 using xhci_hcd
Jul 23 19:44:30 marchbk kernel: ata5: SATA link down (SStatus 4 SControl 300)
Jul 23 19:44:30 marchbk kernel: acpi LNXPOWER:06: Turning OFF
Jul 23 19:44:30 marchbk kernel: acpi LNXPOWER:02: Turning OFF
Jul 23 19:44:30 marchbk kernel: OOM killer enabled.
Jul 23 19:44:30 marchbk kernel: Restarting tasks ... done.
Jul 23 19:44:30 marchbk kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
Jul 23 19:44:30 marchbk dhcpcd[1259]: sending signal TERM to pid 1209
Jul 23 19:44:30 marchbk dhcpcd[1259]: waiting for pid 1209 to exit
Jul 23 19:44:30 marchbk dhcpcd[1209]: received SIGTERM, stopping
Jul 23 19:44:30 marchbk dhcpcd[1209]: wlo1: removing interface
Jul 23 19:44:30 marchbk dhcpcd[1209]: dhcpcd exited
Jul 23 19:44:30 marchbk systemd-sleep[1234]: System resumed.
Jul 23 19:44:30 marchbk kernel: PM: suspend exit
Jul 23 19:44:30 marchbk systemd[1]: systemd-suspend.service: Succeeded.
Jul 23 19:44:30 marchbk systemd[1]: Finished Suspend.
Jul 23 19:44:30 marchbk audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 23 19:44:30 marchbk audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 23 19:44:30 marchbk systemd[1]: Stopped target Sleep.
Jul 23 19:44:30 marchbk systemd[1]: Reached target Suspend.
Jul 23 19:44:30 marchbk systemd[1]: Stopped target Suspend.
Jul 23 19:44:30 marchbk systemd-logind[464]: Operation 'sleep' finished.
Jul 23 19:44:30 marchbk kernel: audit: type=1130 audit(1595547870.850:99): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 23 19:44:30 marchbk kernel: audit: type=1131 audit(1595547870.850:100): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 23 19:44:31 marchbk kernel: wlo1: authenticate with 38:17:c3:71:42:10
Jul 23 19:44:31 marchbk kernel: wlo1: send auth to 38:17:c3:71:42:10 (try 1/3)
Jul 23 19:44:31 marchbk kernel: wlo1: authenticated
Jul 23 19:44:31 marchbk kernel: wlo1: associate with 38:17:c3:71:42:10 (try 1/3)
Jul 23 19:44:31 marchbk kernel: wlo1: RX AssocResp from 38:17:c3:71:42:10 (capab=0x411 status=0 aid=3)
Jul 23 19:44:31 marchbk kernel: wlo1: associated
Jul 23 19:44:31 marchbk dhcpcd[1277]: dhcpcd-9.1.4 starting
Jul 23 19:44:31 marchbk dhcpcd[1279]: DUID 00:04:34:66:38:31:31:36:35:65:32:39:63:30:34:34:38:39
Jul 23 19:44:31 marchbk dhcpcd[1279]: wlo1: connected to Access Point `TELLHOME'
Jul 23 19:44:31 marchbk dhcpcd[1279]: wlo1: IAID a6:6f:7d:18
Jul 23 19:44:33 marchbk dhcpcd[1279]: wlo1: rebinding lease of 192.168.1.4
Jul 23 19:44:33 marchbk audit[1285]: USER_ACCT pid=1285 uid=1000 auid=1000 ses=4 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="samtell" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jul 23 19:44:33 marchbk audit[1285]: CRED_REFR pid=1285 uid=0 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_unix,pam_permit,pam_env acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jul 23 19:44:33 marchbk sudo[1285]:  samtell : TTY=pts/0 ; PWD=/home/samtell ; USER=root ; COMMAND=/usr/bin/journalctl
Jul 23 19:44:33 marchbk audit[1285]: USER_START pid=1285 uid=0 auid=1000 ses=4 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jul 23 19:44:33 marchbk sudo[1285]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jul 23 19:44:33 marchbk kernel: audit: type=1101 audit(1595547873.323:101): pid=1285 uid=1000 auid=1000 ses=4 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="samtell" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jul 23 19:44:33 marchbk kernel: audit: type=1110 audit(1595547873.323:102): pid=1285 uid=0 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_unix,pam_permit,pam_env acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jul 23 19:44:33 marchbk kernel: audit: type=1105 audit(1595547873.323:103): pid=1285 uid=0 auid=1000 ses=4 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jul 23 19:44:34 marchbk audit[1285]: USER_END pid=1285 uid=0 auid=1000 ses=4 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jul 23 19:44:34 marchbk audit[1285]: CRED_DISP pid=1285 uid=0 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_unix,pam_permit,pam_env acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jul 23 19:44:34 marchbk sudo[1285]: pam_unix(sudo:session): session closed for user root
Jul 23 19:44:34 marchbk kernel: audit: type=1106 audit(1595547874.840:104): pid=1285 uid=0 auid=1000 ses=4 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jul 23 19:44:34 marchbk kernel: audit: type=1104 audit(1595547874.840:105): pid=1285 uid=0 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_unix,pam_permit,pam_env acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jul 23 19:44:36 marchbk dhcpcd[1279]: wlo1: probing address 192.168.1.4/24
Jul 23 19:44:38 marchbk audit[1287]: USER_ACCT pid=1287 uid=1000 auid=1000 ses=4 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="samtell" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jul 23 19:44:38 marchbk audit[1287]: CRED_REFR pid=1287 uid=0 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_unix,pam_permit,pam_env acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jul 23 19:44:38 marchbk sudo[1287]:  samtell : TTY=pts/0 ; PWD=/home/samtell ; USER=root ; COMMAND=/usr/bin/journalctl
Jul 23 19:44:38 marchbk audit[1287]: USER_START pid=1287 uid=0 auid=1000 ses=4 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jul 23 19:44:38 marchbk sudo[1287]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jul 23 19:44:38 marchbk kernel: audit: type=1101 audit(1595547878.903:106): pid=1287 uid=1000 auid=1000 ses=4 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="samtell" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jul 23 19:44:38 marchbk kernel: audit: type=1110 audit(1595547878.903:107): pid=1287 uid=0 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_unix,pam_permit,pam_env acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jul 23 19:44:38 marchbk kernel: audit: type=1105 audit(1595547878.903:108): pid=1287 uid=0 auid=1000 ses=4 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'

19:43:33 - I close the lid
19:43:56 - I open it back up. This is when we get the ACPI error
19:44:00-06 - Auto connects to wifi
19:44:15 - I called sudo journalctl
19:44:24 - It just goes back to sleep
19:44:30 - I press the power. We get the ACPI error again

That's pretty much it.

Please let me know if anything here stands out to you. In the mean time, I'll keep investigating and trying to find some online resources that might shed some light on this issue.

samtell · 2020-07-24 00:42:45

OK I just took a look at the logs when I open and close the lid in plasma. The ACPI error is there too. So that is an issue I will look into at some other time, but it's not what's causing my computer to spontaniously go to sleep. I guess it's just that for whatever reason the system doesn't realize it already when to sleep, so just does it again...?

GaKu999 · 2020-07-24 00:54:11

samtell wrote:

OK I just took a look at the logs when I open and close the lid in plasma. The ACPI error is there too. So that is an issue I will look into at some other time, but it's not what's causing my computer to spontaniously go to sleep. I guess it's just that for whatever reason the system doesn't realize it already when to sleep, so just does it again...?

So this wasn't there before and just now it's there? Suspend on lid is handled by systemd, assuming vanilla setup this is unintended...
Suspected cause may be firmware in this case...
You may attempt to downgrade your system to see when it's not replicating anymore to post a proper issue to the devs of the source.
Or try to tweak the boot with some of the ACPI related kernel command lines...

But please add your settings on DE/Systemd if any because they are VERY relevant to this issue...

samtell · 2020-07-24 01:52:27

Well I'm actaully not sure if the ACPI error was there before. Like I said, I'm very new. This is the first time I really feel comfortable enough to dive into the journal. But whatever is going on with ACPI, it's not causing the suspend on lid issue. The error is there when I open the lid in plasma, and there is no suspend on lid issue (unless it is and plasma has some workaround). I will look into the ACPI problem at some other time. I'm learning more about my computer every day, and I'm sure I will eventually notice some issue that will require me to address it. I don't think this is that issue though. I could be wrong...

As for Systemd and DE settings... There is no DE running, just i3. below is my config file. I already tried commenting out all of my custom changes with no luck... And I definitely didn't make any custom changes to Systemd yet. Everything is vanilla. Let me know which commands/files might give me some relevent info.

# 	@custom:
#-------------------------------

# load resources if I open i3 by overriding xinitrc
exec xrdb ~/.Xresources

# disable trackpad while typing

exec syndaemon -d -i 1 -t -K

# gaps

for_window [class=".*"] border pixel 0

gaps inner 25
gaps outer 6

# wallpaper

exec feh --bg-scale ~/Pictures/cld.jpg

# compositor

exec picom

#-------------------------------


# This file has been auto-generated by i3-config-wizard(1).
# It will not be overwritten, so edit it as you like.
#
# Should you change your keyboard layout some time, delete
# this file and re-run i3-config-wizard(1).
#

# i3 config file (v4)
#
# Please see https://i3wm.org/docs/userguide.html for a complete reference!

set $mod Mod4

# Font for window titles. Will also be used by the bar unless a different font
# is used in the bar {} block below.
font pango:monospace 8

# This font is widely installed, provides lots of unicode glyphs, right-to-left
# text rendering and scalability on retina/hidpi displays (thanks to pango).
#font pango:DejaVu Sans Mono 8

# The combination of xss-lock, nm-applet and pactl is a popular choice, so
# they are included here as an example. Modify as you see fit.

# xss-lock grabs a logind suspend inhibit lock and will use i3lock to lock the
# screen before suspend. Use loginctl lock-session to lock your screen.
exec --no-startup-id xss-lock --transfer-sleep-lock -- i3lock --nofork

# NetworkManager is the most popular way to manage wireless networks on Linux,
# and nm-applet is a desktop environment-independent system tray GUI for it.
exec --no-startup-id nm-applet

# Use pactl to adjust volume in PulseAudio.
set $refresh_i3status killall -SIGUSR1 i3status
bindsym XF86AudioRaiseVolume exec --no-startup-id pactl set-sink-volume @DEFAULT_SINK@ +10% && $refresh_i3status
bindsym XF86AudioLowerVolume exec --no-startup-id pactl set-sink-volume @DEFAULT_SINK@ -10% && $refresh_i3status
bindsym XF86AudioMute exec --no-startup-id pactl set-sink-mute @DEFAULT_SINK@ toggle && $refresh_i3status
bindsym XF86AudioMicMute exec --no-startup-id pactl set-source-mute @DEFAULT_SOURCE@ toggle && $refresh_i3status

# Use Mouse+$mod to drag floating windows to their wanted position
floating_modifier $mod

# start a terminal
bindsym $mod+Return exec i3-sensible-terminal

# kill focused window
bindsym $mod+Shift+q kill

# start dmenu (a program launcher)
bindsym $mod+d exec dmenu_run
# There also is the (new) i3-dmenu-desktop which only displays applications
# shipping a .desktop file. It is a wrapper around dmenu, so you need that
# installed.
# bindsym $mod+d exec --no-startup-id i3-dmenu-desktop

# change focus
bindsym $mod+h focus left
bindsym $mod+j focus down
bindsym $mod+k focus up
bindsym $mod+l focus right

# alternatively, you can use the cursor keys:
bindsym $mod+Left focus left
bindsym $mod+Down focus down
bindsym $mod+Up focus up
bindsym $mod+Right focus right

# move focused window
bindsym $mod+Shift+h move left
bindsym $mod+Shift+j move down
bindsym $mod+Shift+k move up
bindsym $mod+Shift+l move right

# alternatively, you can use the cursor keys:
bindsym $mod+Shift+Left move left
bindsym $mod+Shift+Down move down
bindsym $mod+Shift+Up move up
bindsym $mod+Shift+Right move right

# we can toggle between vertical and horizontal using $mod-e

# split in horizontal orientation
bindsym $mod+n split h

# split in vertical orientation
bindsym $mod+v split v

# enter fullscreen mode for the focused container
bindsym $mod+f fullscreen toggle

# change container layout (stacked, tabbed, toggle split)
bindsym $mod+s layout stacking
bindsym $mod+w layout tabbed
bindsym $mod+e layout toggle split

# toggle tiling / floating
bindsym $mod+Shift+space floating toggle

# change focus between tiling / floating windows
bindsym $mod+space focus mode_toggle

# focus the parent container
bindsym $mod+a focus parent

# focus the child container
#bindsym $mod+d focus child

# Define names for default workspaces for which we configure key bindings later on.
# We use variables to avoid repeating the names in multiple places.
set $ws1 "1"
set $ws2 "2"
set $ws3 "3"
set $ws4 "4"
set $ws5 "5"
set $ws6 "6"
set $ws7 "7"
set $ws8 "8"
set $ws9 "9"
set $ws10 "10"

# switch to workspace
bindsym $mod+1 workspace number $ws1
bindsym $mod+2 workspace number $ws2
bindsym $mod+3 workspace number $ws3
bindsym $mod+4 workspace number $ws4
bindsym $mod+5 workspace number $ws5
bindsym $mod+6 workspace number $ws6
bindsym $mod+7 workspace number $ws7
bindsym $mod+8 workspace number $ws8
bindsym $mod+9 workspace number $ws9
bindsym $mod+0 workspace number $ws10

# move focused container to workspace
bindsym $mod+Shift+1 move container to workspace number $ws1
bindsym $mod+Shift+2 move container to workspace number $ws2
bindsym $mod+Shift+3 move container to workspace number $ws3
bindsym $mod+Shift+4 move container to workspace number $ws4
bindsym $mod+Shift+5 move container to workspace number $ws5
bindsym $mod+Shift+6 move container to workspace number $ws6
bindsym $mod+Shift+7 move container to workspace number $ws7
bindsym $mod+Shift+8 move container to workspace number $ws8
bindsym $mod+Shift+9 move container to workspace number $ws9
bindsym $mod+Shift+0 move container to workspace number $ws10

# reload the configuration file
bindsym $mod+Shift+c reload
# restart i3 inplace (preserves your layout/session, can be used to upgrade i3)
bindsym $mod+Shift+r restart
# exit i3 (logs you out of your X session)
bindsym $mod+Shift+e exec "i3-nagbar -t warning -m 'You pressed the exit shortcut. Do you really want to exit i3? This will end your X session.' -B 'Yes, exit i3' 'i3-msg exit'"

# resize window (you can also use the mouse for that)
mode "resize" {
        # These bindings trigger as soon as you enter the resize mode

        # Pressing left will shrink the window’s width.
        # Pressing right will grow the window’s width.
        # Pressing up will shrink the window’s height.
        # Pressing down will grow the window’s height.
        bindsym j resize shrink width 10 px or 10 ppt
        bindsym k resize grow height 10 px or 10 ppt
        bindsym l resize shrink height 10 px or 10 ppt
        bindsym semicolon resize grow width 10 px or 10 ppt

        # same bindings, but for the arrow keys
        bindsym Left resize shrink width 10 px or 10 ppt
        bindsym Down resize grow height 10 px or 10 ppt
        bindsym Up resize shrink height 10 px or 10 ppt
        bindsym Right resize grow width 10 px or 10 ppt

        # back to normal: Enter or Escape or $mod+r
        bindsym Return mode "default"
        bindsym Escape mode "default"
        bindsym $mod+r mode "default"
}

bindsym $mod+r mode "resize"

# Start i3bar to display a workspace bar (plus the system information i3status
# finds out, if available)
bar {
        status_command i3status
}

Last edited by samtell (2020-07-24 01:54:09)

GaKu999 · 2020-07-24 02:10:15

Well, something is definitely telling systemd to suspend...

I'm none the wiser about i3 or this in particular and before the unintended call to suspend, can't see the precise cause for this...
Is this only replicated on i3 and plasma? Does this happen in the linux console as well?

Idk how to find the culprit but if you want to, lets increase the loglevel for the whole system so we can see who is calling for suspend.
The simplest way to do so is to add debug and ignore_loglevel to the kernel command line according to the wiki
So lets start on that.
Beware, it will be VERY verbose...so add the parameters with your bootloader before booting your entry, just to be safe.

Or you may wait for a mod or someone who knows about what is doing this and what do you need to change in your config to prevent this...

ondoho · 2020-07-24 12:32:01

GaKu999 wrote:

Well, something is definitely telling systemd to suspend...

Anyhow, it doesn't seem to "Crash" at all, it just goes to sleep by itself, unceremoniously, the same as when you close the lid:

Jul 23 19:44:24 marchbk systemd-logind[464]: Suspending...

The way I see it it could mean that your systemd is misconfigured, it could be that some other event (loose contact) sends the go-to-sleep signal, or that something around ACPI doesn't work as it should...
Searches for your hardware + variations of the ACPI errors might be helpful.
What is your hardware?

samtell · 2020-07-24 15:43:46

It's a razer blade 15 2019 base model.
Thanks for the advice from both of you. I will be looking into all the suggestion after work today and this weekend

Last edited by samtell (2020-07-24 15:44:16)

Arch Linux

#1 2020-07-23 01:29:13

Crash whenever I close my laptop

#2 2020-07-23 08:29:14

Re: Crash whenever I close my laptop

#3 2020-07-24 00:17:34

Re: Crash whenever I close my laptop

#4 2020-07-24 00:42:45

Re: Crash whenever I close my laptop

#5 2020-07-24 00:54:11

Re: Crash whenever I close my laptop

#6 2020-07-24 01:52:27

Re: Crash whenever I close my laptop

#7 2020-07-24 02:10:15

Re: Crash whenever I close my laptop

#8 2020-07-24 12:32:01

Re: Crash whenever I close my laptop

#9 2020-07-24 15:43:46

Re: Crash whenever I close my laptop

Board footer