Created attachment 381235 [details] lshal output for t400 Description of problem: When resuming from hibernation the t400 will go into a dormant state and exhibit a black screen. Version-Release number of selected component (if applicable):F12 pm-utils. How reproducible: Consistently after the 2nd or third resume from hibernate. I can resume from hibernate once or twice with no noticeable reduction in functionality or error messages in any of the logs. When the malfunction occurs I can sometimes access a tty with ctrl+alt+F[2-8], the actual 'F' key varies, otherwise I have to hard reboot. After the hard reboot the system has required remedies as sever as yum reinstalling all the software or as simple as restoring the journalled state. I have tried some suggested fixes found in other similar bugs with differing results but no success in reliable resume functionality. The first attachment is the the output from lshal.
Created attachment 381236 [details] pm-suspend error log output
Created attachment 381237 [details] message log error output
Created attachment 381238 [details] Xorg log error output
I then tried a suggested fix from another bug report which was to disable and remove the cpu_freq module prior to hibernate via a script in /etc/pm/sleep.d/. This was in effective though the logs indicated the module was removed and successfully reinstalled after the first resume from hibernate, but, on the second attempt I still encountered a frozen system.
I then looked more closely at the error output in pm-suspend.log which pointed to ' /usr/lib64/pm-utils/sleep.d/98smart-kernel-video: line 37: add_parameter: command not found '. That line in the pm script suggested adding the option --quirk-no-chvt to the pm-hibernate command line. I did this and I was able to resume 4 times in a row from hibernate without hanging, but, I had a somewhat crippled system. The symptoms being that all service level daemons were non or semi functional. I could start programs like emacs, firefox, gedit and soforth but I had no network, NetworkManager was in an undetermined state. CPUspeed was stuck at 2.27 MHz. I could logout but I could not shutdown or restart the computer with the GDM greeter menu nor when I accessed a tty. I again had to hard reboot. The attached pm-suspend log captures and catalogues the relevant errors.
Created attachment 381240 [details] pm-suspend log errors after resumes with semi functional system state.
Even though the system was semi functional I could still enter hibernation at the terminal command line repeatedly as long as I did not try to log out or enter a tty. #pm-hibernate --quirk-no-chvt Adding the option to the hibernate command changed the symptoms but not the end result. Please suggest a means to help me further debug this condition.
Is there any update as to the status of this bug? I am sure it is only an issue for 64 bit users. Those who are still using the 32 bit kernel do not experience this issue.
After the latest kernel update to version 11-99.fc12.x86_64, I have been able to resume from hibernate without any problems. I have resumed from hibernate 3 times in a row, once while charging and twice after unplugging. I have yet to reboot. There are no segfaults in the logs or errors related to the resumes. I will have to see how things go in the next few days, but right now internet is working without delay and there is no sign of the prior reported symptoms.
Still good after 5 consecutive resumes from hibernate.
Well the next update broke what was fixed. See attachments for errors. System will boot but mount segfaults, Apps won't start. Some things did work. Wireless started after re-enabling networking, it resumed disabled.
Created attachment 406404 [details] Latest yum update I'm betting on libdrm being the culprit.
Created attachment 406405 [details] message log error output A long list of kernel protection faults.
OK, a day later and I do not think it is libdrm. I downgraded to an earlier version and it had no effect. The common thread through all my prior issues has been the fact that the power/charger has been plugged in. The last bought of system instability and segfaults occurred during the period when I was recharging and the power was plugged in continuously. If the power is unplugged during a session that I have not previously resumed from hibernate there is a 50 50 chance that I will experience subsequent segfaults. The 5 consecutive successful resumes followed a session that the power supply was unplugged prior to the first hibernate. So is this a power management issue, a dbus issue. Is there any common thread in the error output I have provided?
Could someone please check if this bug is related to: https://bugzilla.redhat.com/show_bug.cgi?id=537576 and also https://bugs.launchpad.net/oem-priority/+bug/532374 According the the second bug linked there is a pending bios update from Lenovo to address this issue. Also, with later kernel builds a work-around is to use this kernel command-line option: acpi_sleep=sci_force_enable But this only works on later kernel builds, I think 2.6.33 & up. The kernel option worked for me on the kernel included with Fedora 13 beta. uname -a Linux fmi2727.fic.ffg 2.6.33.1-24.fc13.x86_64 #1 SMP Tue Mar 30 18:21:22 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
The bug on launch pad net is not the same symptoms. I can suspend and resume at will. I only have problems with resuming from hibernate and it is not predictable, as I have described in post 11 & 12. There seems to be a connection to the power / charger being plugged in but I can't even duplicate the exact symptoms deliberately. I continue to collect error output,but it differs from event to event so widely that I can't find a common thread.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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
This bug has been less of an issue over time on F12 for me. I can't say that it has been solved, just that I rarely hibernate more that once in a row between shut downs. I have installed F14 on a separate partition but the tpm bug prevents suspends and hibernates on thinkpads at the moment. Waiting for the upstream kernel to appear. Oh, bug #537576 should be terminated. Jim KR
From previous comments it looks like three or more issues. The pm-utils typo (s/add_parameter/add_parameters/), that was fixed some time ago. The issue with NetworkManager, it should be also fixed now. The other errors seems as not pm-utils fault (maybe kernel problem?). If you encounter this on newer version of Fedora feel free to reopen.
I have had F14 running for 5 days now and after the update to kernel 6-48 on the x86_64 machine (Lenovo T400) with intel graphics I have hibernated several times in a row without any symptoms of this bug.