Bug 879823 - [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
Summary: [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 879825 901687 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-24 17:29 UTC by Mikhail
Modified: 2016-12-20 12:31 UTC (History)
41 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-20 12:31:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
i915_error_state (58.36 KB, application/x-7z-compressed)
2012-12-08 11:40 UTC, Mikhail
no flags Details
my kernel.spec which couldn't compile (81.10 KB, text/x-rpm-spec)
2013-02-10 09:39 UTC, Mikhail
no flags Details
i915_error_state 2 (2.14 MB, text/plain)
2013-05-22 09:19 UTC, Anton Arapov
no flags Details
contents of /sys/kernel/debug/dri/0/i915_error_state after GPU hang (2.22 MB, text/plain)
2013-05-29 09:52 UTC, Ferry Huberts
no flags Details
error state file for Thinkpad T520 Fedora 18 GNOME 3 (2.22 MB, text/plain)
2013-06-21 15:29 UTC, Ravishankar Srinivasan
no flags Details
Fedora 19 i915_error_state Thinkpad E420 (2.02 MB, text/plain)
2013-06-25 20:24 UTC, Igor Mammedov
no flags Details
Fedora 19 Xorg.0.log Thinkpad E420 (39.23 KB, text/plain)
2013-06-25 20:28 UTC, Igor Mammedov
no flags Details
i915_error_state (2.22 MB, text/plain)
2013-07-10 02:28 UTC, Michael Cobb
no flags Details
i915_error_state (2.14 MB, text/plain)
2013-07-16 20:50 UTC, Juan Orti
no flags Details
The i915 error state after my most recent GPU hang up (2.19 MB, text/plain)
2013-07-31 03:10 UTC, Aidan Talerico
no flags Details
Photo of corruption when GPU hangs (183.15 KB, image/jpeg)
2013-07-31 14:23 UTC, Randy Barlow
no flags Details
fresh i915 error state (2.17 MB, text/plain)
2013-08-09 10:13 UTC, Aidan Talerico
no flags Details


Links
System ID Private Priority Status Summary Last Updated
FreeDesktop.org 54226 0 None None None Never

Description Mikhail 2012-11-24 17:29:13 UTC
Description of problem:
With 3.6.7-5.fc18.i686 kernel in dmesg output sometimes occurs message:
[22826.654365] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
[22826.654369] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state


Seems this bug already fixed in drm-intel-next.

https://bugs.freedesktop.org/show_bug.cgi?id=54226

I want that this patch will be included in Fedora.

Comment 1 Josh Boyer 2012-11-26 14:48:16 UTC
(In reply to comment #0)
> Description of problem:
> With 3.6.7-5.fc18.i686 kernel in dmesg output sometimes occurs message:
> [22826.654365] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed...
> GPU hung
> [22826.654369] [drm] capturing error event; look for more information in
> /debug/dri/0/i915_error_state
> 
> 
> Seems this bug already fixed in drm-intel-next.
> 
> https://bugs.freedesktop.org/show_bug.cgi?id=54226
> 
> I want that this patch will be included in Fedora.

Adam, Dave, is this commit:

http://cgit.freedesktop.org/~danvet/drm-intel/commit/drivers/gpu/drm?h=drm-intel-next&id=1c8b46fc8c865189f562c9ab163d63863759712f

something that is stand-alone that can be cherry-picked?  I can't immediately tell from the commit log, and it isn't CC'd to stable so I'm thinking it isn't.

Comment 2 Josh Boyer 2012-11-26 14:49:21 UTC
*** Bug 879825 has been marked as a duplicate of this bug. ***

Comment 3 Dave Airlie 2012-12-04 09:08:00 UTC
Should be fine to backport yes.

Comment 4 Josh Boyer 2012-12-04 13:53:18 UTC
(In reply to comment #3)
> Should be fine to backport yes.

OK.  I'll look at getting that done later today.

Mikhail, I'll have a scratch kernel for you to test with and would appreciate your feedback on it once I put the link in this bug.

Comment 5 Josh Boyer 2012-12-05 14:09:45 UTC
OK, here's the scratch build.  Please test when it completes:

http://koji.fedoraproject.org/koji/taskinfo?taskID=4759096

Comment 6 Mikhail 2012-12-08 11:39:42 UTC
Problem repeated with patched kernel.

[118637.439016] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
[118637.439020] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state
[mikhail@localhost ~]$ uname -a
Linux localhost.localdomain 3.6.9-4.1.fc18.i686.PAE #1 SMP Wed Dec 5 15:16:33 UTC 2012 i686 i686 i386 GNU/Linux
[mikhail@localhost ~]$ sudo cat /sys/kernel/debug/dri/0/i915_error_state > i915_error_state
[sudo] password for mikhail: 
[mikhail@localhost ~]$

Comment 7 Mikhail 2012-12-08 11:40:30 UTC
Created attachment 659798 [details]
i915_error_state

Comment 8 Christopher Wawak 2013-01-04 20:21:26 UTC
kernel: [193364.241099] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
kernel: [193364.241104] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state

$ uname -a
Linux cwawak-rhlaptop 3.6.11-3.fc18.x86_64 #1 SMP Mon Dec 17 21:35:39 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

This is happening roughly every other day or so, I'll try to grab i915_error_state next time.

Comment 9 Mikhail 2013-01-10 01:31:11 UTC
Josh, can you create new kernel package for test new patch from upstream?

https://bugs.freedesktop.org/show_bug.cgi?id=54226#c26

https://bugs.freedesktop.org/attachment.cgi?id=72766

Comment 10 Josh Boyer 2013-01-10 14:36:25 UTC
(In reply to comment #9)
> Josh, can you create new kernel package for test new patch from upstream?
> 
> https://bugs.freedesktop.org/show_bug.cgi?id=54226#c26
> 
> https://bugs.freedesktop.org/attachment.cgi?id=72766

There's a different patch that has been submitted to stable for a GPU hung issue.  I'm not sure which would be preferred at this point.

Comment 11 Christopher Wawak 2013-01-10 21:30:30 UTC
[ 9418.403018] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
[ 9418.403023] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state

# uname -a
Linux localhost 3.7.1-2.fc18.x86_64 #1 SMP Fri Jan 4 00:10:48 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

$ sudo cat /sys/kernel/debug/dri/0/i915_error_state > i915_error_state
cat: /sys/kernel/debug/dri/0/i915_error_state: Cannot allocate memory

Couldn't grab i915_error_state.

Comment 12 Mikhail 2013-01-13 18:50:22 UTC
(In reply to comment #10)
> There's a different patch that has been submitted to stable for a GPU hung
> issue.  I'm not sure which would be preferred at this point.

Which patches do you mean?
I mean last patch from comment 26.

Comment 13 Paulo Fidalgo 2013-01-23 12:43:46 UTC
I have this bug too... quick steps to reproduce: 
install xbmc (rpmfusion)
install libva and libva-intel-driver
enable vaapi e start playing a movie

with a intel i5-3570K.

Comment 14 Christopher Wawak 2013-01-28 21:57:47 UTC
What progress is being made on this issue? What can I do to help?

It's seriously impeding my ability to use Fedora 18 on a Thinkpad T420s.

Thanks!

Comment 15 Paulo Fidalgo 2013-01-29 09:41:05 UTC
Christopher apparently this bug has been fixed in the current stable kernel.
Please check https://admin.fedoraproject.org/updates/F18/FEDORA-2013-1443

I haven't updated yet, but I'll do it and then I'll report here.

Comment 16 Jürgen Geuter 2013-01-29 09:43:49 UTC
It seems to be fixed in the Fedora18 stable kernel, the problem hasn't occurred here after updating to it for a few days (where it used to happen multiply times each day)

Comment 17 Mikhail 2013-01-29 16:07:39 UTC
I still receive drm:i915_hangcheck_hung error message in dmesg output:
[125692.981672] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
[127544.267347] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
[127966.207633] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
[128452.389972] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung

But my kernel is 3.7.4-204

$ uname -a
Linux localhost.localdomain 3.7.4-204.fc18.i686.PAE #1 SMP Wed Jan 23 16:58:41 UTC 2013 i686 i686 i386 GNU/Linux


This bug still not fixed yet.

Which patch are you applied for it?

Comment 18 Mikhail 2013-02-10 09:37:04 UTC
Please help compile kernel with:
This https://bugs.freedesktop.org/attachment.cgi?id=73577
and this https://bugs.freedesktop.org/attachment.cgi?id=72766
patches, for each patch separate kernel for test purpose

Comment 19 Mikhail 2013-02-10 09:39:16 UTC
Created attachment 695697 [details]
my kernel.spec which couldn't compile

Comment 20 Mikhail 2013-02-10 09:40:44 UTC
drivers/gpu/drm/i915/intel_ringbuffer.c: In function 'gen6_add_request':
drivers/gpu/drm/i915/intel_ringbuffer.c:611:3: error: too few arguments to function 'update_mboxes'
drivers/gpu/drm/i915/intel_ringbuffer.c:557:1: note: declared here
drivers/gpu/drm/i915/intel_ringbuffer.c:612:3: error: too few arguments to function 'update_mboxes'
drivers/gpu/drm/i915/intel_ringbuffer.c:557:1: note: declared here
make[4]: *** [drivers/gpu/drm/i915/intel_ringbuffer.o] Error 1
make[3]: *** [drivers/gpu/drm/i915] Error 2
make[2]: *** [drivers/gpu/drm] Error 2
make[1]: *** [drivers/gpu] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [drivers] Error 2
make: *** Waiting for unfinished jobs....
[reply] [-] Comment 36

Comment 21 brhahlen 2013-02-11 12:17:20 UTC
I also get this error on Fedora 18 on a Thinkpad T520.
dmesg:
[ 6934.976050] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
[ 6934.976055] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state

Linux 3.7.6-201.fc18.x86_64 #1 SMP Mon Feb 4 15:54:08 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Comment 22 Charly42 2013-03-30 14:29:58 UTC
Hello,

i have the same Bug with CPU intel G645 and openelec 3.0
when do you thinks the bug fixed?

Many Thanks for help

Charly

Mar 28 19:24:55 openelec user.err kernel: [   94.646120] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
Mar 28 19:24:55 openelec user.info kernel: [   94.646124] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state
Mar 28 19:25:01 openelec user.err kernel: [  101.009793] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
Mar 28 19:26:00 openelec user.err kernel: [  159.705871] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
Mar 28 19:26:06 openelec user.err kernel: [  166.348828] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
Mar 28 19:26:13 openelec user.err kernel: [  172.991785] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
Mar 28 19:26:15 openelec user.err kernel: [  174.494596] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
Mar 28 19:26:15 openelec user.err kernel: [  174.494644] [drm:i915_reset] *ERROR* GPU hanging too fast, declaring wedged!
Mar 28 19:26:15 openelec user.err kernel: [  174.494645] [drm:i915_reset] *ERROR* Failed to reset chip.
Mar 28 19:26:15 openelec user.info kernel: [  174.538630] Jobworker[1210]: segfault at 7f07a8067e59 ip 00007f07a8067e59 sp 00007f078abc3378 error 14

Comment 23 Christopher Wawak 2013-05-08 20:04:34 UTC
Still running into this problem.

Linux localhost 3.8.11-200.fc18.x86_64 #1 SMP Wed May 1 19:44:27 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

I didn't notice it for a week when I was not in the dock, but noticed the issue again when I am plugged into my dock with a 24" and 20" LCD plugged in (internal LCD turned off.)

May  8 15:36:40 localhost kernel: [92938.244482] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
May  8 15:36:40 localhost kernel: [92938.244487] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state
May  8 15:36:48 localhost kernel: [92946.237923] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung

and when I tried to grab the i915_error_state, I get a page allocation error:

May  8 15:38:01 localhost kernel: [93018.742214] cat: page allocation failure: order:9, mode:0x1040d0
May  8 15:38:01 localhost kernel: [93018.742218] Pid: 17595, comm: cat Tainted: G        W    3.8.11-200.fc18.x86_64 #1
May  8 15:38:01 localhost kernel: [93018.742219] Call Trace:
May  8 15:38:01 localhost kernel: [93018.742226]  [<ffffffff811380d9>] warn_alloc_failed+0xe9/0x150
May  8 15:38:01 localhost kernel: [93018.742229]  [<ffffffff8164b36d>] ? __alloc_pages_direct_compact+0x182/0x194
May  8 15:38:01 localhost kernel: [93018.742231]  [<ffffffff8113c2fe>] __alloc_pages_nodemask+0x80e/0xa80
May  8 15:38:01 localhost kernel: [93018.742234]  [<ffffffff8117a5e8>] alloc_pages_current+0xb8/0x190
May  8 15:38:01 localhost kernel: [93018.742237]  [<ffffffff81136fea>] __get_free_pages+0x2a/0x80
May  8 15:38:01 localhost kernel: [93018.742239]  [<ffffffff81185909>] kmalloc_order_trace+0x39/0xb0
May  8 15:38:01 localhost kernel: [93018.742240]  [<ffffffff81185b40>] __kmalloc+0x1c0/0x250
May  8 15:38:01 localhost kernel: [93018.742242]  [<ffffffff81184747>] ? kfree+0x157/0x170
May  8 15:38:01 localhost kernel: [93018.742244]  [<ffffffff811bf42e>] seq_read+0x10e/0x3b0
May  8 15:38:01 localhost kernel: [93018.742247]  [<ffffffff8119dce9>] vfs_read+0xa9/0x180
May  8 15:38:01 localhost kernel: [93018.742248]  [<ffffffff8119de12>] sys_read+0x52/0xa0
May  8 15:38:01 localhost kernel: [93018.742252]  [<ffffffff816577be>] ? do_page_fault+0xe/0x10
May  8 15:38:01 localhost kernel: [93018.742254]  [<ffffffff8165be19>] system_call_fastpath+0x16/0x1b
May  8 15:38:01 localhost kernel: [93018.742255] Mem-Info:
May  8 15:38:01 localhost kernel: [93018.742256] Node 0 DMA per-cpu:
May  8 15:38:01 localhost kernel: [93018.742257] CPU    0: hi:    0, btch:   1 usd:   0
May  8 15:38:01 localhost kernel: [93018.742258] CPU    1: hi:    0, btch:   1 usd:   0
May  8 15:38:01 localhost kernel: [93018.742259] CPU    2: hi:    0, btch:   1 usd:   0
May  8 15:38:01 localhost kernel: [93018.742259] CPU    3: hi:    0, btch:   1 usd:   0
May  8 15:38:01 localhost kernel: [93018.742260] Node 0 DMA32 per-cpu:
May  8 15:38:01 localhost kernel: [93018.742261] CPU    0: hi:  186, btch:  31 usd:   0
May  8 15:38:01 localhost kernel: [93018.742262] CPU    1: hi:  186, btch:  31 usd:   0
May  8 15:38:01 localhost kernel: [93018.742263] CPU    2: hi:  186, btch:  31 usd:   0
May  8 15:38:01 localhost kernel: [93018.742263] CPU    3: hi:  186, btch:  31 usd:   0
May  8 15:38:01 localhost kernel: [93018.742264] Node 0 Normal per-cpu:
May  8 15:38:01 localhost kernel: [93018.742265] CPU    0: hi:  186, btch:  31 usd:   0
May  8 15:38:01 localhost kernel: [93018.742265] CPU    1: hi:  186, btch:  31 usd:   0
May  8 15:38:01 localhost kernel: [93018.742266] CPU    2: hi:  186, btch:  31 usd:   0
May  8 15:38:01 localhost kernel: [93018.742267] CPU    3: hi:  186, btch:  31 usd:   0
May  8 15:38:01 localhost kernel: [93018.742269] active_anon:609781 inactive_anon:119636 isolated_anon:0
May  8 15:38:01 localhost kernel: [93018.742269]  active_file:440429 inactive_file:439906 isolated_file:0
May  8 15:38:01 localhost kernel: [93018.742269]  unevictable:952 dirty:108 writeback:0 unstable:0
May  8 15:38:01 localhost kernel: [93018.742269]  free:254868 slab_reclaimable:53051 slab_unreclaimable:17425
May  8 15:38:01 localhost kernel: [93018.742269]  mapped:41776 shmem:73070 pagetables:15919 bounce:0
May  8 15:38:01 localhost kernel: [93018.742269]  free_cma:0
May  8 15:38:01 localhost kernel: [93018.742271] Node 0 DMA free:15344kB min:124kB low:152kB high:184kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15104kB managed:15360kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB slab_unreclaimable:16kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes
May  8 15:38:01 localhost kernel: [93018.742274] lowmem_reserve[]: 0 3312 7822 7822
May  8 15:38:01 localhost kernel: [93018.742276] Node 0 DMA32 free:809648kB min:28560kB low:35700kB high:42840kB active_anon:837140kB inactive_anon:108356kB active_file:785292kB inactive_file:730236kB unevictable:92kB isolated(anon):0kB isolated(file):0kB present:3391540kB managed:3332476kB mlocked:92kB dirty:64kB writeback:0kB mapped:15836kB shmem:30360kB slab_reclaimable:69548kB slab_unreclaimable:6904kB kernel_stack:336kB pagetables:7844kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
May  8 15:38:01 localhost kernel: [93018.742279] lowmem_reserve[]: 0 0 4510 4510
May  8 15:38:01 localhost kernel: [93018.742280] Node 0 Normal free:194480kB min:38892kB low:48612kB high:58336kB active_anon:1601984kB inactive_anon:370188kB active_file:976424kB inactive_file:1029388kB unevictable:3716kB isolated(anon):0kB isolated(file):0kB present:4618656kB managed:4561328kB mlocked:3716kB dirty:368kB writeback:0kB mapped:151268kB shmem:261920kB slab_reclaimable:142656kB slab_unreclaimable:62780kB kernel_stack:4232kB pagetables:55832kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
May  8 15:38:01 localhost kernel: [93018.742283] lowmem_reserve[]: 0 0 0 0
May  8 15:38:01 localhost kernel: [93018.742285] Node 0 DMA: 0*4kB 0*8kB 1*16kB (U) 1*32kB (U) 1*64kB (U) 1*128kB (U) 1*256kB (U) 1*512kB (U) 0*1024kB 1*2048kB (R) 3*4096kB (M) = 15344kB
May  8 15:38:01 localhost kernel: [93018.742291] Node 0 DMA32: 13104*4kB (UEMR) 10711*8kB (UEMR) 5798*16kB (UEMR) 2971*32kB (UEMR) 2445*64kB (UEMR) 848*128kB (UEMR) 366*256kB (UEM) 129*512kB (UEMR) 56*1024kB (UEMR) 1*2048kB (E) 0*4096kB = 810104kB
May  8 15:38:01 localhost kernel: [93018.742297] Node 0 Normal: 2375*4kB (UEM) 2239*8kB (UEM) 1617*16kB (UEM) 1709*32kB (UEM) 665*64kB (UEM) 221*128kB (UEM) 53*256kB (UEM) 3*512kB (EM) 1*1024kB (U) 0*2048kB 0*4096kB = 194948kB
May  8 15:38:01 localhost kernel: [93018.742303] 953976 total pagecache pages
May  8 15:38:01 localhost kernel: [93018.742304] 2 pages in swap cache
May  8 15:38:01 localhost kernel: [93018.742305] Swap cache stats: add 1465, delete 1463, find 667/667
May  8 15:38:01 localhost kernel: [93018.742305] Free swap  = 7944168kB
May  8 15:38:01 localhost kernel: [93018.742306] Total swap = 7944188kB
May  8 15:38:01 localhost kernel: [93018.760469] 2057712 pages RAM
May  8 15:38:01 localhost kernel: [93018.760471] 71529 pages reserved
May  8 15:38:01 localhost kernel: [93018.760472] 1905068 pages shared
May  8 15:38:01 localhost kernel: [93018.760472] 1186634 pages non-shared

Comment 24 Anton Arapov 2013-05-22 09:18:03 UTC
+1

[ 2653.470231] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
[anton@bandura ~]$ uname -a
Linux bandura.laptop 3.9.2-301.fc19.x86_64 #1 SMP Mon May 13 12:36:24 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Comment 25 Anton Arapov 2013-05-22 09:19:15 UTC
Created attachment 751616 [details]
i915_error_state 2

Comment 26 Ferry Huberts 2013-05-29 09:52:20 UTC
Created attachment 754277 [details]
contents of /sys/kernel/debug/dri/0/i915_error_state after GPU hang

Since a few weeks I've been having this too on my Lenovo W520.

It's very annoying and happens randomly during the day, usually when I'm right in the middle of something.
I also have the distinct feeling that having flash and/or skype loaded/running seems to trigger it sooner. But I might be entirely wrong there.

mesa-dri-drivers.i686       9.1-3.fc18
mesa-dri-drivers.x86_64     9.1-3.fc18
mesa-dri-filesystem.i686    9.1-3.fc18
mesa-dri-filesystem.x86_64  9.1-3.fc18
xorg-x11-drv-intel.x86_64   2.21.6-1.fc18

Comment 27 Ferry Huberts 2013-05-29 09:55:18 UTC
forgot the installed kernel rpms...

kernel.x86_64                  3.8.11-200.fc18
kernel.x86_64                  3.9.2-200.fc18
kernel.x86_64                  3.9.4-200.fc18
kernel-devel.x86_64            3.8.11-200.fc18
kernel-devel.x86_64            3.9.2-200.fc18
kernel-devel.x86_64            3.9.4-200.fc18
kernel-headers.x86_64          3.9.4-200.fc18
kernel-modules-extra.x86_64    3.8.11-200.fc18
kernel-modules-extra.x86_64    3.9.2-200.fc18
kernel-modules-extra.x86_64    3.9.4-200.fc18

Comment 28 Christopher J. 2013-06-17 15:15:08 UTC
Just received this error too on a Dell Latitude E5420 running Fedora 18
Running KDE4 with desktop effects turned on.  All I did was click on a spreadsheet document in Google Docs using Chrome, and it hung.

[ 6893.718127] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
[ 6893.718156] [drm] capturing error event; look for more information in/sys/kernel/debug/dri/0/i915

Intersting thing is that I can hit CTRL-ALT-F2 or another virtual terminal, switch to it, and then switch back to GUI with CTRL-ALT-F1 and everything is back working again.  It seems to hang until I switch the display back/forth between text and graphical again.

Comment 29 Christopher J. 2013-06-18 14:27:05 UTC
(In reply to Christopher J. from comment #28)
> Just received this error too on a Dell Latitude E5420 running Fedora 18
> Running KDE4 with desktop effects turned on.  All I did was click on a
> spreadsheet document in Google Docs using Chrome, and it hung.
> 
> [ 6893.718127] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed...
> GPU hung
> [ 6893.718156] [drm] capturing error event; look for more information
> in/sys/kernel/debug/dri/0/i915
> 
> Intersting thing is that I can hit CTRL-ALT-F2 or another virtual terminal,
> switch to it, and then switch back to GUI with CTRL-ALT-F1 and everything is
> back working again.  It seems to hang until I switch the display back/forth
> between text and graphical again.

kernel-3.9.4-200.fc18.x86_64
kernel-modules-extra-3.9.2-200.fc18.x86_64
kernel-modules-extra-3.9.4-200.fc18.x86_64
kernel-modules-extra-3.9.5-201.fc18.x86_64
kernel-3.9.2-200.fc18.x86_64
kernel-3.9.5-201.fc18.x86_64
xorg-x11-drv-intel-2.21.8-1.fc18.x86_64

KDE Platform Version 4.10.4

Comment 30 Ravishankar Srinivasan 2013-06-21 15:27:16 UTC
I see this issue too. Almost everyday it hangs once or twice. Switch to another tty and then switch back seems to unfreeze my Thinkpad T520

Jun 21 20:42:20 dhcp-0-126 kernel: [ 5615.933753] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
Jun 21 20:42:20 dhcp-0-126 kernel: [ 5615.933764] [drm] capturing error event; look for more information in/sys/kernel/debug/dri/0/i915_error_state

Comment 31 Ravishankar Srinivasan 2013-06-21 15:29:46 UTC
Created attachment 763881 [details]
error state file for Thinkpad T520 Fedora 18 GNOME 3

Comment 32 Ravishankar Srinivasan 2013-06-21 15:33:24 UTC
forgot to add env details:

F18 latest updates (June 21 2013). 64-bit

[rsriniva@valhalla ~]$ uname -a
Linux valhalla 3.9.6-200.fc18.x86_64 #1 SMP Thu Jun 13 18:56:55 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

[rsriniva@valhalla ~]$ lspci -vv
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
	Subsystem: Lenovo Device 21cf
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
	Latency: 0
	Capabilities: <access denied>

00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
	Subsystem: Lenovo Device 21cf
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 44
	Region 0: Memory at f0000000 (64-bit, non-prefetchable) [size=4M]
	Region 2: Memory at e0000000 (64-bit, prefetchable) [size=256M]
	Region 4: I/O ports at 4000 [size=64]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: <access denied>
	Kernel driver in use: i915

00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
	Subsystem: Lenovo Device 21cf
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 45
	Region 0: Memory at f1525000 (64-bit, non-prefetchable) [size=16]
	Capabilities: <access denied>
	Kernel driver in use: mei

00:16.3 Serial controller: Intel Corporation 6 Series/C200 Series Chipset Family KT Controller (rev 04) (prog-if 02 [16550])
	Subsystem: Lenovo Device 21cf
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin B routed to IRQ 19
	Region 0: I/O ports at 40b0 [size=8]
	Region 1: Memory at f152c000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	Kernel driver in use: serial

00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04)
	Subsystem: Lenovo Device 21ce
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 43
	Region 0: Memory at f1500000 (32-bit, non-prefetchable) [size=128K]
	Region 1: Memory at f152b000 (32-bit, non-prefetchable) [size=4K]
	Region 2: I/O ports at 4080 [size=32]
	Capabilities: <access denied>
	Kernel driver in use: e1000e

00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) (prog-if 20 [EHCI])
	Subsystem: Lenovo Device 21cf
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at f152a000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: <access denied>
	Kernel driver in use: ehci-pci

00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04)
	Subsystem: Lenovo Device 21cf
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 47
	Region 0: Memory at f1520000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: snd_hda_intel

00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4) (prog-if 00 [Normal decode])
	Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b4) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
	Memory behind bridge: f1400000-f14fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b4) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Bus: primary=00, secondary=0d, subordinate=0d, sec-latency=0
	I/O behind bridge: 00003000-00003fff
	Memory behind bridge: f0c00000-f13fffff
	Prefetchable memory behind bridge: 00000000f0400000-00000000f0bfffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) (prog-if 20 [EHCI])
	Subsystem: Lenovo Device 21cf
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 23
	Region 0: Memory at f1529000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: <access denied>
	Kernel driver in use: ehci-pci

