You are not logged in.

#1 2016-11-06 01:08:04

Pablo1107
Member
Registered: 2016-11-06
Posts: 3

Suspend don't resume on Intel ATOM-based netbook

First post in Arch forums, I really appreciate how is this community and how well-documented are many things and that I supposed is because of the work of communities like this one.

Suspend just worked perfectly a week ago. I did a general update (pacman -Syu) and install Xfce4 and ligthdm -yeah, i know... too many things in one run-.

Didn't notice till' recently when I tried to suspend (system goes down, led flashing, fan off) and resume it, the fans turned on, the display is black and no interaction is posible, not even blindly a terminal to do a "reboot" from there or something like that.

Searching and trying to learn how the suspension system works on Arch (i'm a newbie but I hate to post for problems) I found that I didn't have installed pm-utils which is curious cause in early logs from journalctl it shows PM running the suspend after a "systemctl suspend" command. Installing it and doing a "pm-suspend" didn't work.

Things I tested:

    Downgrade kernel to linux-4.6 when suspend work.
    Create a swap file and add in the grub config file "GRUB_CMDLINE_LINUX="resume=/swapfile"
    Install pm-utils and doing "pm-suspend"
    Test with various WM and from TTY.

I can say I have no clue whatsover for what it's causing the problem, but I'm new to Arch so maybe a little help from you would be great.

Some logs: journalctl when systemctl suspend http://pastebin.com/xpmnkK2Z

journalctl when pm-suspend http://pastebin.com/1Mm8Qt80 (notice the "PM: detected memory nosave" part)

pm-suspend http://pastebin.com/Uz8nYBbB

Last edited by Pablo1107 (2016-11-06 03:35:06)

Offline

#2 2016-11-08 21:14:15

Pablo1107
Member
Registered: 2016-11-06
Posts: 3

Re: Suspend don't resume on Intel ATOM-based netbook

Anyone have any idea?

Offline

#3 2016-11-13 15:47:26

Pablo1107
Member
Registered: 2016-11-06
Posts: 3

Re: Suspend don't resume on Intel ATOM-based netbook

Well, after some debugging I found out that the problem was caused by NetworkManager and not xfce4-power-manager.

Some idea why NetworkManager produce this error and how can I fixed it?

Offline

Board footer

Powered by FluxBB