You are not logged in.
Suspend to disk does not work for me since kernel 3.7.4 +. I am sure it is something that can be fixed but I am too lazy to fix it.
Last edited by illusionist (2013-03-20 22:02:52)
Never argue with stupid people,They will drag you down to their level and then beat you with experience.--Mark Twain
@github
Offline
seems to be fixed in 3.9. No hangs since 3 days with lots of suspends.
Offline
My setup
Kernel 3.8.4.1, w530 with Optimus (Intel 4000 and 1000M Quadro) enabled and kernel options acpi_osi=Linux acpi_backlight=vendor**
Close laptop -> suspend
Open laptop -> wake, but with a blank screen. On all consoles.
As far as I can tell this is what most people in this thread have.
However, could somebody verify this workaround?
Fn + backlight (F8/F9) = instant screen, everything is fine again. Screen wakes and continues as expected
**Without this option I had no problems whatsoever regarding suspend/wake, but had some problems adjusting brightness.
edit: just read https://bbs.archlinux.org/viewtopic.php?id=159379. Seems I have 'discovered' that bug (and workaround) but it might not be the same as the ones mentioned here.
Last edited by drdnl (2013-03-30 11:02:50)
Offline
I have never been able to change brightness after a suspend (Toshiba z835). This is a blocking issue for me.
--- edit ---
Kernel 3.8.5 solves the suspend issue. As a bonus, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651741 explains how I can make brightness work even after suspend
Last edited by benob (2013-04-04 13:17:34)
Offline
Upgrading to 3.8.5-1 solved it for me.
Offline
Still having similar issue on Thinkpad Edge e520.
Tried kernels 3.8.1 , 3.8.5, 3.9 (mainline) with no success.
Computer suspends, but when trying to resume it blinks whith power led, like starting to work and immediatly stops, repeating from begining (blink-stop, blink-stop).
Offline
Can confirm, like user benob, that this issue is fixed in 3.8.5-1.
Offline
Same issue here (resume to blank screen and no response) on ThinkPad X60, tried the LTS kernel - works like a charm, so the issue is in the kernel I guess.
I have a Dell Latitude E6410 and experience similar (if not, the exact same) symptoms. I have issues using the latest core kernel 3.8.10-1. When I resume from suspend the backlight from the screen turns on, the harddisk spin on but nothing else happens. Other TTY's are not available and keyboard is not responding on anything, even the LED for caps-lock won't toggle. When I open the journal (journalctl -a) I can't see any log entries being made after suspending so there is no way to debug this issue from the logs.
What I did notice is that the problem only occurs when the power is disconnected. When my laptop is connected to AC it has no issues suspending / resuming. Also, when switching to LTS kernel (3.0) the issue is gone.
Since the boot time takes considerably longer with the 3.0 kernel I'd really like to find a proper solution for this. Can anyone else confirm the above behavior (especially the AC connectivity symptom which is kinda odd).
seems to be fixed in 3.9. No hangs since 3 days with lots of suspends.
How did you install 3.9? From AUR? I'd like to try but is it recommendable as a daily driver? (I use my laptop for work)
Offline
Hello,
I agree with perkonix's description, I have had this problem since kernel 3.6. Once or twice when my lenovo t420 managed to wake up from systemd suspend, I got a message upon resume saying something about an error related to iwlwifi. So I tried suspending only after turning off my wifi, but still no success. Around 40% of the time, I have to turn off my laptop by holding down the powerbutton and reboot.
PLEASE somebody find a solution to this, it is excruciating.
Thanks
Last edited by mark-o-solo (2013-05-08 12:16:48)
Offline
@mark-o-solo: did you try to unload the iwlwifi module before suspend (from /usr/lib/systemd/system-sleep)?
Offline
No, I'll do that and report after a few tries, thanks for the hint.
Offline
After upgrade from kernel 3.8.10 to 3.9.2 I experienced this issue: wake up from suspend only give me a black screen with a dash character on the top left corner. I can't do anything else but to force power off my comp and power on a gain ..
Offline
I still getting the completely blank screen after resuming, and is needing to reboot (the hard way) the system Im using kernel 3.9.2-1 and having a Nvidia 9400M and Nvidia 9600M GT.
Offline
After some tries, I have concluded that the problem is not related to the iwlwifi module. Also, since I have an exact partition copy of my arch install on my desktop PC, and I have never had a problem there, the problem must be hardware related.
The fact that it works on AC but not on battery suggests a power problem upon resume from suspend ?
Offline
I added myself to the `power` group, and haven't since then got any problem with resuming from suspend using systemd. I'm not sure if this is the actual solution of the problem or what. I'm currently running Linux kernel 3.9.2-1 x64
Edit:
It happend again Cant understand what the problem is. Btw using Systemd 204-1
Last edited by thall (2013-05-21 18:47:10)
Offline
Problem for me was solved by disabling HPET timer in my BIOS. More info: https://bbs.archlinux.org/viewtopic.php?id=128881
EDIT: No, not solved, it's happening again the next day! BIOS setting made no difference. Resume works only if I use pm-suspend command. If I use systemd or upower (which I think is what Xfce's power management uses), resume always fails. Monitor stays in standby and USB devices don't come back on (like the light on my mouse).
Last edited by nLinked (2013-05-23 08:20:52)
Offline
I have the same issue on Thinkpad x220. I'm currently running Linux kernel 3.9.4-2-ck.
Offline
Sorry for taking this thread up, but I'm experiencing the same issue when the notebook goes on standby, and it is very difficult to me to go on this way, so it would be nice to know if someone managed to solve the problem and how. I've spent some time searching but nothing helped. Thanks.
Offline
The only solution I know of is to install a kernel with a version below 3.7, preferably the lts kernel. Though the lts kernel is at version 3.0, that might be too old for you.
The bug is still open for the current kernel: https://bugs.archlinux.org/task/33516
Maybe if more people vote it up, it gets fixed...
Last edited by Orim (2013-06-19 08:10:04)
Offline
I am experiencing this very same issue on my PC, Intel D865PERL mainboard, 2.4 gHZ Intel Pentium 4, I am using ck-kernel 3.9.7-1-ck, and elevator BFQ. After resuming I often got a black screen, but with a blinking cursor. After that I have to restert by resetting my machine, so if I didn't save everything before hibernating they are completely lost. in /var/log/pm-suspend.log I have no error messages.
Offline
I am using uswsusp, and uresume hook, through command line "sudo pm-hibernate", my /etc/suspend.conf:
snapshot device = /dev/snapshot
resume device = /dev/sda3
suspend loglevel = 2
compute checksum = y
compress = y
threads = y
Offline
Still happens to me, using linux 3.12.7-1-ARCH and systemd 208
Offline
Still happens to me, using linux 3.12.7-1-ARCH and systemd 208
the same to me
Linux Arch 3.12.9-2-ARCH #1 SMP PREEMPT Fri Jan 31 10:22:54 CET 2014 x86_64 GNU/Linux
Offline
same here, with current 32bits linux and linux-lts kernels, on Thinkpad r50e
edit : maybe an other problem. Suspend was not working at all. Works now, with linux-lts-3.0.93-1 (slightly older). (But that one messes up cpupower for me...)
Last edited by scar (2014-02-18 09:46:29)
“The future has already arrived. It's just not evenly distributed yet.”
― William Gibson
Offline
I *think* I have a similar issue. It only occurs very seldomly with suspend and is major problematic.
Laptop: ASUS Zenbook ux301 with intel Iris graphics.
Basically after suspend the laptop appears completely dead. It can't resume or wake from suspend.
The LED on the power button on the keyboard is off and the computer doesn't respond to the on button (which is a soft key on the keyboard).
Plugging it into AC at this time doesn't change anything either.
There is no way to get the laptop on again since it has a builtin battery. Perhaps only after the battery depletes would it wake (after a charge).
This is my theory anyway, since at first I thought it was a hardware error and sent it in.
Offline