Some news after nearly 2h of tests… - latest 2.6.27-7 produces the same crash/freeze on resume (x cursor stuck, no sysrq). Sometimes the unlock dialog can appear before the freeze (but only the frame, not the input field, the photo, the user name…), sometimes only the X cursor. - freeze happens on 100% of suspend/resume tries for me, when using any of Intrepid's 2.6.27-* kernels (tried -3, -5, -6, -7) - trying the 2.6.26-rt from universe, the suspend resume cycle works perfectly, modulo the following workaround-able problem : - first suspend/resume brought me to a strange situation : the computer resumed correctly, but screensaver corrupted the screen (moving the mouse makes screen flicker, doesn't stop screensaver, doesn't bring unlock dialog). - pressing control-alt-f1 to get to console gets me to a black screen (backlight is on, but nothing displayed, not event a cursor). I can [blindly] enter my username and my password, then "killall gnome- screensaver" (with the space). returning to X shows the cursor still making the screen blink/flicker (seems normal). - logging in from SSH and killing gnome-screensaver makes the X screen come back to normal, and computer is fully usable (at least visually : external USB mouse ok, network manager wired OK, wifi OK, webcam ok with Cheese, gnome-power-manager OK, compiz OK…). - I disable screensaver (uncheck "activate screensaver when idle"), try another suspend/resume cycle. - on resume, I get a black screen, but my caps lock works and X seems OK (because I inverted control and caps lock, and the control-key puts the caps led on and off) - going to console strangely gets me a working console (in which i logged in a few minutes ago to kill "gnome- screensaver" and notice my previous typo). - pressing control-alt-f7 brings me back to X, fully working. - suspending/resuming again (i really enjoy this functionnality when it works…) works flawlessly.
So, my conclusions : - suspend/resume totally crashes my kernel with any of the 2.6.27-* Intrepid kernels. - suspend/resume works correctly with 2.6.26-rt from Intrepid's universe, and I sometimes hit another bug related to Intel GMA/video BIOS/fb problem, which forces me, on resume, to go back to console and back to X, to get X displayed on screen. I know there are some X/Intel/uvesafb problems already reported, i'm subscribed to most, but I can't seem to find which one is the one I encounter ; hope they will all be resolved before release). Now, I will stick to 2.6.26-rt kernel, because suspend/resume works perfectly, and all my devices seem ok. I know this is a bad decision because 2.6.26 is not in main, not the official intrepid kernel… But my kernel/debbuging skills are not enough to find what's wrong in the resume cycle of the 2.6.27. I will be happy to help if someone can guide me. I can even provide an ssh access to a kernel hacker if needed. By the way, I can't confirm with 100% of certainty that my bug is the same as Jason's. But it seems. Any other point of view on this issue ? regards, Olivier -- DRM Breaks Resume from Suspend https://bugs.launchpad.net/bugs/274278 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
