Created attachment 685415 [details] /var/log/messages file with the content described in Additional info Description of problem: Resume from suspend worked fine in Fedora 18 after the initial installation. After installing the regular Fedora 18 updates the Laptop Thinkpad T43 "resumes" only the hard disk. The suspend sign (moon) is still on and no CPU, Screen or FAN activity are seen. Suspend has to be stopped by long hitting the POWER buttom and re-booting. Version-Release number of selected component (if applicable): Fedora18 most recent regular fixpack as of Jan, 23th. How reproducible: Happens with every try to Resume from suspend. Steps to Reproduce: 1. Close Laptop (suspend) 2. Suspended ok. 3. Open Laptop (try to resume) Actual results: Doesn't resume from suspend successfully Expected results: Resume from suspend Additional info: Attaching the /var/log/messages file It contains the following - see timestamps.... 20:05 Initial Boot 20:07 Check for Updates 20:08 Suspend - OK (but error msg in log!) 20:10 Try to Resume (Cover opened) ..... doesn't work 20:12 Power off (long hitting the POWER buttom) 20:14 Restart
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 18 kernel bugs. Fedora 18 has now been rebased to 3.11.4-101.fc18. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 19, and are still experiencing this issue, please change the version to Fedora 19. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. It has been over a month since we asked you to test the 3.11 kernel updates and let us know if your issue has been resolved or is still a problem. When this happened, the bug was set to needinfo. Because the needinfo is still set, we assume either this is no longer a problem, or you cannot provide additional information to help us resolve the issue. As a result we are closing with insufficient data. If this is still a problem, we apologize, feel free to reopen the bug and provide more information so that we can work towards a resolution If you experience different issues, please open a new bug report for those.
Moved to CentOs 6.5 which solved the issue. Thanks!