Created attachment 442573 [details] lspci -nn from my computer Description of problem: After updating from kernel-2.6.33.8-149.fc13.x86_64 to kernel-2.6.34.6-47.fc13.x86_64 I'm no longer able to use stand-by function for monitor. My computer freeze after monitor in stand-by mode. No way to ping the computer. There is no problem with screensaver function. I've tried with catalyst 10.7 and 10.8 same problem but works fine with kernel 2.6.33.8-149.fc13.x86_64. I don't use hibernate or stand-by mode for computer and/or hard disk drive, only for screen. Version-Release number of selected component (if applicable): kernel-2.6.34.6-47.fc13.x86_64 xorg-x11-drv-catalyst-10.8-1.fc13.x86_64 akmod-catalyst-10.8-1.fc13.x86_64 kmod-catalyst-2.6.34.6-47.fc13.x86_64-10.8-1.fc13.x86_64 xorg-x11-drv-catalyst-libs-10.8-1.fc13.x86_64 How reproducible: Update kernel and use stand-by mode for screen. Wait for screen in stand-by mode. Nothing append after moving mouse or pressing key from keyboard. Steps to Reproduce: 1. 2. 3. Actual results: The computer blocks after screen goes in a stand-by mode. Keyboard not responding. Only action on reset button can reboot the computer. Expected results: Screen go in stand-by mode and after action on keyboard or mouse screen and computer works fine. Additional info: Actually I have to set stand-by mode for screen to "never". Nothing special in /var/log/messages and /var/log/Xorg.0.log
I'm experiencing the same effect while trying to suspend to ram my laptop (DELL E4300). I'm not able to say if it's related to video going stand-by or to some other suspend task but the effect is the same: black screen and keyboard unusable. Apparently I cannot find any log line explaining this behaviour. I then reverted to kernel-2.6.33.8-149.fc13.x86_64 and everything went ok.
(In reply to comment #2) > > Version-Release number of selected component (if applicable): > kernel-2.6.34.6-47.fc13.x86_64 > > xorg-x11-drv-catalyst-10.8-1.fc13.x86_64 > akmod-catalyst-10.8-1.fc13.x86_64 > kmod-catalyst-2.6.34.6-47.fc13.x86_64-10.8-1.fc13.x86_64 > xorg-x11-drv-catalyst-libs-10.8-1.fc13.x86_64 > Does it happen with xorg-x11-drv-ati as well?
I just tried with xorg-x11-drv-ati-6.13.0-1.fc13.x86_64 (radeon driver) and with kernel-2.6.34.6-47.fc13.x86_64 no problem with stand-by mode for monitor. However the screen is a little bit vague, it is unpleasant and there is a purple horizontal line to the left of the screen, no 3D support for moment so that's why I use Catalyst driver, but it's an other bug and no link with this kernel.
Today I tried some tests and I'm really amazed because stand-by mode for monitor works fine now. After tests with radeon driver and back with fglrx (Catalyst 10.8) I saw that radeon was always loaded with lsmod command and in spite of rdblacklist=radeon in my grub.conf. So I decided to blacklist radeon in /etc/modprobe.d/blacklist.conf, and this time no module radeon loaded, but problem still present. The only thing I've done after was to set parameters by default in ATI Catalyst Control Center, but I can't exactly remember my previous parameters. In /boot/grub/grub.conf I use radeon.modeset=0 and rdblacklist=radeon options. After boot radeon module is still loaded, fglrx module (Catalyst) too and works fine. xorg.conf is the same than before I try radeon driver instead of fglrx (Catalyst 10.8). I don't know why the stand-by mode for monitor works fine again. Nothing special in logs. I'll try to do others tests to reproduce this bug.
Both the problem and its fix (installing the -49 kernel) confirmed on Sony Vaio FW21E with a Radeon HD3400 chip. Hope to see that kernel in Bodhi soon! :)
(In reply to comment #0) I experienced the same behaviour on my desktop with a Radeon 1950 chip, kernel-PAE, driver xorg-x11-drv-ati-6.13.0-1.fc13.i686 (ok in 2.6.33.8-149, broken in 2.6.34.6-47, fixed in 2.6.34.6-54). The problem still remains on my Laptop, though, with an Intel GW45 chip, kernel-PAE, driver xorg-x11-drv-intel-2.11.0-5.fc13.i686. Here is the corresponding output of lspci -v: 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device 30dd Flags: bus master, fast devsel, latency 0, IRQ 32 Memory at d0000000 (64-bit, non-prefetchable) [size=4M] Memory at c0000000 (64-bit, prefetchable) [size=256M] I/O ports at 60f0 [size=8] Expansion ROM at <unassigned> [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 3 Kernel driver in use: i915 Kernel modules: i915 Kind regards, Thomas
(In reply to comment #6) I forgot to mention that I run a _32_ bit kernel-PAE-2.6.34.6-54.fc13.i686. So my post should rather be added to bug 634064.
(In reply to comment #7) The latest kernel (2.6.34.7-56.fc13.i686.PAE) has now fixed the problem with the Intel GW45 Chip :-) Thomas
(In reply to comment #8) Please ignore my last comment (no. 8); the information is not correct. I.e. the problem still persists with the latest kernel 2.6.34.7-56.fc13.i686.PAE. Thomas
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
Can't add more experiences and tests beacause I'm running F15 with Gnome-Shell now. Can be close for me.
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.