You are not logged in.
Greetings,
I'm having a problem running any kernel above 3.12.*
The later 3.14.* kernels also have the below problem, but I'm not sure exactly which version is the threshold.
Basically, with a kernel above 3.12.*, every time my machine suspends/hibernates/sleeps, it is impossible to wake up. It does not respond to keypresses, mouse movement, nor holding down the power button. I can't even hard power-off holding down the power button.
In order to get it out of hibernate/suspend, I have to unplug the power and also unplug the battery. Then I can restart...
This is what I'm running now:
Linux tinydada-a 3.12.3-1-ARCH #1 SMP PREEMPT Wed Dec 4 21:59:02 CET 2013 i686 GNU/Linux
on an Acer Aspire One 0751h.
I haven't been able to find a similar thread concerning the issue, but if there is one, I apologize for not contributing to that thread.
Let me know if it would be a good idea to post journalctl -blk
I appreciate anyone's help in trying to remediate this issue.
Thanks!
~WK
Offline
I updated to 3.15-1 to see if anything would improve. It appears that now it won't't even suspend when I close the laptop lid, it will just stay on.
If I force it to suspend with systemctl suspend, it acts as it would with the 3.14 kernel where it goes into suspend but it can't be woken up.
Where can I look on my system to see what is causing the problem so that I can remedy it?
Thanks.
Offline
bump...
I'm still having this problem... even with 3.16... Any thoughts as to how I can approach troubleshooting this?
I doubt the 3.14 LTS kernel will work since I've had this problem since 3.12.
Offline
I wasn't sure whether to post this here, or at the apparently solved https://bbs.archlinux.org/viewtopic.php?id=186922
My problem with suspend/resume is now intermittent, sometimes suspend (or more to the point, resume) will work. Other times, I'll attempt to resume my computer only to be met with a blank, unresponsive screen.
Whether it is related or not, there was one cold boot with the same issue and in that case (but not usually after resuming) the machine was working to some degree - I managed to log in blindly and reboot successfully.
Offline
My problem with suspend/resume is now intermittent, sometimes suspend (or more to the point, resume) will work. Other times, I'll attempt to resume my computer only to be met with a blank, unresponsive screen
+1 I have the same problem, resuming from suspend to ram sometimes doesn't work. I just tried to resume and I had to forcefully shut down my laptop, because it was totally unresponsive. There's nothing in systemd journal, even the suspension is not logged and the journal restarts from when I rebooted the system. I'm using kernel 3.16.3, by the way.
Offline