You are not logged in.
Hello there,
For some time now, I have been using Arch Linux on my laptop. Sometimes when I open the lid after the laptop has been in suspend mode, after a couple of seconds (sometimes minutes) the screen suddenly turns black, after which the system starts to boot again.
This problem is not only very annoying, it is dangerous too, as it often results in the system not being shut down properly. One time I started an update quickly after waking up the machine, during which it crashed, leaving me with an unusable system. After a fresh install of Arch, the problem was gone for a couple of weeks but then appeared again.
I paid attention to when the problem happens (with charger plugged in, using Bluetooth, running on low battery, etc.). The only trend that really stands out it the fact that it happens quickly after resuming from suspend mode.
I have no idea where this problem comes from. Where should I start looking for error messages, warnings, etc.?
Thanks in advance
Offline
Welcome to the forums.
journalctl -b -1to look at the journal from the previous boot, but you might find the journal is missing if the system isn't shutting down properly.
journalctl -bfor the current boot. If there are related errors prior to the crash, you might be able to find something, but if there's nothing prior, you may draw a blank.
Is Arch the only OS installed? If not does only happen with Arch?
How are you suspending?
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
Running
journalctl -b -1did not give me anything useful. Right now, I can't paste any logs here, because it hasn't happened today. What I remember from checking journalctl
Arch is not the only OS installed, but it is the only OS that is used. The other OS installed is Windows. I did not experience anything like this there, but that could very well be because I almost never use it.
To put my computer in suspend mode, I either press press the suspend mode in the power menu (I'm using Gnome), or I use the command
systemctl suspend. The machine automatically wakes up when I open the laptop lid again.
Offline
Boot into Windows and make sure Fast Start (or Fast Boot?) is disabled. This is different from similar-sounding BIOS options.
As well as the journal, you could try coredumpctl to see if there's a core dump following the crash. But if the machine is just powering off at a hardware level, you're not going to find traces.
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
So this morning I disabled "Fast Startup" on the Windows installation. Just now when I waked the laptop from suspend it happened again. Unfortunately, this did not make a difference.
The coredumctl command also did not give me any signals from around the time of the crash. It's starting to look like this could be a hardware issue then... But thanks for your suggestions anyway ![]()
Offline
Does it happen in Windows?
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
after a couple of seconds (sometimes minutes)
1. after disabling windows fast-start make sure to reboot windows and linux at least twice
2. check the boot after such crash for MCE errors in the journal/dmesg
3. what kind of CPU is this? Are you undervolting it?
4. post a journal that covers a successful S3 cycle.
Offline