Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 480930 - sys-kernel/gentoo-sources-3.10.2 drm:i915_hangcheck_hung
Summary: sys-kernel/gentoo-sources-3.10.2 drm:i915_hangcheck_hung
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers
URL: https://bugs.freedesktop.org/show_bug...
Whiteboard: watch-linux-bugzilla
Keywords: UPSTREAM
Depends on:
Blocks:
 
Reported: 2013-08-13 22:31 UTC by januszmk
Modified: 2013-10-14 17:55 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
dmesg (dmesg,24.80 KB, text/plain)
2013-08-13 22:32 UTC, januszmk
Details
.config (kernel-config,96.25 KB, text/plain)
2013-08-13 22:32 UTC, januszmk
Details
/sys/kernel/debug/dri/0/i915_error_state (i915_error_state.tgz,320.42 KB, application/x-compressed-tar)
2013-08-13 22:34 UTC, januszmk
Details

Note You need to log in before you can comment on or make changes to this bug.
Description januszmk 2013-08-13 22:31:08 UTC
sometimes my screen freeze, I am getting messages like: [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung (but not always)
GPU: intel hd3000 on cpu i5 2500k
mainboard: gigabyte ga-z68m-d2h
current mesa version: 9.1.6
current kernel version: linux-3.10.2-gentoo
current xorg drivers: 2.21.14

I started to have this problem since kernel 3.8. 
I am attaching dmesg output, .config and i915_error_state.
Comment 1 januszmk 2013-08-13 22:32:06 UTC
Created attachment 355906 [details]
dmesg
Comment 2 januszmk 2013-08-13 22:32:30 UTC
Created attachment 355908 [details]
.config
Comment 3 januszmk 2013-08-13 22:34:32 UTC
Created attachment 355910 [details]
/sys/kernel/debug/dri/0/i915_error_state
Comment 4 Chí-Thanh Christopher Nguyễn gentoo-dev 2013-08-13 23:02:24 UTC
See if the problem still exists with latest 3.10.6 kernel.
If yes, try adding i915.i915_enable_rc6=0 kernel parameter.
Comment 5 januszmk 2013-08-15 12:34:20 UTC
seems that adding 915.i915_enable_rc6=0 solved the problem, if it will occur again, I will report that
Comment 6 Chí-Thanh Christopher Nguyễn gentoo-dev 2013-08-15 13:07:36 UTC
If passing i915.i915_enable_rc6=0 kernel parameter to the latest kernel release made the problem go away, please report this upstream at https://bugs.freedesktop.org/ so the issue can be addressed in the default configuration (by adding a quirk for your hardware or through other means).

If you create an upstream bug report, please provide the link here.
Comment 7 januszmk 2013-08-15 16:46:20 UTC
ehh, I got another error, this time I got i915_hangcheck_hung + additionally "[drm:kick_ring] *ERROR* Kicking stuck semaphore on render ring"
Comment 8 Tom Wijsman (TomWij) (RETIRED) gentoo-dev 2013-09-03 19:45:57 UTC
(In reply to januszmk from comment #7)
> ehh, I got another error, this time I got i915_hangcheck_hung + additionally
> "[drm:kick_ring] *ERROR* Kicking stuck semaphore on render ring"

Did you try what was asked in Comment #6; though, please report this upstream anyway because semaphores in graphics drivers we have no experience in are a bit to complex for us to deal with. Please leave us a link behind that points to the upstream bug, thank you in advance.
Comment 9 januszmk 2013-09-05 23:17:38 UTC
(In reply to Tom Wijsman (TomWij) from comment #8)
> (In reply to januszmk from comment #7)
> > ehh, I got another error, this time I got i915_hangcheck_hung + additionally
> > "[drm:kick_ring] *ERROR* Kicking stuck semaphore on render ring"
> 
> Did you try what was asked in Comment #6; though, please report this
> upstream anyway because semaphores in graphics drivers we have no experience
> in are a bit to complex for us to deal with. Please leave us a link behind
> that points to the upstream bug, thank you in advance.

Yes, I tried.
I found upstream report bug, https://bugs.freedesktop.org/show_bug.cgi?id=54226
in kernel 3.11 I thinks it's fixed, because I don't have it anymore, but I do have something like this:

[22221.843000] [drm:i915_hangcheck_elapsed] *ERROR* stuck on render ring
[22221.843483] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x4dfb5000 ctx 1) at 0x4dfb5518
and in comments there are saying that is a blorp (mesa/i965) bug
Comment 10 Tom Wijsman (TomWij) (RETIRED) gentoo-dev 2013-10-14 17:26:12 UTC
(In reply to januszmk from comment #9)
> I found upstream report bug,
> https://bugs.freedesktop.org/show_bug.cgi?id=54226
> in kernel 3.11 I thinks it's fixed, because I don't have it anymore, but I
> do have something like this:
> 
> [22221.843000] [drm:i915_hangcheck_elapsed] *ERROR* stuck on render ring
> [22221.843483] [drm:i915_set_reset_status] *ERROR* render ring hung inside
> bo (0x4dfb5000 ctx 1) at 0x4dfb5518
> and in comments there are saying that is a blorp (mesa/i965) bug

Someone mentioned "Unlikey that this is the same gpu hang. Please file a new bug report and attach the error state.", thus could you file a new bug upstream?

If you do, please provide us an URL to the upstream bug report.

Good luck and thank you in advance.
Comment 11 januszmk 2013-10-14 17:42:58 UTC
(In reply to Tom Wijsman (TomWij) from comment #10)
> (In reply to januszmk from comment #9)
> > I found upstream report bug,
> > https://bugs.freedesktop.org/show_bug.cgi?id=54226
> > in kernel 3.11 I thinks it's fixed, because I don't have it anymore, but I
> > do have something like this:
> > 
> > [22221.843000] [drm:i915_hangcheck_elapsed] *ERROR* stuck on render ring
> > [22221.843483] [drm:i915_set_reset_status] *ERROR* render ring hung inside
> > bo (0x4dfb5000 ctx 1) at 0x4dfb5518
> > and in comments there are saying that is a blorp (mesa/i965) bug
> 
> Someone mentioned "Unlikey that this is the same gpu hang. Please file a new
> bug report and attach the error state.", thus could you file a new bug
> upstream?
> 
> If you do, please provide us an URL to the upstream bug report.
> 
> Good luck and thank you in advance.

Yes, this is another bug and I filed new bug report: https://bugs.freedesktop.org/show_bug.cgi?id=70151