Summary: | [SNB] GPU HANG, firefox webgl massive usage, using onshape service (online CAD) | ||
---|---|---|---|
Product: | Mesa | Reporter: | ski <ug7vekjhu2> |
Component: | Drivers/DRI/i965 | Assignee: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Status: | RESOLVED WORKSFORME | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Severity: | normal | ||
Priority: | medium | CC: | intel-gfx-bugs |
Version: | 10.1 | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | SNB | i915 features: | GPU hang |
Attachments: |
output of /sys/class/drm/card0/error, and list of installed packages.
dmesg drmdump output of dpkg -l outptu of xrandr --verbose output ot intel_reg_dumper vbios.dump Xorg.0.log intel reg dump 2 Xorg.0.log 2 drm crash dump 2 dmesg 2 gpu crash dump |
Description
ski
2016-05-23 06:23:02 UTC
Created attachment 123978 [details]
dmesg
Created attachment 123979 [details]
drmdump
Created attachment 123980 [details]
output of dpkg -l
Created attachment 123981 [details]
outptu of xrandr --verbose
Created attachment 123982 [details]
output ot intel_reg_dumper
Created attachment 123983 [details]
vbios.dump
Created attachment 123984 [details]
Xorg.0.log
arch: x86_64 kernel: 3.13.0-61-generic Ubuntu 14.04.4 LTS mb: gigabyte h61m-s1 VGA connection Repeated with drm.debug=0xe, not X restarted. folowed attachments for this repeat. Created attachment 123985 [details]
intel reg dump 2
Created attachment 123986 [details]
Xorg.0.log 2
Created attachment 123987 [details]
drm crash dump 2
Created attachment 123988 [details]
dmesg 2
(In reply to ski from comment #9) > Repeated with drm.debug=0xe, not X restarted. > folowed attachments for this repeat. NOW x restarted. 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 Please test a new version of Mesa (12 or 13) and mark as REOPENED if you can reproduce and RESOLVED/* if you cannot reproduce. mesa 12 (ubuntu 16.10). So far so good. Created attachment 127813 [details]
gpu crash dump
again, after long idle time.
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.