00:1f.0 ISA bridge: Intel Corporation QM67 Express Chipset Family LPC Controller (rev 04)
	Subsystem: Lenovo Device 21cf
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Capabilities: <access denied>
	Kernel driver in use: lpc_ich

00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 04) (prog-if 01 [AHCI 1.0])
	Subsystem: Lenovo Device 21cf
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin B routed to IRQ 42
	Region 0: I/O ports at 40a8 [size=8]
	Region 1: I/O ports at 40bc [size=4]
	Region 2: I/O ports at 40a0 [size=8]
	Region 3: I/O ports at 40b8 [size=4]
	Region 4: I/O ports at 4060 [size=32]
	Region 5: Memory at f1528000 (32-bit, non-prefetchable) [size=2K]
	Capabilities: <access denied>
	Kernel driver in use: ahci

00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04)
	Subsystem: Lenovo Device 21cf
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin C routed to IRQ 18
	Region 0: Memory at f1524000 (64-bit, non-prefetchable) [size=256]
	Region 4: I/O ports at efa0 [size=32]
	Kernel driver in use: i801_smbus

03:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300 (rev 3e)
	Subsystem: Intel Corporation Centrino Ultimate-N 6300 3x3 AGN
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 46
	Region 0: Memory at f1400000 (64-bit, non-prefetchable) [size=8K]
	Capabilities: <access denied>
	Kernel driver in use: iwlwifi

