В Sun, 14 Dec 2014 22:19:07 +0100 Aaron Digulla <digulla@hepe.com> пишет:
Am 14.12.2014 um 21:54 schrieb John Andersen:
On 12/14/2014 04:39 AM, Aaron Digulla wrote:
Am 13.12.2014 um 12:45 schrieb Marcus Meissner:
First guess would be the dracut update, where we added a filesystem check after hibernation.
I have
Name : dracut Version : 037 Release : 17.9.1 Architecture: x86_64 Install Date: Sa 06 Dez 2014 00:20:49 CET
I also have NFS mounts. Are they excluded properly?
When the system hangs after restart, I just see a very dark background default blotch pattern, so graphics mode is there. But network isn't (system doesn't respond to ping).
Any way I could quickly disable the check to see whether it helps?
Regards,
Since you are the only one complaining about suspend/resume not working, (it continues to work perfectly for me and many others), I don't think you should assume any software update broke your system. Its just as likely an existing problem was unmasked.
Over the years, this kind of problem has been caused by modules not being unloaded pre suspend or reloaded post suspend. https://forums.opensuse.org/showthread.php/501343-openSUSE-13-1-resume-from-...
Also the google search: https://www.google.com/#q=modules+to+unload+on+suspend+opensuse may be helpful.
There is no indication of any kind of problem in /var/log/pm-suspend.log
That rings the bell. Recent patch re-enabled pm-utils in systemd: * Tue Nov 25 2014 gber@opensuse.org - temporarily re-enable Forward-suspend-hibernate-calls-to-pm-utils.patch until boo#904828 can be addressed properly So it is quite possible that you suddenly started to use pm-utils where you did not before. How exactly you hibernate now and before (using GUI menu, some command)? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org