Created attachment 699099 [details] dmesg from a problem session Description of problem: Sometimes, often after a suspend/resume cycle, the integrated graphics on my Intel i7 2760QM gets stuck in the Active state (100% as measured by powertop). This raises the temperature the system noticeably. Normally (like right now), it's only around 20% active and 80% in RC6. This is with: kernel-3.7.6-102.fc17.x86_64 xorg-x11-drv-intel-2.20.16-2.fc17.x86_64 although I have seen it with earlier kernels (including the last two of the 3.6 series for Fedora 17). How reproducible: Sporadically, but not rarely. Perhaps after 30-50% of suspend/resume cycles. sometimes happens spontaneously. Additional info: Sometimes another suspend/resume cycle returns things to normal. dmesg-issue.log was taken after a suspend/resume cycle I tried to get back to normal operation. (Ignore the sr 33:0:0:0: mess ages, they're due to a 3G dongle.) It contains the lines [108171.248801] [drm:init_ring_common] *ERROR* bsd ring initialization failed ctl 00000000 head 00000000 tail 00000000 start 00000000 [108171.248917] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [108171.396654] usb 1-1.2: reset full-speed USB device number 24 using ehci_hcd [108171.456531] dpm_run_callback(): pci_pm_resume+0x0/0xd0 returns -5 [108171.456532] PM: Device 0000:00:02.0 failed to resume async: error -5 dmesg-normal.log is from a functioning session. There are no errors logged in i915_error_state. Attempting to log out and back in doesn't work: GDM won't start, just get a black screen with a cursor. The attached Xorg.0.log and gdmlog.log were captured after this, and contain a lot of Failed to submit batch buffer, expect rendering corruption or even a frozen display: Invalid argument.
Created attachment 699100 [details] dmesg from working session
Created attachment 699101 [details] Xorg.0.log after trying to log back in
Created attachment 699102 [details] broken gdm log
Still present with 3.7.9-104.fc17.x86_64 xorg-x11-drv-intel-2.21.2-1.fc17.x86_64
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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 change the 'version' to a later Fedora version prior to Fedora 17's end of life. 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.
Still happening under Fedora 19: kernel-3.9.8-300.fc19.x86_64 xorg-x11-drv-intel-2.21.8-1.fc19.x86_64
Not seen this in a while now. Closing.