0d:00.0 System peripheral: Ricoh Co Ltd PCIe SDXC/MMC Host Controller (rev 08) (prog-if 01)
	Subsystem: Lenovo Device 21cf
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at f0c00000 (32-bit, non-prefetchable) [size=256]
	Capabilities: <access denied>
	Kernel driver in use: sdhci-pci

[rsriniva@valhalla ~]$ rpm -qa | grep intel
xorg-x11-drv-intel-2.21.8-1.fc18.x86_64

[rsriniva@valhalla ~]$ rpm -qa | grep mesa
mesa-libxatracker-9.2-0.7.20130528.fc18.x86_64
mesa-libEGL-9.2-0.7.20130528.fc18.x86_64
mesa-libGL-9.2-0.7.20130528.fc18.i686
mesa-libGLU-9.0.0-1.fc18.x86_64
mesa-filesystem-9.2-0.7.20130528.fc18.x86_64
mesa-libGLES-9.2-0.7.20130528.fc18.x86_64
mesa-libGL-9.2-0.7.20130528.fc18.x86_64
mesa-libglapi-9.2-0.7.20130528.fc18.i686
mesa-libgbm-9.2-0.7.20130528.fc18.i686
mesa-libglapi-9.2-0.7.20130528.fc18.x86_64
mesa-libgbm-9.2-0.7.20130528.fc18.x86_64
mesa-libGLU-9.0.0-1.fc18.i686
mesa-libEGL-9.2-0.7.20130528.fc18.i686
mesa-dri-drivers-9.2-0.7.20130528.fc18.x86_64

