Description of problem: Up until recently, my Cauldron based laptop would sleep and wake up fine when I closed the lid and later reopened it. Now, since recent Cauldron updates (I suspect the new kernel) - when I close the lid - the sleep symbol blinks once a second and never stops - when I open the lid -the power button is blinking, screen is blank - and I can not re-awake the machine. I have to hold the power button down for 10 seconds and hard reset the laptop. Version-Release number of selected component (if applicable): How reproducible: Everytime Steps to Reproduce: 1. Close laptop lid 2. wait 30 seconds - see flashing sleep LED 3. Open lid and see power button flash every second - blank screen 4. Have to hard reset / reboot to get machine back Reproducible: Steps to Reproduce:
Update - when I manually click on suspend to RAM it works - by "lid close" it doesn't
Update - I spoke too soon - When I manually "Suspend to Ram" is also fails as described above - so it is NOT just lid close related!!
The observed "crash" with the blinking power light and dead screen looks similar to when there is segfault of the kernel - but the screen in blank when it happens - so I need to check the logs but not sure where to check . . . I will also try a different DM (than KDE) to se if the problem is DM independent
I can confirm this problem occurs with other DMs (GNNOME, etc.) - so it is not DM specific!! Must be kernel and power management on a lower level . . . this has occured since the most recent kernel updates (3.18) - before I had no issues
Did you wait over 90 sec when that slow flashing occured? I have the same problem with hibernate on a Panasonic Toughbook S10. When I try to hibernate (eg run pm-hibernate) the system will go black, the disk light will flash about 1 per second for almost 2 min, and finally it will hibernate. So if you wait for 2-3 min, does it finally go to sleep? (See bug report 14676 for my report of this problem already in 4.1 and it seems like it is not fixed in Cauldron) And it happens whether I run pm-hibernate directly or I push the hibernate button in KDE.
CC: (none) => unruh
I did not wait that long - mostly because it was working before (very fast sleep and wake up because I have a SSD) - and to be totally honest - waiting 2-3 minutes is not a long term solution!
I certainly agree that it is not a long term solution either for sleep or hibernate. For hibernation I was advised to just do a poweroff, since it is fast. On my system it is not. I get a "a stop job..." message on poweroff or reboot very often, which then has a 90 sec timeout, so that is just as slow as hibernate. I guess, the only long term solution is never to turn your laptop off:-) Anyway, could you try waiting 3 min to see if it is just a long timeout or if the shutdown really hangs (which would make it different from mine, and might help the developers narrow down where the problem is, since sleep does not copy everything to disk, and that disk light pulsing once a second is not the system trying to copy all the web pages to disk. )
I just tried on my system to have the system go to sleep when the lid is closed. It does goto sleep (as indicated by the slow flash of the on-off button-- I cannot see the disk button with the lid closed) in about 6 sec, and wakes up before I have lifted the lid far enough to see the screen. Similarly if I run pm-suspend either as user or as root, it goes to sleep in about 6-10 sec. while hibernate takes minutes. So while my system has a hibernate problem which seems similar to his sleep problem, my MGA4.1 does not have his sleep problem.
Any better luck nowadays? I have similar problems: bug 14392
CC: (none) => fri
I can confirm this problem still exists - since I have reported it, the RAM sleep function is highly unreliable - sometimes t works, sometimes the system freezes beyond usage and requires a hard reboot
CC: (none) => thomas.bigot
I meet the same issue :Â when launching s2ram or just pressing my keyboard sleep button as usual, the machine seems to process suspending, session is been locked, screen goes to standby, the HDDs stop, but the power light stays lighten. No way to wake it, the only solution is to reset the machine. Reproductible: always. Reverting to an older kernel (eg 3.17.4-desktop-1.mga5) makes suspend work fine back. Success reproducible: always. Graphic card: AMD RV730 PRO Motherboard: ICH7 Family Iâm using mdadm for a Raid-5 If I can test diagnosis commands, please ask! Thansk.
CC: (none) => tmb
New update - once again - Using Thinkpad X220 and KDE - latest Cauldron updates as of today. When I perform a "pm-suspend" manually from a console - the machine sleeps fine and wakes up fine (can do it is several times in a row) If I leave the machine idle (lid open) - after a timeout period the machine tries to sleep by itself (like lid close action) and the same issue appears as described in the first post - the system crashes hard and can only be recovered by hard shutdown and restart!! This ia a major problem moving forward . . .
I have been lucky; suspend to RAM always have been working on my Thinkpads R60 & T61 since spring/summer. Hibernate to disk however never works, but breaks different ways between updates. Earlier i have tried some suggestions at the thinkpad forum but they did not work then, and I admit I got tired and am just watching a couple bugs here. If someone can tell how to make a detailed log of the hibernating process it would probably help (it is not saved when it hangs... so probably it need to spit it out at fast rate over network or serial port, or be made to save and sync to disk very frequently...)
I think this has something to do with how KDE calls the sleep mode (and I amsuspecting it doesn't call pm-suspend - which works when manually started in a console!)
Instead of using the pm- utilities try systemctl hibernate On my system the pm utilities for hibernation were a disaster-- it would hibernate but it would take over 2 min to do so-- the disk light would flash once per second suggesting that the writing to swap was taking place at an incredibly slow rate. However using systemctl hibernate, it now takes at most 20 aec to hibernate. Yes, the absence of any debugging for hibernation is a real pain.
This still exists in M5b2 - after fresh install - definitely related to KDE suspend method with lid-close - as mentioned earlier, pm-suspend works fine in a console!
Iâm not using a Thinkpad, but the only way for me to have suspend works without blocking my PC is to use a 2.17.x kernel. Even the latest kernel (and a up to date system yesterday evening) does not suspend properly the system. Even if I type pm-suspend in a terminal using IceWM, it gets stuck with the power light and no way to resume the system.
Worth an Errata entry I suppose. Could you provide a proposition of text in a comment below?
Whiteboard: (none) => FOR_ERRATA
I have since turned off the KDE feature "suspend on lid close" and now use the "Leave" or "Logout" from the Panel and then chose "Suspend to Ram" under "turn off computer" - Not sure is this affects other devices, or whether this problem is fixed with the latest Cauldron - therefore not confident an "Eratta" entry would be helpful here . . .
Whiteboard: FOR_ERRATA => MGA5TOO FOR_ERRATA
(In reply to Robert Fox from comment #19) > I have since turned off the KDE feature "suspend on lid close" and now use > the "Leave" or "Logout" from the Panel and then chose "Suspend to Ram" under > "turn off computer" - Not sure is this affects other devices, or whether > this problem is fixed with the latest Cauldron - therefore not confident an > "Eratta" entry would be helpful here . . . Removing "FOR_ERRATA" then.
CC: (none) => shlomifWhiteboard: MGA5TOO FOR_ERRATA => MGA5TOO
Appears to be fixed in latest cauldron
Status: NEW => RESOLVEDResolution: (none) => FIXED