Bug 95533 - [SNB] GPU HANG, firefox webgl massive usage, using onshape service (online CAD)
Summary: [SNB] GPU HANG, firefox webgl massive usage, using onshape service (online CAD)
Status: RESOLVED WORKSFORME
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: 10.1
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-23 06:23 UTC by ski
Modified: 2017-03-22 02:17 UTC (History)
1 user (show)

See Also:
i915 platform: SNB
i915 features: GPU hang


Attachments
output of /sys/class/drm/card0/error, and list of installed packages. (2.90 MB, text/plain)
2016-05-23 06:23 UTC, ski
Details
dmesg (61.14 KB, text/plain)
2016-05-23 06:28 UTC, ski
Details
drmdump (276.84 KB, application/x-bzip)
2016-05-23 06:28 UTC, ski
Details
output of dpkg -l (64.38 KB, application/x-bzip)
2016-05-23 06:30 UTC, ski
Details
outptu of xrandr --verbose (4.38 KB, text/plain)
2016-05-23 06:31 UTC, ski
Details
output ot intel_reg_dumper (14.30 KB, text/plain)
2016-05-23 06:32 UTC, ski
Details
vbios.dump (38.12 KB, application/x-bzip)
2016-05-23 06:34 UTC, ski
Details
Xorg.0.log (21.22 KB, text/x-log)
2016-05-23 06:35 UTC, ski
Details
intel reg dump 2 (14.30 KB, text/plain)
2016-05-23 07:03 UTC, ski
Details
Xorg.0.log 2 (21.74 KB, application/x-trash)
2016-05-23 07:04 UTC, ski
Details
drm crash dump 2 (276.61 KB, application/x-bzip)
2016-05-23 07:05 UTC, ski
Details
dmesg 2 (121.74 KB, text/plain)
2016-05-23 07:06 UTC, ski
Details
gpu crash dump (1.71 MB, text/plain)
2016-11-07 11:46 UTC, ski
Details

Description ski 2016-05-23 06:23:02 UTC
Created attachment 123977 [details]
output of /sys/class/drm/card0/error, and list of installed packages.

playing with online CAD service onshape, making viewport rotation, scales, moving, got "[drm] stuck on render ring".
problem repeteable.

cad document is public:
https://cad.onshape.com/documents/573ea6d2e4b05d0d35a8fef8/w/de5278f320951921495e09cb/e/dbe8e6ecd88538a1387e34f0

dmesg:
[ 1938.185262] [drm] stuck on render ring
[ 1938.185271] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 1938.185272] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 1938.185273] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 1938.185274] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 1938.185275] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 1938.188286] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x2e200000 ctx 8) at 0x2e200d50
[ 1945.195027] [drm] stuck on render ring
[ 1945.195163] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x2d120000 ctx 1) at 0x2d1202c0

attached: output of drm dump, and starting at line 115408 list of installed packages.
Comment 1 ski 2016-05-23 06:28:04 UTC
Created attachment 123978 [details]
dmesg
Comment 2 ski 2016-05-23 06:28:55 UTC
Created attachment 123979 [details]
drmdump
Comment 3 ski 2016-05-23 06:30:01 UTC
Created attachment 123980 [details]
output of dpkg -l
Comment 4 ski 2016-05-23 06:31:00 UTC
Created attachment 123981 [details]
outptu of xrandr --verbose
Comment 5 ski 2016-05-23 06:32:52 UTC
Created attachment 123982 [details]
output ot intel_reg_dumper
Comment 6 ski 2016-05-23 06:34:15 UTC
Created attachment 123983 [details]
vbios.dump
Comment 7 ski 2016-05-23 06:35:50 UTC
Created attachment 123984 [details]
Xorg.0.log
Comment 8 ski 2016-05-23 06:39:02 UTC
arch: x86_64
kernel: 3.13.0-61-generic
Ubuntu 14.04.4 LTS
mb: gigabyte h61m-s1
VGA connection
Comment 9 ski 2016-05-23 07:02:41 UTC
Repeated with drm.debug=0xe, not X restarted.
folowed attachments for this repeat.
Comment 10 ski 2016-05-23 07:03:41 UTC
Created attachment 123985 [details]
intel reg dump 2
Comment 11 ski 2016-05-23 07:04:05 UTC
Created attachment 123986 [details]
Xorg.0.log 2
Comment 12 ski 2016-05-23 07:05:36 UTC
Created attachment 123987 [details]
drm crash dump 2
Comment 13 ski 2016-05-23 07:06:17 UTC
Created attachment 123988 [details]
dmesg 2
Comment 14 ski 2016-05-23 07:07:36 UTC
(In reply to ski from comment #9)
> Repeated with drm.debug=0xe, not X restarted.
> folowed attachments for this repeat.

NOW x restarted.
Comment 15 yann 2016-09-01 13:30:06 UTC
Assigning to Mesa product (please let me know if I am mistaken with this GPU Hang).

From this error dump, hung is happening in render ring batch with active head at 0x1bc5bd50, with 0x7a000004 (PIPE_CONTROL) as IPEHR (same case in both gpu dump)

Batch extract (around 0x1bc5bd50):

0x1bc5bd2c:      0x78021302: 3DSTATE_SAMPLER_STATE_POINTERS: VS mod 1, GS mod 1, PS mod 1
0x1bc5bd30:      0x000076c0:    VS sampler state
0x1bc5bd34:      0x00000000:    GS sampler state
0x1bc5bd38:      0x00007540:    WM sampler state
0x1bc5bd3c:      0x7a000003: PIPE_CONTROL
0x1bc5bd40:      0x00100002:    no write, cs stall, stall at scoreboard,
0x1bc5bd44:      0x00000000:    destination address
0x1bc5bd48:      0x00000000:    immediate dword low
0x1bc5bd4c:      0x00000000:    immediate dword high
0x1bc5bd50:      0x7a000003: PIPE_CONTROL
0x1bc5bd54:      0x00004000:    qword write,
0x1bc5bd58:      0x03112004:    destination address
0x1bc5bd5c:      0x00000000:    immediate dword low
0x1bc5bd60:      0x00000000:    immediate dword high
0x1bc5bd64:      0x78150003: 3DSTATE_CONSTANT_VS_STATE
0x1bc5bd68:      0x00000000:    dword 1
0x1bc5bd6c:      0x00000000:    dword 2
0x1bc5bd70:      0x00000000:    dword 3
0x1bc5bd74:      0x00000000:    dword 4
Comment 16 yann 2016-11-04 15:12:32 UTC
Please test a new version of Mesa (12 or 13) and mark as REOPENED
if you can reproduce and RESOLVED/* if you cannot reproduce.
Comment 17 ski 2016-11-07 10:29:21 UTC
mesa 12 (ubuntu 16.10). So far so good.
Comment 18 ski 2016-11-07 11:46:32 UTC
Created attachment 127813 [details]
gpu crash dump

again, after long idle time.
Comment 19 Matt Turner 2017-03-22 02:17:21 UTC
Sorry no one ever investigated your bug.

The good news is that everything seems to be working on kernel 4.9.5 and mesa-13.0.3.

Please reopen if you can still reproduce with Mesa 17.0.


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.