[rsriniva@valhalla ~]$ rpm -qa | grep kernel
kernel-devel-3.9.6-200.fc18.x86_64
abrt-addon-kerneloops-2.1.4-3.fc18.x86_64
kernel-modules-extra-3.9.6-200.fc18.x86_64
libreport-plugin-kerneloops-2.1.4-4.fc18.x86_64
kernel-3.9.4-200.fc18.x86_64
kernel-headers-3.9.6-200.fc18.x86_64
kernel-3.9.6-200.fc18.x86_64
kernel-modules-extra-3.9.4-200.fc18.x86_64

Comment 33 Igor Mammedov 2013-06-25 20:24:51 UTC
Created attachment 765278 [details]
Fedora 19 i915_error_state Thinkpad E420

kernel-3.9.5-301.fc19.x86_64
xorg-x11-drv-intel-2.21.8-1.fc19.x86_64

Most often GPU freeze happens during google hangout video call, i.e. display freezes but sound still works. Attempt to switch to another VT doesn't work, i.e. screen stays frozen.

Host is accessible via ssh and killing Xorg restores VT console and after that GDM restarts and new X session works ok for some time.

There is backtrace in Xorg.log which will be attached with next attachment.

Comment 34 Igor Mammedov 2013-06-25 20:28:28 UTC
Created attachment 765280 [details]
Fedora 19 Xorg.0.log Thinkpad E420

