Bug 72107 - [BDW]igt/gem_render_linear_blits causes gpu hangs
Summary: [BDW]igt/gem_render_linear_blits causes gpu hangs
Status: CLOSED NOTABUG
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: high major
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on: 72106
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-28 09:25 UTC by Guo Jinxian
Modified: 2017-10-06 14:41 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg (92.92 KB, text/plain)
2013-11-28 09:25 UTC, Guo Jinxian
no flags Details
error state (2.84 MB, text/plain)
2013-11-29 03:22 UTC, Guo Jinxian
no flags Details

Description Guo Jinxian 2013-11-28 09:25:10 UTC
Created attachment 89951 [details]
dmesg

ystem Environment:
--------------------------
Platform: Broadwell
kernel   (drm-intel-nexe-queued)8b4f49e03901e82898540bd1189333edf9588d74
Some additional commit info:
Author: Jesse Barnes <jbarnes@virtuousgeek.org>
Date:   Mon Nov 25 15:51:16 2013 -0800

    drm/i915: split fb allocation and initialization v2

    If we use a stolen buffer, our probe callback shouldn't allocate a new
    buffer; we should re-use the one from the BIOS instead if possible.

    v2: fix locking (Jesse)

Bug detailed description:
-----------------------------
Igt/gem_render_linear_blits causes gpu hangs.

This is the first time to run igt test on Broadwell.

[  163.658036] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[  163.658129] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[  163.658234] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[  163.658303] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[  163.658378] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.

Steps:
---------------------------
./gem_render_linear_blits
Comment 1 Daniel Vetter 2013-11-28 13:16:49 UTC
Again, we need the gpu error state.
Comment 2 Guo Jinxian 2013-11-29 03:22:31 UTC
Created attachment 89970 [details]
error state

Attached error state.
Comment 3 Ben Widawsky 2013-12-06 00:41:47 UTC
I cannot reproduce this. Can you confirm it still exists for you? Please run the test alone to make sure we don't hit the GPU reset issues.

bwidawsk@vandamme ~/intel-gfx/intel-gpu-tools (master)$ sudo ./tests/gem_linear_blits
Using 3072 1MiB buffers
Verifying initialisation...
Cyclic blits, forward...
Cyclic blits, backward...
Random blits...
Subtest normal: SUCCESS
Verifying initialisation...
Cyclic blits, forward...
Cyclic blits, backward...
Random blits...
Subtest interruptible: SUCCESS
Comment 4 Guo Jinxian 2013-12-06 03:25:12 UTC
Retested on latest IGT(commit 8ac7b93b218af1544988331cd68c69ba4102c29f),this bug still cause gpu gangs.


Here it the info print in console:

[root@x-bdw01 tests]# ./gem_render_linear_blits
Using 3072 1MiB buffers
Verifying initialisation...
Cyclic blits, forward...
Test assertion failure function igt_drop_caches_set, file igt_debugfs.c:338:
Failed assertion: nbytes == strlen(data) + 1
Subtest forked-interruptible-faulting-reloc-thrashing: FAIL
Test assertion failure function igt_drop_caches_set, file igt_debugfs.c:338:
Failed assertion: nbytes == strlen(data) + 1
Subtest forked-faulting-reloc-thrashing: FAIL
Comment 5 Guo Jinxian 2013-12-10 06:37:27 UTC
Update test result on IGT commit(3c5423b9a74fe056cae1fce41fd3ad16584e9c8d), the test is disabled

[root@x-bdw01 tests]# ./gem_render_linear_blits
Temporarily disabled
no render-copy function, doing nothing
Comment 6 Ben Widawsky 2013-12-10 07:16:12 UTC
disabled by rendercopy for now
Comment 7 Guo Jinxian 2013-12-10 07:22:57 UTC
The test is disabled on IGT commit(3c5423b9a74fe056cae1fce41fd3ad16584e9c8d)
Comment 8 Elizabeth 2017-10-06 14:41:47 UTC
Closing old verified.


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.