You are not logged in.
I messed my post. see next
Last edited by agumonkey (2013-09-25 12:13:44)
Offline
The -2 linux package just has a fix for a skge (network) module regression. Like Aaron Lu says in the bug report, he can't reproduce the bug, and needs some extra information to diagnose the problem. Jeff Pohlmeyer looks to have done most of the hard work and isolated a cluster of commits where the problem surfaced. If you can find the time to assist with the investigation and share your findings on the bug report, it may help find a fix sooner.
Link to Jeff's comments : https://bugzilla.kernel.org/show_bug.cgi?id=61781#c6
Offline
Same thing here. Kernel 3.11.1 on i686 fails to resume dropping me down at login prompt.
Any systemd command after that results in the previously reported D-Bus connection failed error.
Downgrade to 3.10.10 fixes it.
Offline
And the glibc 2.18-5 push of today has brought back the problem for me (kern 3.11.1-2 too)
Offline
Are you guys still having the problem? I'm on kernel 3.11.2 , x86_64 install and I can't resume from suspend.
Offline
Are you guys still having the problem?
I didn't update yet, I'm also waiting to check if the problem is still present.
I'm on kernel 3.11.2, x86_64 install and I can't resume from suspend.
So the problem isn't just about 32bit anymore?
"For even better randomness, let your cat walk on the keyboard." -- From the "Advanced Linux Programming" book
Offline
The 64bit 3.11.2 kernel works for me. Still same problem with 32bit.
Offline
For me, on i686, the problem still persist. Curently using LTS version to avoid the bug.
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
I was wondering if anyone could help fix this issue. When i close down my laptop lid and open it back up again the gnome 3 lock screen appears as expected. But when i log back in gnome's networkmanager application doesn't start back up. Ive tried the "systemctl enable networkmanager" command and nothing happens the terminal just freezes. Also it dosn't let me shut down or restart the laptop with both the GUI and terminal nothing happens. The networkmanager and the shutdown and restart functions work fine before I close the lid down.
Offline
Is this a 32-bit laptop with an up-to-date kernel?
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Online
Yes its a 32-bit machine with the latest kernel version.
Offline
Then, from the symptoms you've described, you're probably suffering from the same bug described in that topic. An interim "solution" is to downgrade your kernel or switch to the lts kernel, though you should consider helping to isolate and debug the problem by participating in the kernel bug report.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Online
Merging threads
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Updated to the latest kernel. Suspend still breaks systemd on my 32bit computer.
Offline
Same situation with kernel 3.11.2-1
Resumed from suspend, first I found I couldn't establish any network connection, then, not even be able to use reboot command.
Last edited by rongmu (2013-10-01 06:18:26)
Offline
Reading the last comments https://bugzilla.kernel.org/show_bug.cgi?id=61781#c19 they seems to be closing in on the issue. Pretty interesting investigation.
Offline
Ugly workaround script (works for me, YMMV)
#!/bin/bash
strace -p 1 -o /dev/null 2>/dev/null &
StracePid=$!
sleep 1
systemctl suspend
kill $StracePid
Note: You'll need to have strace installed (pacman -S strace) and you might need to run this script as root.
.
Offline
Ugly workaround script (works for me, YMMV)
#!/bin/bash strace -p 1 -o /dev/null 2>/dev/null & StracePid=$! sleep 1 systemctl suspend kill $StracePid
Note: You'll need to have strace installed (pacman -S strace) and you might need to run this script as root.
.
Could you explain what appears to me as black magic ? strace interfere with kernel time ?
Offline
Could you explain what appears to me as black magic ? strace interfere with kernel time ?
Your guess is as good as mine.
.
Offline
As an only mildly-educated guess, if a running strace fixes the problem, the underlying problem is likely a race condition. The strace adds just enough lag or delay to alleviate the conflicting timing.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
As an only mildly-educated guess, if a running strace fixes the problem, the underlying problem is likely a race condition. The strace adds just enough lag or delay to alleviate the conflicting timing.
Ok, so the script is a way to "install" some operations post wake up. I still wonder if it's strace specific, gonna try with other programs.
ps: just realized strace was attaching to systemd ..
Last edited by agumonkey (2013-10-01 11:33:39)
Offline
[Ok, so the script is a way to "install" some operations post wake up ...
No - at least that's not what I was suggesting. Again, my suggested explanation is a bit of a guess, but I suspect it is simply due to the strace making every step take a little longer. This added time allows some processes or threads to get to a needed place before some other process or thread that relies on them.
Again, this is a guess, but it is based on experience with buggy multithreaded processes: in my (admittedly limited) experience, if simply running an strace on a process makes the buggy behavior disappear, the buggy behavior is likely due to a race condition of one process getting "ahead" of another process that it should be synchronized or coordinated with.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Same problem here with kernel 3.11.2-1-i686.
Downgrade to kernel 3.11.1-2-i686 but the problems continued.
The kernel 3.11.1-1-i686 fixed both the wireless and the shutdown
problems after resume from suspend.
Thank you all...
Offline
Please don't post simply to echo that you have the same issue: if you have substantive information, add that, but otherise it is just empty posting that clutters the thread.
Offline
Same problem here with kernel 3.11.2-1-i686.
Downgrade to kernel 3.11.1-2-i686 but the problems continued.
The kernel 3.11.1-1-i686 fixed both the wireless and the shutdown
problems after resume from suspend.
Thank you all...
Hm, my machine seems to be still on 3.11.1-1, at least uname -a yields
3.11.1-1-ARCH #1 SMP PREEMPT Sat Sep 14 20:31:35 CEST 2013 i686 GNU/Linux
Does that mean, that there's an other reason for this behaviour, here?
Offline