Created attachment 490858 [details] dmesg post hang Filing this because "suspend" is the default in gnome-shell, and I once again got trapped into pressing it : The kernel resumes properly, I get to the "enter password" dialogue and that works, but once the password has been entered, graphics fall apart, get overlaid and garbled and input stops working. Mouse no longer functions, and the keyboard takes ~10 seconds to respond to num-lock presses before toggling the led. Toggling to a terminal (ctrl alt f2) works after a while (also ~10 seconds) then lets me get a dmesg log and shut the system down somewhat cleanly. I'm well aware that this is a tainted kernel, but I'm also of the opinion that if you want to provoke kernel bugs by making suspend default in gnome-shell as a policy, you should also work to remove these bugs. My solution would be to make suspend _not_ be default on tainted kernels, but since you're just getting told "try a broken driver" when asking on IRC...... [root@Waves ~]# uname -a Linux Waves.darkmere 2.6.38.2-9.fc15.x86_64 #1 SMP Wed Mar 30 16:55:57 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux NVRM version: NVIDIA UNIX x86_64 Kernel Module 270.30 Fri Feb 25 14:34:55 PST 2011 GCC version: gcc version 4.6.0 20110331 (Red Hat 4.6.0-2) (GCC) Tail of xorg.0.log.old [ 29938.835] (II) NVIDIA(0): Setting mode [ 29938.835] (II) NVIDIA(0): "DFP-0:nvidia-auto-select+1920+0,DFP-1:nvidia-auto-select+0+0" [ 29938.906] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon [ 29938.906] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X [ 29938.907] (II) NVIDIA(0): configuration option may not be set correctly. When the [ 29938.907] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will [ 29938.907] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For [ 29938.907] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and [ 29938.907] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X [ 29938.907] (II) NVIDIA(0): Config Options in the README. [ 43759.354] (II) NVIDIA(0): Setting mode [ 43759.354] (II) NVIDIA(0): "DFP-0:nvidia-auto-select+1920+0,DFP-1:nvidia-auto-select+0+0" [ 43759.438] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon [ 43759.438] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X [ 43759.438] (II) NVIDIA(0): configuration option may not be set correctly. When the [ 43759.438] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will [ 43759.438] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For [ 43759.438] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and [ 43759.438] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X [ 43759.438] (II) NVIDIA(0): Config Options in the README. [ 43790.329] (II) AT Translated Set 2 keyboard: Close [ 43790.329] (II) UnloadModule: "evdev" [ 43790.329] (II) Unloading evdev [ 43790.329] (II) Logitech USB Receiver: Close [ 43790.329] (II) UnloadModule: "evdev" [ 43790.329] (II) Unloading evdev [ 43790.329] (II) Power Button: Close [ 43790.329] (II) UnloadModule: "evdev" [ 43790.329] (II) Unloading evdev [ 43790.329] (II) Power Button: Close [ 43790.329] (II) UnloadModule: "evdev" [ 43790.329] (II) Unloading evdev
Created attachment 490869 [details] dmesg with nouveau Retrying this without nvidia drivers but with nouveau drivers instead causes other (bad) behaviour. dmesg attached. Note that at this time for some reason it auto-resumed as soon as it shut off, but I'm not sure that's me touching keyboard/mouse or something else.
(In reply to comment #0) > I'm well aware that this is a tainted kernel, but I'm also of the opinion that > if you want to provoke kernel bugs by making suspend default in gnome-shell as > a policy, you should also work to remove these bugs. My solution would be to > make suspend _not_ be default on tainted kernels, but since you're just getting > told "try a broken driver" when asking on IRC...... OK, so you are very right that if you come to us with nvidia binary-only kernel we would close this bug as CANTFIX (because that's the situation, we really cannot fix it). So, switching this to the gnome-shell copmonent as RFE for not allowing suspend when it is not expected to work. And of course, this is (if I understand your request correctly) just a discussion about defaults), you can change the action caused by pressing any key in Control Center / Power-Batter settings. For the rest of your issue, I have cloned this bug into bug 694917. Please continue there.
Yes, You understood my request correctly. I'll make sure to follow up properly in the other bug#.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping