You are not logged in.
So, I'm on 3.12 stable right now. So far, I'm not having any systemd crashes after waking up from sleep.
~ » pacman -Qi linux-suicidal-squirrel|grep -i version
Version : 3.12-1
Offline
linux 3.12-1 is now in testing repo.
Offline
Hi! Ok it's clear about this bugfix. But could you please explain me for the future: I have this link for example. And how I can to uderstand in what kernel version this bugfix was commited? Why it's impossible to wait in 3.11.10-1 version for example? Or this third number was added by archlinux developers?? Sorry for offtop.
Offline
And how I can to uderstand in what kernel version this bugfix was commited? Why it's impossible to wait in 3.11.10-1 version for example?
One way how to find out is to click at parent link (http://git.kernel.org/cgit/linux/kernel … 6c15c01bfb) of that patch, there you will see "Linux 3.12-rc7", so it means it should be fixed there (at least that would make sense to me).
Why is it impossible in 3.11? I'm not sure, I guess you can't want to have it repaired in 3.11, if upstream fixes it in 3.12...
English isn't my first language.
Is Arch Linux user called archer? Where are our bows and arrows?
Offline
One way how to find out is to click at parent link (http://git.kernel.org/cgit/linux/kernel … 6c15c01bfb) of that patch, there you will see "Linux 3.12-rc7", so it means it should be fixed there (at least that would make sense to me).
Why is it impossible in 3.11? I'm not sure, I guess you can't want to have it repaired in 3.11, if upstream fixes it in 3.12...
Thank you for explanation!
Offline
So, I'm on 3.12 stable right now. So far, I'm not having any systemd crashes after waking up from sleep.
~ » pacman -Qi linux-suicidal-squirrel|grep -i version Version : 3.12-1
Just got the stable `Linux 3.12.0-1-ARCH` running, did a few manual suspend and no issues so far, time will tell but I trust the dev bisect and rollback mentionned in the bug report.
Offline
We should be cautious about that. Since this change will be reintroduced in the future and if not properly tested as previously, the problem may reappear.
Last edited by dagon666 (2013-11-14 14:26:24)
Offline
bug is closed. 3.12 is out. Test it for a few days. If all's OK, I'll mark the thread as solved.
Offline
I've just been watching this thread as I had the same issue - but for me it happened on 100% of resumes from suspend. I just upgraded to 3.12 and it works fine now through several suspends.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Yes, I confirm fixing this bug in 3.12. Even Gnome Shell starts to perform autosuspending with 3.11 it didn't do that.
Offline
Confirming fix with 3.12, no issues over several suspends until now.
Offline
Yep, works perfectly so far. At last
If you have built castles in the air, your work need not be lost; that is where they should be. Now put foundations under them.
Henry David Thoreau
Registered Linux User: #559057
Offline
But I get this sleep resume failure after I upgraded the kernel to 3.12. After resuming, my computer just completely freezes.I don't know how to begin diagnosing the problem. I ran journalctl but the only recent error I found was
Failed to open private bus connection: Failed to connect to socket /run/user/1000/dbus/user_bus_socket: No such file or directory
However, I had the error before I upgraded. So I'm at a loss.
How do i diagnose and possibly fix my problem?
Offline
I have also problem with resuming from suspend on 3.12. After resume, i have black screen, can't kill X, can only one time switch to tty, but in tty i can't do anything. Only hard reset. Kernel 3.9 works ok with resuming from suspend.
Offline
I have also problem with resuming from suspend on 3.12. After resume, i have black screen, can't kill X, can only one time switch to tty, but in tty i can't do anything. Only hard reset. Kernel 3.9 works ok with resuming from suspend.
Same problem here. Everything worked ok on 3.11.
Offline
Still no fix after upgrade to kernel 3.12.1 .
Offline
I still have the same problem. Do any of you know what the problem may be? I don't want to downgrade because I have a dependency with virtualbox.
Last edited by shadeless (2013-11-23 13:18:49)
Offline
firekage wrote:I have also problem with resuming from suspend on 3.12. After resume, i have black screen, can't kill X, can only one time switch to tty, but in tty i can't do anything. Only hard reset. Kernel 3.9 works ok with resuming from suspend.
Same problem here. Everything worked ok on 3.11.
I can't downgarde kernel because of nvidia drivers.
Offline
OK I had the same error but it was fixed when upgrading to kernel version 12.5
But now a new problem occurs. When I suspend my computer I get stuck with a black screen and an underscore in the upper left corner. I can't do anything except for shutting down my laptop with the "long power off press".
Does anyone experiance the same issue? I searched the forums and the web but no one has the same problem after upgrading.
I can't help but think that these issues are connected.
Offline
Have you read ealier posts? I have the same thing on desktop computer with new kernel.
Offline
Fixed as of 3.12.8
Offline
Incredible. Even the 3.13.4 kernel doesn't fix this issue. Upon resume the screen is blank, after some 20 seconds the desktop is very briefly shown, and then the monitor goes in sleep mode. If i enter a terminal with alt+f(1), the login prompt appears and gets stuck after entering login name. I use latest KDE as DE.
Offline
I am having this issue as well. With kernel 3.14.1 64-bit and GNOME 3.12 when GNOME autosuspends after the set 15 minutes my illuminated keyboard and mouse turn off but my case lights stay one. When I press a key on my keyboard, the keyboard and mouse lights come back but there is no response on the monitor and the hardisks do not spin; I have to manually reset with the hardware button. when I use the `systemctl suspend` command, everything works beautifully! What the heck is going on?
"Melody reigns supreme!"
-J. J. Johnson
Offline