Arch Linux

slopey

Member

Registered: 2020-01-27

Posts: 4

MacBook late 2013 model magnetic lid only works sometimes

Hi, I have a late 2013 model MacBook that I'm dual booting Arch Linux on. I'm having an issue where sometimes when I put the lid down the computer does not suspend and the computer stays on. However, this is a very inconsistent problem; sometimes the lid works and sometimes it doesn't, and I have no idea why. Any help would be appreciated.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,237

Re: MacBook late 2013 model magnetic lid only works sometimes

Welcome to the boards slopey.

Are you doing something that would prevent suspension in the "not working case" ? e.g. watching a video in chrome or so will invoke a power save disabling hint. Check the relevant list of these inhibitors with

systemd-inhibit --list

MODE block would mean the application sets up a block on the specified action (note that some programs are normal here, e.g. most power managers of desktop environments will "block" everything, because they provide their own tunables as to when something should happen.

Outside of that please post a

sudo journalctl -b

when it does and doesn't happen and use [ code ] [ /code ] tags when posting them.

slopey

Member

Registered: 2020-01-27

Posts: 4

Re: MacBook late 2013 model magnetic lid only works sometimes

Thank you for the help, V1del. After closing my computer lid and it went to sleep, I ran journalctl and received the following:

Jan 27 16:34:08 arch systemd-logind[399]: Lid closed.
Jan 27 16:34:08 arch systemd-logind[399]: Suspending...
Jan 27 16:34:08 arch systemd[1]: Reached target Sleep.
Jan 27 16:34:08 arch systemd[1]: Starting Suspend...
Jan 27 16:34:08 arch systemd-sleep[5685]: Suspending system...
Jan 27 16:34:08 arch kernel: PM: suspend entry (deep)
Jan 27 16:34:11 arch kernel: Filesystems sync: 0.010 seconds
Jan 27 16:34:11 arch kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Jan 27 16:34:11 arch kernel: OOM killer disabled.
Jan 27 16:34:11 arch kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Jan 27 16:34:11 arch kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jan 27 16:34:11 arch kernel: pcieport 0000:06:05.0: quirk: waiting for Thunderbolt to reestablish PCI tunnels...
Jan 27 16:34:11 arch kernel: pcieport 0000:06:06.0: quirk: waiting for Thunderbolt to reestablish PCI tunnels...
Jan 27 16:34:11 arch kernel: pcieport 0000:06:04.0: quirk: waiting for Thunderbolt to reestablish PCI tunnels...
Jan 27 16:34:11 arch kernel: pcieport 0000:06:03.0: quirk: waiting for Thunderbolt to reestablish PCI tunnels...
Jan 27 16:34:11 arch kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jan 27 16:34:11 arch kernel: sd 0:0:0:0: [sda] Stopping disk
Jan 27 16:34:11 arch kernel: ACPI: EC: interrupt blocked
Jan 27 16:34:11 arch kernel: ACPI: Preparing to enter system sleep state S3
Jan 27 16:34:11 arch kernel: ACPI: EC: event blocked
Jan 27 16:34:11 arch kernel: ACPI: EC: EC stopped
Jan 27 16:34:11 arch kernel: PM: Saving platform NVS memory
Jan 27 16:34:11 arch kernel: Disabling non-boot CPUs ...
Jan 27 16:34:11 arch kernel: smpboot: CPU 1 is now offline
Jan 27 16:34:11 arch kernel: smpboot: CPU 2 is now offline
Jan 27 16:34:11 arch kernel: smpboot: CPU 3 is now offline
Jan 27 16:34:11 arch kernel: ACPI: Low-level resume complete
Jan 27 16:34:11 arch kernel: ACPI: EC: EC started
Jan 27 16:34:11 arch kernel: PM: Restoring platform NVS memory
Jan 27 16:34:11 arch kernel: Enabling non-boot CPUs ...
Jan 27 16:34:11 arch kernel: x86: Booting SMP configuration:
Jan 27 16:34:11 arch kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Jan 27 16:34:11 arch kernel: CPU1 is up
Jan 27 16:34:11 arch kernel: smpboot: Booting Node 0 Processor 2 APIC 0x1
Jan 27 16:34:11 arch kernel: CPU2 is up
Jan 27 16:34:11 arch kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Jan 27 16:34:11 arch kernel: CPU3 is up
Jan 27 16:34:11 arch kernel: ACPI: Waking up from system sleep state S3
Jan 27 16:34:11 arch kernel: ACPI: EC: interrupt unblocked
Jan 27 16:34:11 arch kernel: pcieport 0000:06:06.0: quirk: waiting for Thunderbolt to reestablish PCI tunnels...
Jan 27 16:34:11 arch kernel: pcieport 0000:06:05.0: quirk: waiting for Thunderbolt to reestablish PCI tunnels...
Jan 27 16:34:11 arch kernel: pcieport 0000:06:03.0: quirk: waiting for Thunderbolt to reestablish PCI tunnels...
Jan 27 16:34:11 arch kernel: pcieport 0000:06:04.0: quirk: waiting for Thunderbolt to reestablish PCI tunnels...
Jan 27 16:34:11 arch kernel: pcieport 0000:06:06.0: quirk_apple_wait_for_thunderbolt+0x0/0xc0 took 24144 usecs
Jan 27 16:34:11 arch kernel: pcieport 0000:06:03.0: quirk_apple_wait_for_thunderbolt+0x0/0xc0 took 24133 usecs
Jan 27 16:34:11 arch kernel: pcieport 0000:06:05.0: quirk_apple_wait_for_thunderbolt+0x0/0xc0 took 24145 usecs
Jan 27 16:34:11 arch kernel: pcieport 0000:06:04.0: quirk_apple_wait_for_thunderbolt+0x0/0xc0 took 24156 usecs
Jan 27 16:34:11 arch kernel: ACPI: EC: event unblocked
Jan 27 16:34:11 arch kernel: sd 0:0:0:0: [sda] Starting disk
Jan 27 16:34:11 arch kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 27 16:34:11 arch kernel: ata1.00: unexpected _GTF length (8)
Jan 27 16:34:11 arch kernel: ata1.00: unexpected _GTF length (8)
Jan 27 16:34:11 arch kernel: ata1.00: configured for UDMA/133
Jan 27 16:34:11 arch kernel: OOM killer enabled.
Jan 27 16:34:11 arch kernel: Restarting tasks ... done.
Jan 27 16:34:11 arch systemd-logind[399]: Lid opened.
Jan 27 16:34:11 arch dhcpcd[4453]: wlp3s0: carrier lost
Jan 27 16:34:11 arch dhcpcd[4453]: wlp3s0: deleting route to 192.168.1.0/24
Jan 27 16:34:11 arch dhcpcd[4453]: wlp3s0: deleting default route via 192.168.1.1
Jan 27 16:34:11 arch systemd-sleep[5685]: System resumed.
Jan 27 16:34:11 arch systemd[1]: systemd-suspend.service: Succeeded.
Jan 27 16:34:11 arch kernel: video LNXVIDEO:00: Restoring backlight state
Jan 27 16:34:11 arch kernel: PM: suspend exit
Jan 27 16:34:11 arch kernel: audit: type=1130 audit(1580171651.726:197): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 27 16:34:11 arch kernel: audit: type=1131 audit(1580171651.726:198): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 27 16:34:11 arch 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'
Jan 27 16:34:11 arch 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'
Jan 27 16:34:11 arch systemd[1]: Started Suspend.
Jan 27 16:34:11 arch systemd[1]: Stopped target Sleep.
Jan 27 16:34:11 arch systemd[1]: Reached target Suspend.
Jan 27 16:34:11 arch systemd[1]: Stopped target Suspend.
Jan 27 16:34:11 arch systemd-logind[399]: Operation 'sleep' finished.
Jan 27 16:34:15 arch dhcpcd[4453]: wlp3s0: carrier acquired
Jan 27 16:34:15 arch dhcpcd[4453]: wlp3s0: IAID c2:d5:22:30
Jan 27 16:34:15 arch dhcpcd[4453]: wlp3s0: rebinding lease of 192.168.1.55
Jan 27 16:34:16 arch dhcpcd[4453]: wlp3s0: probing address 192.168.1.55/24
Jan 27 16:34:21 arch dhcpcd[4453]: wlp3s0: leased 192.168.1.55 for 86400 seconds
Jan 27 16:34:21 arch dhcpcd[4453]: wlp3s0: adding route to 192.168.1.0/24
Jan 27 16:34:21 arch dhcpcd[4453]: wlp3s0: adding default route via 192.168.1.1
Jan 27 16:34:23 arch audit[5847]: USER_ACCT pid=5847 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="slopey" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Jan 27 16:34:23 arch sudo[5847]:   slopey : TTY=pts/1 ; PWD=/home/slopey ; USER=root ; COMMAND=/usr/bin/journalctl -b
Jan 27 16:34:23 arch audit[5847]: CRED_REFR pid=5847 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_unix,pam_permit,pam_env acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Jan 27 16:34:23 arch audit[5847]: USER_START pid=5847 uid=0 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Jan 27 16:34:23 arch sudo[5847]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jan 27 16:34:23 arch kernel: audit: type=1101 audit(1580171663.069:199): pid=5847 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="slopey" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Jan 27 16:34:23 arch kernel: audit: type=1110 audit(1580171663.069:200): pid=5847 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_unix,pam_permit,pam_env acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Jan 27 16:34:23 arch kernel: audit: type=1105 audit(1580171663.069:201): pid=5847 uid=0 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'

I closed my lid again, and this time my laptop did not go to sleep. Running journalctl again, I got the following:

Jan 28 08:05:05 arch systemd-logind[399]: Lid closed.
Jan 28 08:05:09 arch systemd-logind[399]: Lid opened.
Jan 28 08:05:25 arch audit[10148]: USER_AUTH pid=10148 uid=1000 auid=1000 ses=1 msg='op=PAM:authentication grantors=pam_unix,pam_permit acct="slopey" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jan 28 08:05:25 arch audit[10148]: USER_ACCT pid=10148 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="slopey" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jan 28 08:05:25 arch sudo[10148]:   slopey : TTY=pts/0 ; PWD=/home/slopey ; USER=root ; COMMAND=/usr/bin/journalctl -b
Jan 28 08:05:25 arch audit[10148]: CRED_REFR pid=10148 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jan 28 08:05:25 arch kernel: audit: type=1100 audit(1580227525.009:272): pid=10148 uid=1000 auid=1000 ses=1 msg='op=PAM:authentication grantors=pam_unix,pam_permit acct="slopey" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jan 28 08:05:25 arch kernel: audit: type=1101 audit(1580227525.009:273): pid=10148 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="slopey" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jan 28 08:05:25 arch kernel: audit: type=1110 audit(1580227525.009:274): pid=10148 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jan 28 08:05:25 arch kernel: audit: type=1105 audit(1580227525.009:275): pid=10148 uid=0 auid=1000 ses=1 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'
Jan 28 08:05:25 arch audit[10148]: USER_START pid=10148 uid=0 auid=1000 ses=1 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'
Jan 28 08:05:25 arch sudo[10148]: pam_unix(sudo:session): session opened for user root by (uid=0)

Weirdly enough, it seems like literally nothing happens after the lid closes. It's detected by the system, but no further action is taken.
And also, here is a list of my inhibitors:

WHO     UID  USER   PID  COMM    WHAT  WHY                                MODE 
Discord 1000 slopey 4832 Discord sleep Application cleanup before suspend delay

1 inhibitors listed