Bug 744253 - Shutting down and will not wake up
Summary: Shutting down and will not wake up
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: John Feeney
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-07 15:45 UTC by David Highley
Modified: 2013-01-10 07:41 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-16 02:55:17 UTC
Type: ---


Attachments (Terms of Use)
JPEG of BIOS screen showing version of BIOS (133.82 KB, image/jpeg)
2011-10-07 15:45 UTC, David Highley
no flags Details

Description David Highley 2011-10-07 15:45:36 UTC
Created attachment 526919 [details]
JPEG of BIOS screen showing version of BIOS

Description of problem:
After 30 minutes of system being idle is shuts off and will not wake up.

Version-Release number of selected component (if applicable):
Version with fedora 16 beta release, would provide version but system is not accessible as it is shutdown.

How reproducible:
Every time

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Will provide more details later, motherboard is Asus P8H67-I Deluxe REV 3.0 with the new uefi BIOS. Behavior is complete shutdown, fans and all. Hold power button and the fans will come back on but we are not able to get any video. This is a new computer and we ended up taking it back to the system shop as this failure can be confused with a motherboard not posting. This worked with the fedora 16 alpha version. So far the only way to recover is to pull the power plug and wait for a couple of minutes and then plug it back in and do a full power boot up cycle. If you plug the cord back in too quickly it will not come up.

Comment 1 David Highley 2011-10-07 15:56:22 UTC
More thoughts on this issue. While we support making changes, the power management aspects seem to be now buried deeply and so far we have not discovered how to control them. We should probable look into having this an install configuration decision much like disk layout as there probably is not one default that is safe and works for all situations.

Comment 2 Dave Jones 2011-10-07 17:26:44 UTC
I'm wondering if the 'shuts down while idle' part of this bug is thermal related.
(Not necessarily hardware, could be an acpi issue).  Please attach the output of acpidump (it's in the pmtools package).

Matthew ?

Comment 3 David Highley 2011-10-07 17:41:03 UTC
Do not think so as sensors shows no temperature issue and this system ran with the alpha version of Fedora 16. Note the beta version has a kernel update.

Comment 4 Matthew Garrett 2011-10-07 17:57:14 UTC
System is suspending due to the changed g-p-m defaults, and resume is failing. I believe that this default has now been changed again in g-p-m.

Comment 5 Josh Boyer 2011-10-07 17:58:12 UTC
Is the system sitting at a GDM login prompt with nobody logged in?  There was an issue reported recently where GDM would trigger a suspend after 30min of inactivity.

http://lists.fedoraproject.org/pipermail/devel/2011-October/157578.html

Comment 6 David Highley 2011-10-08 01:22:57 UTC
Well that seems to be the issue. Appears that the only fix is to run in init 3 level until a fix is available. We must say that Gnome has caused several platform issues in the last couple of years. Maybe some other platform should take the lead with this subsystem or we need to be more cautious about release there new updates. The referenced Gnome problem report indicates that is has been fixed, but there was no identification of when the update will be released or what identifying version to look for.

Comment 7 David Highley 2011-10-11 03:52:06 UTC
Found a work around. Add acpi=off to the grub.cfg boot line. System no longer shuts down.

Comment 8 David Highley 2011-10-16 02:54:52 UTC
Confirm fixed by update of gnome-settings-daemon-3.2.0-3.fc16.x86_64. Which was fixed in bug report: https://bugzilla.redhat.com/show_bug.cgi?id=742685


Note You need to log in before you can comment on or make changes to this bug.