Bug 72110

Summary: [BDW]igt/gem_ringfill/render causes system hangs
Product: DRI Reporter: Guo Jinxian <jinxianx.guo>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED NOTABUG QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: critical    
Priority: high CC: intel-gfx-bugs
Version: XOrg git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Bug Depends on: 72106    
Bug Blocks:    

Description Guo Jinxian 2013-11-28 09:34:19 UTC 
system 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_ringfill/render causes system hangs, unable to fetch dmesg

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



Steps:
---------------------------
./gem_ringfill --run-subtest render
Comment 1 Chris Wilson 2013-11-29 14:11:54 UTC 
The critical one is gem_render_copy. That is the basic test for the gen8_render_copy func and until that works correctly and passes, there is little point investigating the tests built upon it.
Comment 2 Ben Widawsky 2013-12-06 00:35:23 UTC 
As Chris said, it's not a specific test failure at this point. It's rendercpy.
Comment 3 Guo Jinxian 2013-12-10 06:31:04 UTC 
The test had disabled.

[root@x-bdw01 tests]# ./gem_ringfill --run-subtest render
Temporarily disabled
Test requirement not met in function __real_main203, file gem_ringfill.c:223:
Test requirement: (!(copy))
Subtest render: SKIP
Comment 4 Jari Tahvanainen 2017-08-14 10:35:55 UTC 
Closing old Verified+Notabug.

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.