https://bugzilla.novell.com/show_bug.cgi?id=853773 https://bugzilla.novell.com/show_bug.cgi?id=853773#c0 Summary: traps: systemd[1] general protection, after resuming from suspend to RAM on i586 Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: i686 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: jimc@math.ucla.edu QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Versions: OpenSuSE-13.1 final, kernel-desktop-3.11.6-4.1.i686 , systemd-208-6.1.i586 Symptom: After the system has successfully suspended to RAM and is woken by Wake-on-LAN, I see this message in syslog: kernel: [68547.311035] traps: systemd[1] general protection ip:b7495df1 sp:bfe5a920 error:0 in libc-2.18.so[b7452000+1ab000] All kinds of stuff doesn't work after that; in particular you can't log in nor signal a shutdown; you have to kill the box by leaning on the power button. See https://bugzilla.kernel.org/show_bug.cgi?id=61781 in which it's recommended to revert the culprit git commit. The above bug report is mentioned by https://bugs.freedesktop.org/show_bug.cgi?id=69663 in connection with the reported error message. Reproducibility: Most comment posters report that it happens to them every time, but I got through several suspend-resume cycles and survived. My hardware is an AMD Athlon Neo X2 Dual Core Processor 6850e, 2Gb RAM, in a Dell Inspiron 400HD "Zino". People running x86_64 report no failures. In the bug report one of the developers speculates about a race condition, and it's very plausible that different hardware races differently, so some people always get killed, some never do, and some have intermittent failures. I never saw this problem before upgrading to OpenSuSE-13.1. What I would like the developers to do: Follow Fedora's lead, revert the "epoll freezable blocking call" commit, and send out a kernel update. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.