You are not logged in.
I have a MacBook Air on which I'm dual-booting into Arch Linux (which is the default) with GNOME desktop. I'm unable to use suspend as there's a bug which cause the screen backlight to go dark upon resume. Instead, I'm hibernating to disk -- specifically, I'm using a swap file, and I have hibernate when closing the lid. Originally, I had made the swapfile 4GBs (machine has 8GBs for RAM) and now it has 8GBs, but I still have an issue where very third or fourth time I open the lid, the resume stalls. It'll go thru the grub boot screen and a cursor will blink the top left. Much of the time, it'll blink a few times before going dark and then presenting the GNOME login. However, sometimes the cursor will blink and then become solid and stall. The only way to resolve is by hard-booting the laptop (holding down the power button).
Again, keep in mind that hibernates are successful, but sometimes it stalls when resuming.
I have the following kernel parameters:
grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet resume=UUID=36a92e2f-3b6e-4b67-ad35-41c4855ee76c resume_offset=2136064 pcie_aspm=force i915.i915_enable_rc6=1"I have the following in /etc/systemd/logind.conf:
cat /etc/systemd/logind.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
#
# You can override the directives in this file by creating files in
# /etc/systemd/logind.conf.d/*.conf.
#
# See logind.conf(5) for details
[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#InhibitDelayMaxSec=5
#HandlePowerKey=poweroff
#HandleSuspendKey=suspend
#HandleHibernateKey=hibernate
HandleLidSwitch=hibernate
#HandleLidSwitchDocked=ignore
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
#IdleAction=ignore
#IdleActionSec=30min
#RuntimeDirectorySize=10%
#RemoveIPC=yesThe swap file is on my home partition:
cat /etc/fstab
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda5
UUID=211a4929-dc81-4290-9f81-578a06bd3318 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda4
UUID=a5ec7cef-8002-48c9-ae2f-5b7c5dee4c59 /boot ext4 rw,relatime,stripe=4,data=ordered 0 2
# /dev/sda6
UUID=36a92e2f-3b6e-4b67-ad35-41c4855ee76c /home ext4 rw,relatime,data=ordered 0 2
/home/.swap none swap defaults 0 0
ls -lh /home/.swap
-rw------- 1 root root 7.7G May 3 06:44 /home/.swapAnd just to double check, I've put in the right offset in the kernel parameters:
filefrag -v /home/.swap | head
Filesystem type is: ef53
File size of /home/.swap is 8192000000 (2000000 blocks of 4096 bytes)
ext: logical_offset: physical_offset: length: expected: flags:
0: 0.. 0: 2136064.. 2136064: 1:
1: 1.. 2047: 2136065.. 2138111: 2047: unwritten
2: 2048.. 32767: 2144256.. 2174975: 30720: 2138112: unwritten
3: 32768.. 63487: 2174976.. 2205695: 30720: unwritten
4: 63488.. 94207: 2205696.. 2236415: 30720: unwritten
5: 94208.. 124927: 2236416.. 2267135: 30720: unwritten
6: 124928.. 155647: 2267136.. 2297855: 30720: unwrittenI've been unable to find any associated errors or anything of interest in the journal logs, but I'm going to take a closer look next time it happens. Since it is a seemingly random issue, it's difficult to recreate.
Anyone else ever encountered such a thing?
Last edited by jdubs (2015-05-04 08:01:09)
Offline
You can use this https://aur.archlinux.org/packages/mba6x_bl-dkms/ to fix the backlight bug.
I do sometimes (not very often) get a black screen when resuming from suspend but it is fixed by switching to a different virtual console and then back.
Offline
Your post is doubly helpful. I'll see if I can resolve the issue by switching console.
Offline
Issue reoccurred today. Was unable to switch terminals and had to do a hard reboot. I don't believe that journald is logging anything when this issue occurs as I'm not sure it even gets that far.
Isn't there a setting that I can tweak to change the size of the "image" created when the computer hibernates? I could've swore I saw it somewhere, but I'm unable to find it.
Offline