Bug 769447

Summary: After inactivity, Gnome blanks the screen and crashes my machine.
Product: [Fedora] Fedora Reporter: Joseph Perrin <jap>
Component: upowerAssignee: Richard Hughes <hughsient>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 16CC: hughsient
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 14:38:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Joseph Perrin 2011-12-20 21:15:43 UTC
Description of problem:

As long as I'm actively using my machine, all is well, but after the screen blanks, my system crashes.  Nothing works, (i.e. Caps Lock), fans still run, I can't ping it.  Remote ssh sessions to it get dropped.  (Yup, it's gone!)  The only recourse is to reset.   I'm assuming it's gnome, maybe UPower??, but I can't tell exactly.  Nothing in the logs that I can see!  I wish I could give more complete information, but there's a lack of good documentation on this topic.  :-(


Version-Release number of selected component (if applicable):
gnome-power-manager: 3.2.1
upower: 0.9.15
acpi: 1.5

How reproducible:
Wait for screen to blank.


Steps to Reproduce:
1. Go get coffee
2. 
3. 
  
Actual results:
System Crash.

Expected results:
A functioning computer and the unlock screen.

Additional info:

Intel D865GVHZ Motherboard.

processor	: 0
vendor_id	: GenuineIntel
cpu family	: 15
model		: 2
model name	: Intel(R) Pentium(R) 4 CPU 2.40GHz
stepping	: 9
cpu MHz		: 2399.940
cache size	: 512 KB
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 2
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe up pebs bts cid xtpr
bogomips	: 4788.78
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 32 bits virtual
power management:

Some dmesg snippets:
:
[    0.019394] ACPI: Core revision 20110623
[    0.022609] ftrace: allocating 22221 entries in 44 pages
[    0.023092] Enabling APIC mode:  Flat.  Using 1 I/O APICs
[    0.023386] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    0.033668] CPU0: Intel(R) Pentium(R) 4 CPU 2.40GHz stepping 09
[    0.033997] Performance Events: Netburst events, Netburst P4/Xeon PMU driver.
:
:
[    0.040780] ACPI: Added _OSI(Module Device)
[    0.040785] ACPI: Added _OSI(Processor Device)
[    0.040789] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.040794] ACPI: Added _OSI(Processor Aggregator Device)
[    0.041755] ACPI: EC: Look up EC in DSDT
[    0.042935] ACPI: Executed 3 blocks of module-level executable AML code
[    0.045721] ACPI: Interpreter enabled
[    0.045734] ACPI: (supports S0 S1 S3 S4 S5)
[    0.045766] ACPI: Using IOAPIC for interrupt routing
[    0.050089] ACPI: Power Resource [URP1] (off)
[    0.050148] ACPI: Power Resource [FDDP] (off)
[    0.050210] ACPI: Power Resource [LPTP] (off)
[    0.052476] ACPI: No dock devices found.
:
:
[    0.054759] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[    0.054846] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P3._PRT]
[    0.055089]  pci0000:00: Unable to request _OSC control (_OSC support mask: 0x1e)
[    0.058190] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
[    0.058283] ACPI: PCI Interrupt Link [LNKB] (IRQs *3 4 5 6 7 9 10 11 12 14 15)
[    0.058376] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
[    0.058468] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
[    0.058558] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
[    0.058651] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
[    0.058742] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
[    0.058839] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
:
:
[    0.758870] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[    0.758873] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[    0.759356] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input0
[    0.759366] ACPI: Sleep Button [SLPB]
[    0.759429] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
[    0.759435] ACPI: Power Button [PWRF]
[    0.759555] ACPI: acpi_idle registered with cpuidle
[    0.761534] ERST: Table is not found!
[    0.761538] GHES: HEST is not enabled!


Some suspicions:

My /home directory is a lvm mounted fs, which was previously running under F10/GNOME.  I question if there's some bad cruft in a dot library that could be the cause.

Comment 1 Joseph Perrin 2011-12-21 01:59:25 UTC
Here are the results to some additional sanity checks:

Runlevel 3:

Leaving it in text mode: No problems, screen blanks, any key restores the display.

Running X from shell, (i.e. startx) (To Gnome): No problem.


Runlevel 5:

Leaving it on the GDM Greeter: No problem.

Login using KDE: No problem.

Login using Gnome: PUKES!

Login using Gnome & Logoff to Greeter: No problem.

I'm now getting a whiff of rotting F9/10 gnome config files in my home directory.  Going to try creating a new account, and see if that makes any difference.

Comment 2 Joseph Perrin 2011-12-21 02:32:37 UTC
Ok...  I created a new login account, (& obviously new home directory), logged in, (set screensaver to 1min), after screensaver...  I noticed the UPS load dropped down two points.   Then the system Crashed.  :-(  

So, it would not appear to be my home directory configuration.  It therefore must be what gnome does that's incompatible with my system architecture.

Of side note:  After these many crashes, there have been several instances of file system corruption.  (i.e. Beyond the normally expected simple journal rollbacks.)    

I'll be happy to help in any way, but I need to figure out a way to just whack power management, so I can walk away from my desk without fear of loss.  I guess using KDE will work...

Comment 3 Fedora End Of Life 2013-01-16 13:45:22 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

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 Fedora version prior to Fedora 16'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 Fedora 16 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 Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

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 Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Fedora End Of Life 2013-02-13 14:38:33 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.