Bug 106495 - [snb] GPU HANG: ecode 6:0:0x85fffffc in ositorWorkQueue
Summary: [snb] GPU HANG: ecode 6:0:0x85fffffc in ositorWorkQueue
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-12 21:40 UTC by James
Modified: 2019-09-25 19:11 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
sysfs dump (31.72 KB, text/plain)
2018-05-12 21:40 UTC, James
Details

Note You need to log in before you can comment on or make changes to this bug.
Description James 2018-05-12 21:40:17 UTC
Created attachment 139534 [details]
sysfs dump

Watching a video in Totem under Gnome 3 in X. Screen froze for a few seconds, then unfroze. Caught the following in dmesg:


[46336.090639] [drm] GPU HANG: ecode 6:0:0x85fffffc, in ositorWorkQueue [8616], reason: Hang on rcs0, action: reset
[46336.090642] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[46336.090642] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[46336.090643] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[46336.090643] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[46336.090644] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[46336.090698] i915 0000:00:02.0: Resetting chip after gpu hang


I was rendering something with Kdenlive at the time, but I didn't see any excessive heat or anything.
Comment 1 Denis 2018-05-14 14:08:13 UTC
Hello James, could be that it is the same problem?
https://bugs.freedesktop.org/show_bug.cgi?id=100991
From both logs I see that you have the same CPU Gen (SNB). What mesa version do you have?
Also could you provide a bit more info about video? Any video, or resolution of it matters?
Do you have 1 monitor connected/enabled, or two? (laptop + display, for example)?
Comment 2 James 2018-05-14 18:54:16 UTC
xorg-x11-drv-intel-2.99.917-32.20171025.fc28.x86_64
mesa-dri-drivers-18.0.2-1.fc28.x86_64

Only the laptop's built-in screen connected (LVDS), at native resolution (1366x768). I've not tried any other resolution, not have I seen another hangs. I'll try provoking it over the next few days.
Comment 3 GitLab Migration User 2019-09-25 19:11:16 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1724.


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.