The system hung after sorting from a suspend mode. Hibernate works. try to find answer on the web and I found that Ubunutu and Fedora users where having the same problem. One user give the script above that works for me : #!/bin/sh # Workaround for concurrency bug in xserver-xorg-video-intel 2:2.4.1-1ubuntu10. # Save this as /etc/pm/sleep.d/00CPU . "${PM_FUNCTIONS}" case "$1" in hibernate|suspend) echo "Going to use a single Core..." for i in /sys/devices/system/cpu/cpu*/online ; do echo 0 >$i done ;; thaw|resume) # sleep 10 # run with one core for 10 secs # echo "Switching back to SMP..." # for i in /sys/devices/system/cpu/cpu*/online ; do # echo 1 >$i # done ;; *) ;; esac If it could be integrated into the main suspend function...
@ Christophe Sorry for responding so late, we are very short on triagers Do you still have the â/var/log/pm-suspend.log part of when this happened? If so, could you please attach it. And the output of lspcidrake -v too please and the dmesg-withpatch.txt that results from dmesg > /tmp/dmesg-withpatch.txt According to our triage guide, I should ask you a lot more, but since you got the bug solved, the rest of the questions seem useless now.
Keywords: (none) => PATCHCC: (none) => marja11, thierry.vignaud, tmbSource RPM: (none) => pm-utils
Forgot to add the UPSTREAM keyword Did you report upstream, Christophe, or if you know someone else did, could you please give the link to the bug report? If you didn't, could you please report here: https://bugs.freedesktop.org/enter_bug.cgi and choose the pm-utils product Thanks a lot.
Keywords: (none) => UPSTREAM
Created attachment 990 [details] lspcidrake -v
Created attachment 991 [details] dmesg > /tmp/dmesg-withpatch.txt
Do you still have the â/var/log/pm-suspend.log part -> no lspcidrake -v -> in attach file /tmp/dmesg-withpatch.txt -> in attach file Did you report upstream, Christophe, or if you know someone else did, could you please give the link to the bug report? -> no. I have not find a similar bug but I find the solution for my problem so I ve post the solution
I have the same problem with the netbook MSI U110 I changed the action when the screen is closed from suspend to turn off the screen because after opening the screen cap i could nt use the netbook, it does nt want to wake up. I did nt try the above script, i use vesa driver
CC: (none) => dglent
Summary: Unable to resume from suspend on Lenovo Thinkpad T410 Laptop => Unable to resume from suspend on Lenovo Thinkpad T410 Laptop and netbook MSI U110
@ pterjan I saw your name in the changelogs of pm-utils and laptop-mode-tools, therefore cc'ing you
CC: (none) => pterjan
(In reply to comment #7) > @ pterjan > > I saw your name in the changelogs of pm-utils and laptop-mode-tools, therefore > cc'ing you And because of what Ahmad said in the changelog of pm-utils: Wed May 18 2011 ahmad <ahmad> 1.4.1-3.mga1 + Revision: 99676 - Conflict with laptop-mode-tools, its functionalities overlap pm-utils, and upstream thinks it should conflict http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612710#59 I do not know whether or not this resume bug can have anything to do with that conflict
We still don't have a maintainer for pm-utils
I tried the above script but it did nt work in my netbook.
(In reply to comment #10) > I tried the above script but it did nt work in my netbook. In that case, there are two different issues: Christophe's one that can be fixed with that script, and yours, that can't You might want to file a seperate bug report for your issue. Please look here to see which files to attach to the new report: https://wiki.mageia.org/en/Triage_guide#Suspend.2FHibernate_issues
ok: https://bugs.mageia.org/show_bug.cgi?id=4019
@ Dimitrios Thx :)
Summary: Unable to resume from suspend on Lenovo Thinkpad T410 Laptop and netbook MSI U110 => Unable to resume from suspend on Lenovo Thinkpad T410 Laptop
3 months later, still no maintainer for pm-utils
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. 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 Mageia version prior to Mageia 1'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 Mageia 1 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 Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. 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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => WONTFIX