Bug 88379 - [ilk 3.16] GPU HANG: ecode 0:0xfdffffdd, reason: Ring hung, action: reset
Summary: [ilk 3.16] GPU HANG: ecode 0:0xfdffffdd, reason: Ring hung, action: reset
Status: CLOSED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-14 00:55 UTC by Mikhail Morfikov
Modified: 2017-07-24 22:49 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
content of /sys/class/drm/card0/error (1.49 MB, text/plain)
2015-01-14 00:55 UTC, Mikhail Morfikov
no flags Details

Description Mikhail Morfikov 2015-01-14 00:55:06 UTC
Created attachment 112185 [details]
content of /sys/class/drm/card0/error

According to the instruction in syslog, I'm sending the content of /sys/class/drm/card0/error .

I'm using debian sid.
Comment 1 Chris Wilson 2015-01-14 09:19:54 UTC
Death on a MI_FLUSH after a pageflip + seqno write. Unusual.
Comment 2 Rodrigo Vivi 2015-01-14 22:56:45 UTC
I've seem something similar yesterday... I guess on gen2 (#75957)
Comment 3 Mikhail Morfikov 2015-01-24 21:40:20 UTC
I think I know what causes this problem -- I had the following kernel parameters set in extlinux:

i915.enable_rc6=7 i915.lvds_downclock=1 i915.semaphores=1 i915.fastboot=1

I removed them from the kernel line because the problem started to occur 5-10 times a day.

I don't know if one of the parameters is to blame or all. I just used them for power save mode, at least that's what they said on the internet.

Anyway, now I don't get the error.
Comment 4 Jani Nikula 2015-01-26 09:22:21 UTC
Mikhail, we consider changing i915.enable_rc6 or i915.semaphores from their platform specific defaults unsafe. I'm closing the bug, if you can reproduce without the parameters, please do reopen. Thanks.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.