Description of problem: see also bug 1811 Closing lid appears to do the Right Thing(tm); but will not resume when lid is opened. I have to cold reboot twice per day (at office in AM and home in PM) Platform: Dell Studio 1747, i7(8 CPU), 8G mem, 2*500G HD (sda=Win7; sdb=Mageia) Version-Release number of selected component (if applicable): Linux hg 2.6.38.7-tmb-laptop-1.mga #1 SMP Sun May 22 16:34:58 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux How reproducible: always Steps to Reproduce: 1. Close lid 2. Open lid. 3. Initially, Mageia installed vmlinuz-2.6.38.8-desktop-8.mga When I try to install laptop-mode-tools, the dependencies want to remove most of KDE packages (647MB!!) -- I DON'T THINK SO!!!! So I don't have laptop power controls. When I open the lid, the BIOS lights up the indicators and the CPU fan kicks in; but the OS never starts. Hitting the power button does nothing -- have to hold it for 4+ seconds and restart cold.
Created attachment 1068 [details] as requested in [similar] bug 1811
Created attachment 1069 [details] lspcidrake -v output
CC: (none) => pf
Last night, I opted to Sleep the system before closing the lid. When I re-opened it at home, it still would not restart, so I had to cold boot it. A few moments after logging in, the system suffered a fatal crash. Rebooted and all OK until this morning when I tried to Hibernate the system instead... This also did not work; required cold boot... [attachments coming next]
Created attachment 1074 [details] syslog spanning Sleep and Hibernate which fail.
Created attachment 1075 [details] photo of screen when system crashed after cold boot following un-sleep fail Original photo available on request... used Gimp to make dump easier to read. Could not find file with this content.
Summary: laptop will not resume => laptop will not resume [from lid close/open, sleep, or hibernate]
Attachment 1069 mime type: application/octet-stream => text/plain
Hi, thanks for reporting this bug. I guess it's for our kernel hacker :)
Keywords: (none) => TriagedAssignee: bugsquad => tmb
Created attachment 1076 [details] biosdecode output
Created attachment 1077 [details] dmidecode output Figured it might be useful to see the BIOS info... it was upgraded to the latest version (A14) before installing Mageia.
Hmmm... doing "dmidecode -t <N>" for all the available Ns, the following are suspicious...(?) System Reset Boot Option: Do Not Reboot Boot Option On Limit: Do Not Reboot
If this is a kernel issue, something puzzles me... I rebooted and before logging in, closed and re-opened the lid -- the system did NOT attempt to sleep (probably a different bug). My bug report only happens after logging in (KDE). Did not find any BIOS settings related to "Do not reboot" (comment 9). Found this thread: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/748994 -- sounds like this is a more widespread problem...
sigh... this problem is getting ridiculous!!! This morning, I decided not to close the lid and simply carry the laptop as-is into the office. When I got there, I plugging in the power adapter and mouse. The screen lit up and the session was locked -- don't know why as Require password is not set on screen saver. OK... just enter password... ARGH!!!!!!!! Upon hitting Enter, system went through SHUTDOWN!! When fully powered down, hit power button and it came up WITHOUT going through the BIOS screen and just sat there -- like it does when opening lid as previously reported. No choice but to hold power button until this mode shuts down and power up again into a COLD boot...
This weekend, after wondering if my swap partition was too small (8G v. 8G physical memory), I resized / & swap(20G), then completely re-installed Mageia. This morning, I issued Start->Leave->Hibernate and the system froze part way through shutdown and the fan kept running. So I just closed the lid and drove to the office where the fan was still running and the shutdown image was still on the screen when I opened the lid...
Created attachment 1093 [details] relevant part of /va/log/messages with comments
Created attachment 1094 [details] Photo of bottom of shutdown screen Stayed in this state through lid close, drive to office, open lid until forced power down.
This system has 2*500GB HDs (sda=Win7; sdb=Mageia). To be sure this is not a hardware problem, I booted into Win7 and performed some tests: 1. close lid, wait for fan to stop, wait a few seconds, open lid... OK 2. Start->Shutdown->Hibernate, wait for fan to stop, close lid, open lid. System stayed off, momentarily pressed power button, system resumed OK. Looks to me like hardware is operating as expected... (posting this comment from Win7/FF8)
Same problem here
CC: (none) => n54
But for Cauldron, I'm attaching lspcidrake -v output
Created attachment 1481 [details] dell studio 1555 lspcidrake output
*** Bug 5471 has been marked as a duplicate of this bug. ***
CC: (none) => dvgevers
I've been compiling my own kernel since 3.2.6 and this problem is not present under kernel releases since then. In fact, I can now even close the lid with VirtualBox running W7 and XP instances and all is well when I re-open the lid. Solved and working well with kernel 3.3.0 at this time. I was going to change this bug's status to RESOLVED; but there's no option LATEST S/W VERSION... It's still a problem with the Mageia 1; but can be marked resolved on Mageia 2...
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
see Comment 20 on this bug... After compiling my own kernel, this problem is fixed for me. Still running mga1; but now with kernel 3.4.4 and I'm happy.
(In reply to comment #22) > see Comment 20 on this bug... After compiling my own kernel, this problem is > fixed for me. Still running mga1; but now with kernel 3.4.4 and I'm happy. Thx Pierre @ Kamil @ Dick Do you still have this bug in Mageia 2 and/or current cauldron? This bug is filed against Mga 1 If so, please set version to highest, and put MGA1TOO (and if needed MGA2TOO) on the whiteboard
CC: (none) => marja11
My problems seems to be related to the proprietary ATI drivers
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