complete log is in attachment
--- cut ---
(EE) [mi] EQ overflowing.  Additional events will be discarded until existing events are processed.
(EE) 
(EE) Backtrace:
(EE) 0: /usr/bin/Xorg (mieqEnqueue+0x22b) [0x575fab]
(EE) 1: /usr/bin/Xorg (QueuePointerEvents+0x52) [0x44d612]
(EE) 2: /usr/lib64/xorg/modules/input/synaptics_drv.so (_init+0x29c8) [0x7f14783ed968]
(EE) 3: /usr/lib64/xorg/modules/input/synaptics_drv.so (_init+0x46ea) [0x7f14783f1d8a]
(EE) 4: /usr/bin/Xorg (DPMSSupported+0xe8) [0x485978]
(EE) 5: /usr/bin/Xorg (xf86SerialModemClearBits+0x230) [0x4adf30]
(EE) 6: /lib64/libpthread.so.0 (__restore_rt+0x0) [0x3ccc20ef9f]
(EE) 7: /lib64/libpthread.so.0 (__read_nocancel+0x24) [0x3ccc20e0c4]
(EE) 8: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x57397) [0x7f147a6ea767]
(EE) 9: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x57dd0) [0x7f147a6eb930]
(EE) 10: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x47c50) [0x7f147a6cb5a0]
(EE) 11: /usr/bin/Xorg (BlockHandler+0x44) [0x43ae44]
(EE) 12: /usr/bin/Xorg (WaitForSomething+0x124) [0x4660b4]
(EE) 13: /usr/bin/Xorg (SendErrorToClient+0xe1) [0x436b31]
(EE) 14: /usr/bin/Xorg (_init+0x3ab2) [0x429ae2]
(EE) 15: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x3ccbe21b75]
(EE) 16: /usr/bin/Xorg (_start+0x29) [0x426741]
(EE) 17: ? (?+0x29) [0x29]
(EE) 
(EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack.
(EE) [mi] mieq is *NOT* the cause.  It is a victim.
--- cut ---

Comment 35 Ravishankar Srinivasan 2013-06-26 02:50:25 UTC
I did a "yum downgrade xorg-x11-drv-intel" and T520 is much more stable now. It rolled back to version 2.20.x of the Intel Driver.

Comment 36 moondrake 2013-07-03 18:02:13 UTC
Same here on T410. 2.21 seems completely unstable as I get horrible performance and a hung GPU very easily (This seems unrelated to the semaphore problem mentioned by the original report: I used sysfs to switch off semaphores. So I am guessing some of us are seeing a different bug).

2.20.14 is fine.

Comment 37 Ferry Huberts 2013-07-03 19:00:12 UTC
I ran on 2.20.14 for a while too but that one was also unstable for me, causing just a many GPU hangs.

this morning I upgraded to F19 and haven't seen the GPU hang yet.
kernel   3.9.8-300.fc19
xorg     2.21.8-1.fc19

Comment 38 Ferry Huberts 2013-07-04 06:57:02 UTC
Ah, it's not fixed.
The thing I now see is that the (drawn) mouse cursor doesn't move but that the actual cursor still moves (I can see that because of the changing highlights in my frippery favorites on the top of the screen).

so the full GPU hang has become a hang of the cursor planes

Comment 39 Ferry Huberts 2013-07-08 16:24:19 UTC
After a some days working with F19 on my W520, I can say that the hangs of the cursor planes happens extremely often.

At least the full GPU doesn't hang, but it's still very annoying ;-)

