Hide Forgot
After upgrading the kernel to 2.6.38.3-18.fc15 suspending is always failing for this NVIDIA based laptop: http://www.smolts.org/client/show/pub_b3cccc26-d7e0-49b4-9b75-4c2e35942010 Downgrading to 2.6.38.2-9.fc15.x86_64 makes it work again
there are a few more reports of this .2 -> .3 resume breakage on different platforms, i googled "2.6.38.3 suspend resume". as of 2.6.38.5 it's not fixed for me, i'm proceeding to bisect it.
Just to be clear, in my case it is the suspend operation that is broken. When I close the lid or activate the suspend command the laptop never enter suspend, panel remains active with a movable, but useless, mouse pointer. The only way out is a power cycle.
bisect successful, mine is caused by acer-wmi: https://bugzilla.kernel.org/show_bug.cgi?id=34682
(In reply to comment #3) > bisect successful, mine is caused by acer-wmi: > https://bugzilla.kernel.org/show_bug.cgi?id=34682 Great job! Except, isn't your bug about resume? If I read comment 2 correctly, reporter of this bug never gets computer suspended in the first place.
Anyway, reporter, we could use some more information about the process of suspending. Please attach * your X server config file (/etc/X11/xorg.conf, if available), * X server log file (/var/log/Xorg.*.log) * output of the dmesg command after you try to suspend computer (and before reboot), and * system log (/var/log/messages) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Yes, my problem is about suspend, not resume. Also, this is a Toshiba so I'd think the acer-wmi is not the culprit for me. Anyway, I'm going to attach the additional data requested. Please note I'm not using any xorg.conf and it's likely I won't be able to get the dmesg after I try to suspend the computer. The behavior I see here is: * try to suspend (by closing the lid or from user menu -> suspend) * PC never enters sleep mode * I can move mouse cursor, but everything else is unresponsive, including switching to any TTY, so I can't grab the dmesg at this point.
Created attachment 499115 [details] /var/log/messages
Created attachment 499116 [details] Xorg.0.log
Created attachment 499118 [details] Xorg.1.log
Created attachment 499119 [details] Xorg.2.log
yep, mine is unrelated, did not notice the stage of the problem in the middle of all the searches and stuff at the time.
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