Description of problem: System freezes when monitor put on standby. Version-Release number of selected component (if applicable): kernel-3.2.3-2.fc16.i686 How reproducible: always Steps to Reproduce: 1. Lock screen 2. Wait for it to turn off (configurable time) 3. Actual results: System freezes. No crash. No Kdump possible. No network. Much worse than a screen of death. Expected results: Monitor goes to sleep and system keeps operating. Additional info: Reported in bug#730853 as an Intel driver problem. However, the workaround in suggested in that bug on comment#6 stopped working with kernel-3.2.3-2. I confirmed that the workaround is still effective in kernel-3.2.2-1. Since changing only which kernel is booted makes the problem manifest or not, I concluded that kernel modeset is the culprit, not the Intel graphics driver.
kernel-3.2.5-3 is broken also.
I see my conclusion was overruled. Why does rebooting with a different kernel change the behaviour? I found a new workaround for the new kernels. In addition to the idle-delay workaround referenced above, set "Lock screen after" to "Screen turns off" in System Display settings. I have no idea why this makes a difference.
The workaround in comment#2 does not work for a 2 cpu system! It only works for single cpu systems. This should give a clue - timing issue? My 2 cpu system is still unusable with current kernels. I'll see if I can disable a CPU in bios and see if that makes the workaround viable.
I found a (sort of) workaround that is viable on 2 cpu systems: after locking your screen, switch to a text console. The text console does not freeze the system when putting monitor on standby. Hey - at least I can go out to the store without shutting down my computer.
ARrrrgggh! I went on a lunch date and forgot to switch to a text console...
Good news! kernel-3.2.6 once again works with the idle_delay=0 workaround. I haven't yet tested whether it works without idle_delay=0. But at least the system is usable again!
kernel-3.2.6 only works if you manually invoke "Lock Screen". Letting the screensaver lock the screen still freezes the system. Oh well - that will teach me to lock my screen when I step out...
I've ordered an ATI radeon 7000 very cheap. Open source driver was working in 2010, hopefully still works in F16.
So I leave my workstation on a text console when I leave for work, so it doesn't freeze (ATI card hasn't arrived yet). I connect via vnc, screen is blank (normal), and I remember I had to switch to text console. So I disconnect. System freezes (or crashes - I'll check when I get home). Another clue?
Seems to have frozen. I put in the radeon7000, and gnome-shell still doesn't work, but system no longer freezes on power save.
A patch is out for bug#730853 which should be applied to F16 as well. Hopefully this is fixed.
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
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.