Comment 40 Michael Cobb 2013-07-10 02:24:48 UTC
I am having the same problem too after upgrading to Fedora 19. It most often happens when using Flash (eg. YouTube (in Chrome)) but sometimes happens when i'm doing other things, even just using gnome-shell with no windows open! The whole Xorg display 'freezes' (the video appears stuck and the display will not respond to keyboard/mouse input. Although I can still move the mouse pointer, the display does not respond to mouse clicks. I am unable to switch to a TTY).

I know the system hasn't totally crashed, as I can still move the cursor and hear any audio playing normally (this would suggest an Xorg/video driver error). This goes on for around 10 seconds (sometimes longer). My system will usually TOTALLY CRASH - the cursor stops moving, my system totally locks up, and I hear a 1 second loop of any audio playing. I have to force power off my laptop and lose all my work.

The last few times this has happened, after 10 seconds or so, my machine has become responsive again, and I can investigate the error (which has lead me here). I wouldn't blame this entirely on flash, however it does happen more often when flash is being used. It's very frustrating when it happens almost once every day and I have to lose all of my work and reboot my laptop.

DMESG Shows:
=====================================================
[ 1510.714479] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
[ 1510.714496] [drm] capturing error event; look for more information in/sys/kernel/debug/dri/0/i915_error_state
[ 2746.409651] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
=====================================================

