Hide Forgot
Created attachment 545609 [details] dmesg Description of problem: When I returned from suspend, I could not get X back, it crashed and moved to the old non-accel one. In Xorg log I see: [ 31458.267] (WW) intel(0): I830DRI2GetMSC:1305 get vblank counter failed: Invalid argument [ 31458.272] (WW) intel(0): I830DRI2GetMSC:1305 get vblank counter failed: Invalid argument [ 31458.272] (WW) intel(0): first get vblank counter failed: Invalid argument [ 31458.277] (WW) intel(0): I830DRI2GetMSC:1305 get vblank counter failed: Invalid argument [ 31458.481] (WW) intel(0): I830DRI2GetMSC:1305 get vblank counter failed: Invalid argument [ 31458.503] (WW) intel(0): I830DRI2GetMSC:1305 get vblank counter failed: Invalid argument [ 31458.503] (WW) intel(0): first get vblank counter failed: Invalid argument [ 31458.590] (WW) intel(0): first get vblank counter failed: Invalid argument [ 31459.156] (WW) intel(0): first get vblank counter failed: Invalid argument [ 31459.179] (WW) intel(0): first get vblank counter failed: Invalid argument [ 31459.448] (WW) intel(0): first get vblank counter failed: Invalid argument [ 31459.499] (WW) intel(0): first get vblank counter failed: Invalid argument [ 31459.562] (WW) intel(0): first get vblank counter failed: Invalid argument [ 31459.589] (WW) intel(0): first get vblank counter failed: Invalid argument [ 31461.204] (WW) intel(0): I830DRI2ScheduleWaitMSC:1372 get vblank counter failed: Invalid argument [ 31461.243] (WW) intel(0): I830DRI2ScheduleWaitMSC:1372 get vblank counter failed: Invalid argument [ 31461.700] (WW) intel(0): I830DRI2ScheduleWaitMSC:1372 get vblank counter failed: Invalid argument [ 31461.718] (WW) intel(0): I830DRI2ScheduleWaitMSC:1372 get vblank counter failed: Invalid argument [ 31462.603] (WW) intel(0): I830DRI2ScheduleWaitMSC:1372 get vblank counter failed: Invalid argument [ 31543.062] (EE) intel(0): Detected a hung GPU, disabling acceleration. [ 31543.062] (EE) intel(0): When reporting this, please include i915_error_state from debugfs and the full dmesg. [ 31553.073] (II) evdev: Power Button: Close Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 545610 [details] Xorg log
Relevant part 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: Lenovo Device 20e4 Flags: bus master, fast devsel, latency 0, IRQ 48 Memory at f4400000 (64-bit, non-prefetchable) [size=4M] Memory at d0000000 (64-bit, prefetchable) [size=256M] I/O ports at 1800 [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 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) Subsystem: Lenovo Device 20e4 Flags: bus master, fast devsel, latency 0 Memory at f4200000 (64-bit, non-prefetchable) [size=1M] Capabilities: [d0] Power Management version 3
I can make this happen very reliably on my mostly-Rawhide machine: (1) Run a DVD in VLC. (2) Pause the DVD. (3) Close the lid (*note* my laptop is configured to *not* suspend). (4) Open lid. Consequences of this: (1) VLC cannot play at all (even after restart). (2) Terminal colours and messed up. (3) Acceleration is disabled. In xorg.log: [ 22845.859] (EE) intel(0): Detected a hung GPU, disabling acceleration. [ 22845.861] (EE) intel(0): When reporting this, please include i915_error_state from debugfs and the full dmesg. [ 22846.315] (II) AIGLX: Suspending AIGLX clients for VT switch [ 22848.249] (II) AIGLX: Resuming AIGLX clients after VT switch [ 22848.337] (II) intel(0): EDID vendor "LEN", prod id 16561 [ 22848.337] (II) intel(0): Printing DDC gathered Modelines: [ 22848.337] (II) intel(0): Modeline "1600x900"x0.0 108.50 1600 1648 1680 1920 900 903 908 942 -hsync -vsync (56.5 kHz) [ 22848.337] (II) intel(0): Modeline "1600x900"x0.0 90.43 1600 1648 1680 1920 900 903 908 942 -hsync -vsync (47.1 kHz) [ 22848.772] (--) SynPS/2 Synaptics TouchPad: touchpad found How do I enable debugfs to read that error state?
kernel: 3.2.0-0.rc1.git2.1.fc17.x86_64 xorg-x11-server-Xorg-1.11.1-1.fc16.x86_64 xorg-x11-drv-intel-2.16.0-2.fc16.x86_64 (as I said, "mostly" Rawhide, but lots of F16 packages still)
This also happened to me (or something similar) with F17. I don't know how exactly it happened. I locked the screen and when I unlocked it again, gnome-shell was down (it fell down about the time I unlocked the screen). This is tail of Xorg.0.log: [137583.532] (EE) intel(0): Detected a hung GPU, disabling acceleration. [137583.532] (EE) intel(0): When reporting this, please include i915_error_state from debugfs and the full dmesg. kernel: kernel-3.4.2-4.fc17.x86_64 xorg-x11-server-Xorg-1.12.2-3.fc17.x86_64 xorg-x11-drv-intel-2.19.0-5.fc17.x86_64
Created attachment 594469 [details] dmesg
Created attachment 594470 [details] Xorg.0.log
Created attachment 594471 [details] i915_error_state
I recently updated my laptop to almost pure F17, and the steps in comment 4 still cause this bug 100% reliably.
I have recently upgraded my desktop to fedora 17. I have observed that whenever I login after some time the my X crashes. On checking the Xorg.0.log I saw that I am getting similar error specified here. Here is the log excrept - [ 1065.491] (EE) intel(0): Detected a hung GPU, disabling acceleration. [ 1065.491] (EE) intel(0): When reporting this, please include i915_error_state from debugfs and the full dmesg. [ 1065.493] [mi] Increasing EQ size to 512 to prevent dropped events. [ 1065.493] [mi] EQ processing has resumed after 453 dropped events. [ 1065.493] [mi] This may be caused my a misbehaving driver monopolizing the server's resources. I am attaching my hardware profile, i915_error_state from debugfs and dmesg.
Created attachment 600990 [details] Hardware Profile My lshw command output
Created attachment 600991 [details] Xorg log
Created attachment 600992 [details] i915 Error State file
Created attachment 600993 [details] dmesg full output
I am seeing the same error after Fedora 18 upgrade: Detected a hung GPU, disabling acceleration. Right after start. #rpm -qa kernel xorg-x11-server-Xorg xorg-x11-drv-intel xorg-x11-drv-intel-2.20.16-1.fc18.i686 xorg-x11-drv-intel-2.20.16-1.fc18.x86_64 kernel-3.7.2-201.fc18.x86_64 xorg-x11-server-Xorg-1.13.1-4.fc18.x86_64
My screen suddenly goes completely black and switching to virtual terminals or switching back doesn't change anything. I must restart the system. After a restart, I see the following in my Xorg.0.log.old: [ 25693.349] (EE) intel(0): Detected a hung GPU, disabling acceleration. [ 25693.349] (EE) intel(0): When reporting this, please include i915_error_state from debugfs and the full dmesg. [ 25693.350] (WW) intel(0): I830DRI2GetMSC:1358 get vblank counter failed: Invalid argument [ 25727.234] (WW) intel(0): I830DRI2GetMSC:1358 get vblank counter failed: Invalid argument [ 25727.235] (WW) intel(0): I830DRI2GetMSC:1358 get vblank counter failed: Invalid argument [ 25762.454] (WW) intel(0): I830DRI2GetMSC:1358 get vblank counter failed: Invalid argument [ 25762.493] (WW) intel(0): I830DRI2GetMSC:1358 get vblank counter failed: Invalid argument I just hope that it is not a hardware problem!
The problem have not happened for me anymore, looks like that it is fixed in the updates.
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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.