Bug 78764

Summary: [ILK/IVB/HSW Bisected]igt/gem_reg_read fails
Product: DRI Reporter: Guo Jinxian <jinxianx.guo>
Component: DRM/IntelAssignee: Daniel Vetter <daniel>
Status: CLOSED FIXED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: high CC: intel-gfx-bugs
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg none

Description Guo Jinxian 2014-05-16 03:41:27 UTC
Created attachment 99132 [details]
dmesg

==System Environment==
--------------------------
Regression: Yes. 
It was igt issue

Non-working platforms: ILK IVB HSW

==kernel==
--------------------------
-nightly: c74cad3c2599b47438b168ca5629fbb00ab63f95 (fails)
-queued: 229b0489aa75a8c51d2f2e124329d3ac326f326d (fails)
    Author: Mika Kuoppala <mika.kuoppala@linux.intel.com>
    Date:   Wed May 14 17:02:17 2014 +0300

    drm/i915: add null render states for gen6, gen7 and gen8

    These are generated with intel-gpu-tools/tools/null_state_gen

    v2: Don't use header file for states (Daniel Vetter)

    v3: Proper URB state size for gen8/GT3 (Damien Lespiau)

    Tested-by: Kristen Carlson Accardi <kristen@linux.intel.com> (v1)
    Tested-by: Oscar Mateo <oscar.mateo@intel.com> (v2)
    Acked-by: Damien Lespiau <damien.lespiau@intel.com>
    Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com>
    Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>


-fixes: 05adaf1f101f25f40f12c29403e6488f0e45f6b6 (fails)
    Author: Jani Nikula <jani.nikula@intel.com>
    Date:   Fri May 9 14:52:34 2014 +0300

    drm/i915/vlv: reset VLV media force wake request register

    Media force wake get hangs the machine when the system is booted without
    displays attached. The assumption is that (at least some versions of)
    the firmware has skipped some initialization in that case.

    Empirical evidence suggests we need to reset the media force wake
    request register in addition to the render one to avoid hangs.

    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=75895
    Reported-by: Imre Deak <imre.deak@intel.com>
    Reported-by: Darren Hart <dvhart@linux.intel.com>
    Tested-by: Darren Hart <dvhart@linux.intel.com>
    Reviewed-by: Mika Kuoppala <mika.kuoppala@intel.com>
    Cc: stable@vger.kernel.org
    Signed-off-by: Jani Nikula <jani.nikula@intel.com>

==Bug detailed description==
-----------------------------
igt(5e83f0444d0fcef2d5996ef12f9cf1593ccd8f78)

igt/gem_reg_read fails

Output:
./gem_reg_read
IGT-Version: 1.6-g62cd793 (x86_64) (Linux: 3.15.0-rc3_drm-intel-nightly_c74cad_20140515+ x86_64)
Test assertion failure function __real_main55, file gem_reg_read.c:76:
Last errno: 22, Invalid argument
Failed assertion: ret != 0 && errno == ENOENT

==Reproduce steps==
---------------------------- 
1. ./gem_reg_read


==Bisect results==
----------------------------
Bisect shows: 0b7ce4ac2929ea56dfde508d551163a5304c66d8 is the first bad commit

commit 0b7ce4ac2929ea56dfde508d551163a5304c66d8
Author:     Daniel Vetter <daniel.vetter@ffwll.ch>
AuthorDate: Wed May 14 09:56:53 2014 +0200
Commit:     Daniel Vetter <daniel.vetter@ffwll.ch>
CommitDate: Wed May 14 09:56:53 2014 +0200

    tests: Use igt macros more

    Often just folding together of the common if (cond) printf;
    abort|igt_skip|igt_fail; pattern. But in a few cases I've ripped out
    more since the igt macros will already print the condition and errno.

    A few tests where more work (like ripping out return codes en masse)
    is needed left as-is.

    Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Comment 1 Daniel Vetter 2014-05-16 20:55:46 UTC
commit 943511a3ab53df1db5e631bface63bdae663c4c8
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Thu May 15 10:03:11 2014 +0200

    tests/gem_reg_read: Fix errno check
Comment 2 Guo Jinxian 2014-05-19 06:11:26 UTC
Test on latest igt(252d1151a809683b0f6ed2c546358b7375a27f18), This bug had fixed. Thanks.
Comment 3 Jari Tahvanainen 2017-09-04 10:21:51 UTC
Closing old verified+fixed.

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.