I get the following in /var/log/messages:
=====================================================
Jul 10 02:11:52 cobby-aspire-5750 kernel: [ 1510.714479] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
Jul 10 02:11:52 cobby-aspire-5750 kernel: [ 1510.714496] [drm] capturing error event; look for more information in/sys/kernel/debug/dri/0/i915_error_state
Jul 10 02:32:27 cobby-aspire-5750 kernel: [ 2746.409651] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
Jul 10 02:32:27 cobby-aspire-5750 /etc/gdm/Xsession[1110]: Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Jul 10 02:32:27 cobby-aspire-5750 /etc/gdm/Xsession[1110]: Window manager warning: Got a request to focus 0x1a00007 (Desktop) with a timestamp of 0.  This shouldn't happen!
=====================================================

My CPU is "Intel(R) Core(TM) i3-2310M CPU @ 2.10GHz" (/proc/cpuinfo) 

Integrated graphics are Intel HD 3000 Integrated graphics (VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09))

I will be so glad when Xorg is gone and Flash player has died.

I will also attach /sys/kernel/debug/dri/0/i915_error_state

Comment 41 Michael Cobb 2013-07-10 02:28:17 UTC
Created attachment 771341 [details]
i915_error_state

Comment 42 Juan Orti 2013-07-16 20:50:56 UTC
Created attachment 774483 [details]
i915_error_state

I'm suffering this error around 6 times per day, my computer is becoming unusable.
It happens anytime, I'm using KDE and suddenly the display becames corrupted, with a lot of weird color pixels.

The versions I'm using are:
kernel-3.9.9-302.fc19.x86_64
xorg-x11-drv-intel-2.21.8-1.fc19.x86_64

My hardware:
Intel Core i7-2600K
Asus P8Z68-V LE motherboard

00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
        Subsystem: ASUSTeK Computer Inc. Device 844d
        Flags: bus master, fast devsel, latency 0, IRQ 58
        Memory at f7800000 (64-bit, non-prefetchable) [size=4M]
        Memory at e0000000 (64-bit, prefetchable) [size=256M]
        I/O ports at f000 [size=64]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Capabilities: [d0] Power Management version 2
        Capabilities: [a4] PCI Advanced Features
        Kernel driver in use: i915

Comment 43 Scott Radvan 2013-07-25 22:38:53 UTC
Same issue here:

Jul 26 08:33:53 t520 kernel: [ 1135.615221] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung

I tried updating to xorg-x11-drv-intel-2.21.12-1.fc19.x86_64 from updates-testing, no luck, problem still happening.

Thinkpad T520

3.9.9-302.fc19.x86_64

