Bug 89000 - [BDW ppgtt Bisected]igt/gem_evict_everything/major-hang causes system hang
Summary: [BDW ppgtt Bisected]igt/gem_evict_everything/major-hang causes system hang
Status: CLOSED DUPLICATE of bug 88652
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: high critical
Assignee: Nick Hoath
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-06 03:13 UTC by lu hua
Modified: 2017-08-14 08:34 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description lu hua 2015-02-06 03:13:29 UTC
==System Environment==
--------------------------
Regression: yes
good commit: 1d83d957e621f160dfe0f08194e9c2fdd5fa7f3e
bad commit: 93180785d44e3d417099e293b9ff6eeb4fd20aa2

no-working platforms: BDW

==kernel==
--------------------------
drm-intel-nightly/9583cb470cd82997b5f23d4acab852563f5c0047
commit 9583cb470cd82997b5f23d4acab852563f5c0047
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Wed Feb 4 15:22:12 2015 +0100

    drm-intel-nightly: 2015y-02m-04d-14h-21m-52s UTC integration manifest

==Bug detailed description==
-----------------------------
It causes system hang, add i915.enable_ppgtt=0, it works well. bug 88652 tracks BSW, report this bug to track BDW.

output:
IGT-Version: 1.9-gbef692d (x86_64) (Linux: 3.19.0-rc7_drm-intel-nightly_75ce8a_20150206+ x86_64)
Test requirement not met in function intel_require_memory, file intel_os.c:244:
Test requirement: !(total <= required)
Estimated that we need 12884905984 bytes for the test, but only have 3915382784 bytes available (RAM)
Subtest major-hang: SKIP (0.012s)

==Reproduce steps==
---------------------------- 
1. ./gem_evict_everything --run-subtest major-hang
Comment 1 lu hua 2015-02-06 03:15:15 UTC
> ==Bug detailed description==
> -----------------------------
> It causes system hang, add i915.enable_ppgtt=0, it works well. bug 88652

Add i915.enable_execlists=0, it works well.
Comment 2 lu hua 2015-02-09 06:26:26 UTC
add  i915.enable_ppgtt=0, It works well.
Comment 3 lu hua 2015-02-09 07:02:41 UTC
Bisect shows: 6d3d8274bc45de4babb62d64562d92af984dd238 is the first bad commit.
commit 6d3d8274bc45de4babb62d64562d92af984dd238
Author:     Nick Hoath <nicholas.hoath@intel.com>
AuthorDate: Thu Jan 15 13:10:39 2015 +0000
Commit:     Daniel Vetter <daniel.vetter@ffwll.ch>
CommitDate: Tue Jan 27 09:50:53 2015 +0100

    drm/i915: Subsume intel_ctx_submit_request in to drm_i915_gem_request

    Move all remaining elements that were unique to execlists queue items
    in to the associated request.

    Issue: VIZ-4274

    v2: Rebase. Fixed issue of overzealous freeing of request.
    v3: Removed re-addition of cleanup work queue (found by Daniel Vetter)
    v4: Rebase.
    v5: Actual removal of intel_ctx_submit_request. Update both tail and postfix
    pointer in __i915_add_request (found by Thomas Daniel)
    v6: Removed unrelated changes

    Signed-off-by: Nick Hoath <nicholas.hoath@intel.com>
    Reviewed-by: Thomas Daniel <thomas.daniel@intel.com>
    [danvet: Reformat comment with strange linebreaks.]
    Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Comment 4 Jani Nikula 2015-02-10 08:18:48 UTC

*** This bug has been marked as a duplicate of bug 88652 ***
Comment 5 lu hua 2015-03-09 08:21:37 UTC
Fixed.
root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# ./gem_evict_everything --run-subtest major-hang
IGT-Version: 1.9-g5e4fc0c (x86_64) (Linux: 4.0.0-rc2_drm-intel-nightly_c2f6e5_20150307+ x86_64)
Test requirement not met in function intel_require_memory, file intel_os.c:244:
Test requirement: !(total <= required)
Estimated that we need 12884905984 bytes for the test, but only have 3914334208 bytes available (RAM)
Subtest major-hang: SKIP (0.013s)
Received signal SIGTERM.
Received signal SIGTERM.
root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# echo $?
77
Comment 6 Jari Tahvanainen 2017-08-14 08:34:13 UTC
Moving old bug from Verified to Closed.


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.