Bug 581898 - Regression: 2.6.32 fails to resume from display standby. Not a problem with 2.6.31
Summary: Regression: 2.6.32 fails to resume from display standby. Not a problem with 2...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 13
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-13 14:43 UTC by lexual
Modified: 2011-06-07 05:49 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-06-07 05:49:29 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Xorg.log (197.66 KB, text/plain)
2010-04-13 14:44 UTC, lexual
no flags Details
dmesg (39.07 KB, text/plain)
2010-04-13 14:45 UTC, lexual
no flags Details

Description lexual 2010-04-13 14:43:13 UTC
2.6.32 kernel.
Either wait for system to timeout and blank monitor display or run something like:
xset dpms force suspend

With 2.6.32, the monitor goes blank and displays the error:

Out of Range.
H.Frequency 33 KHz
V.Frequency 31 Hz

Intel 965G Chipset
ViewSonic vg2030wm monitor.

Problem doesn't occur with 2.6.31.

Comment 1 lexual 2010-04-13 14:44:30 UTC
Created attachment 406265 [details]
Xorg.log

some info on graphics setup.
Am running without xorg.conf (this has worked fine until now)

Comment 2 lexual 2010-04-13 14:45:07 UTC
Created attachment 406266 [details]
dmesg

Comment 3 lexual 2010-04-13 14:46:42 UTC
Forgot to mention that when error message comes up on blank screen (this is monitor message not from OS), I can't switch to virtual terminal (ctrl+alt+f2, etc) and need to reboot system.

Comment 4 lexual 2010-05-01 11:06:17 UTC
This bug affects latest f13.

I am forced to turn of monitor power saving, or else I have to manually (press the reboot button) reboot anytime the system tries to put monitor to sleep!!

2.6.33

Comment 5 Bug Zapper 2011-06-02 15:26:12 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13'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 13 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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 6 lexual 2011-06-07 05:49:29 UTC
Seems to be have fixed in recent versions.


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