Comment 44 Laerte Barbalho Jr. 2013-07-27 11:53:36 UTC
Same here. Last lines of dmesg:
[15399.626850] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
[15502.735410] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
[15502.738388] [drm:__gen6_gt_force_wake_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[15582.825907] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
[17040.485125] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
[18273.874969] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
[18358.971136] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung

Occurs mostly when I play games (native and via Wine). After the hang period I can switch to VT and back and the video becomes correct again.

Hardware:

00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
        Subsystem: Dell Device 0502
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 42
        Region 0: Memory at f6800000 (64-bit, non-prefetchable) [size=4M]
        Region 2: Memory at e0000000 (64-bit, prefetchable) [size=256M]
        Region 4: I/O ports at f000 [size=64]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
                Address: fee0f00c  Data: 41a1
        Capabilities: [d0] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [a4] PCI Advanced Features
                AFCap: TP+ FLR+
                AFCtrl: FLR-
                AFStatus: TP-
        Kernel driver in use: i915

Comment 45 Aidan Talerico 2013-07-31 03:07:04 UTC
I am also experiencing this GPU hang problem while playing games and more rarely when watching HD video. I am not having the cursor hang problem others are describing, but the full GPU hang.

From journalctl:
Jul 30 21:39:32 localhost kernel: [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
Jul 30 21:39:32 localhost kernel: [drm] capturing error event; look for more information in /sys/kernel/debug/dri/0/i915_error_state

Versions:
kernel.3.10.3-300.fc19.x86_64
xorg-x11-drv-intel.2.21.12-1.fc19.x86_64

Hardware:
Dell Inspiron 15R laptop
Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
	Subsystem: Dell Device 04b0
	Flags: bus master, fast devsel, latency 0, IRQ 51
	Memory at f6800000 (64-bit, non-prefetchable) [size=4M]
	Memory at e0000000 (64-bit, prefetchable) [size=256M]
	I/O ports at f000 [size=64]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [d0] Power Management version 2
	Capabilities: [a4] PCI Advanced Features
	Kernel driver in use: i915

Comment 46 Aidan Talerico 2013-07-31 03:10:03 UTC
Created attachment 780915 [details]
The i915 error state after my most recent GPU hang up

Comment 47 Randy Barlow 2013-07-31 14:21:00 UTC
I've been finding that this happens quite reproducibly on my F19 T530 ever since upgrading to kernel 3.10. Any time I suspend, I get a very corrupted screen when resuming, and /var/log/messages will have the GPU hung message in it.

Comment 48 Randy Barlow 2013-07-31 14:23:24 UTC
Created attachment 781172 [details]
Photo of corruption when GPU hangs

Comment 49 Aidan Talerico 2013-08-09 10:11:08 UTC
Problem still persists on recent kernel and xorg-x11-drv-intel updates.

kernel.x86_64.3.10.4-300.fc19
xorg-x11-drv-intel.x86_64.2.21.12-2.fc19
xorg-x11-server-Xorg.x86_64.1.14.2-9.fc19

Would I be better served taking this to the freedesktop.org bugzilla?

Comment 50 Aidan Talerico 2013-08-09 10:13:37 UTC
Created attachment 784787 [details]
fresh i915 error state

Comment 51 Ferry Huberts 2013-08-09 10:23:32 UTC
My situation (on fully updated software) continues to be 'interesting'

I have (listed in priority of occurrence)
1- very frequent cursor/mouse pointer plane hangs. usually the GPU 'unlocks' itself within a few seconds.
2- 'infrequent' GPU hangs. usually the GPU 'unlocks' itself after about 30 seconds
3- very infrequent GPU hangs while still able to move the cursor/mouse pointer. usually the GPU 'unlocks' itself after about 30 seconds

Isn't it time that this got escalated to the Intel guys?
It's persisting over several kernel versions


Lenovo W520 machine 4284-4MG, 16GB memory

Comment 52 Gwyn Ciesla 2013-08-30 11:55:57 UTC
*** Bug 901687 has been marked as a duplicate of this bug. ***

Comment 53 Gwyn Ciesla 2013-08-30 12:03:28 UTC
I'm getting this too on my Acer netbook with an i915.  I can attach any logs, configs, etc. fc19, kernel 3.10.9-200 x86_64, xorg-x11-drv-intel 2.21.12-2.

Usually happens while playing a game and often listening to music.  dosbox, foobillard or OpenTTD so far, they freeze, totem's audio loops over a few seconds, I can't get a virtual tty and the machine is unresponsive.

Comment 54 Ravishankar Srinivasan 2013-10-07 08:50:50 UTC
Still happening with latest F19 updates applied on Thinkpad T520

Oct  7 13:57:58 localhost kernel: [10343.338442] [drm:i915_hangcheck_elapsed] *ERROR* stuck on render ring
Oct  7 13:57:58 localhost kernel: [10343.338454] [drm] capturing error event; look for more information in /sys/kernel/debug/dri/0/i915_error_state
Oct  7 13:57:58 localhost kernel: [10343.347326] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x24e3000 ctx 1) at 0x24e31c8

Linux localhost 3.11.3-201.fc19.x86_64 #1 SMP Thu Oct 3 00:47:03 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

xorg-x11-drv-intel-2.21.12-2.fc19.x86_64
mesa-dri-drivers-9.2-1.20130919.fc19.x86_64
mesa-libGL-9.2-1.20130919.fc19.x86_64
mesa-libwayland-egl-9.2-1.20130919.fc19.x86_64
mesa-libglapi-9.2-1.20130919.fc19.i686
mesa-libEGL-9.2-1.20130919.fc19.x86_64
mesa-filesystem-9.2-1.20130919.fc19.x86_64
mesa-libGLU-9.0.0-2.fc19.x86_64
mesa-libGLU-9.0.0-2.fc19.i686
mesa-libEGL-9.2-1.20130919.fc19.i686
mesa-libgbm-9.2-1.20130919.fc19.i686
mesa-libglapi-9.2-1.20130919.fc19.x86_64
mesa-libxatracker-9.2-1.20130919.fc19.x86_64
mesa-libgbm-9.2-1.20130919.fc19.x86_64
mesa-libGL-9.2-1.20130919.fc19.i686

Comment 55 Fedora End Of Life 2013-12-21 15:12:25 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 18'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.

Comment 56 Andre Robatino 2014-07-11 19:15:26 UTC
Happening on F20 with latest BIOS and Fedora updates (including 3.15.4 kernel).

Comment 57 Jan Kurik 2015-07-15 14:56:04 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23

Comment 58 Fedora End Of Life 2016-11-24 10:51:47 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 EOL if it remains open with a Fedora  'version'
of '23'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 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 this bug is closed as described in the policy above.

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.

Comment 59 Fedora End Of Life 2016-12-20 12:31:01 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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