[igt-dev] ✗ Fi.CI.BAT: failure for Change gem_sync to no-reloc

[Vudum, Lakshminarayana]

Filed following bugs for the regression and re-reported.
https://gitlab.freedesktop.org/drm/intel/-/issues/4406
igt at kms_force_connector_basic@.* -dmesg-fail/crash *ERROR* No EDID firmware found on connector: .* ,forcing to OFF!, *ERROR* dc_sink is NULL!

https://gitlab.freedesktop.org/drm/intel/-/issues/4405
igt at kms_addfb_basic@.* - fail - Failed assertion: igt_ioctl.*, error: 0 != -1

https://gitlab.freedesktop.org/drm/intel/-/issues/4404
igt at core_hotunplug@unbind-rebind - incomplete - RIP: 0010:smu7_powergate_uvd

Lakshmi.
-----Original Message-----
From: Kempczynski, Zbigniew <zbigniew.kempczynski at intel.com> 
Sent: Thursday, October 28, 2021 10:02 PM
To: igt-dev at lists.freedesktop.org
Cc: Vudum, Lakshminarayana <lakshminarayana.vudum at intel.com>
Subject: Re: ✗ Fi.CI.BAT: failure for Change gem_sync to no-reloc

On Thu, Oct 28, 2021 at 09:11:34PM +0000, Patchwork wrote:
>    Patch Details
> 
>    Series:  Change gem_sync to no-reloc                                    
>    URL:     https://patchwork.freedesktop.org/series/96401/                
>    State:   failure                                                        
>    Details: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6362/index.html 
> 
>               CI Bug Log - changes from CI_DRM_10809 -> IGTPW_6362
> 
> Summary
> 
>    FAILURE
> 
>    Serious unknown changes coming with IGTPW_6362 absolutely need to be
>    verified manually.
> 
>    If you think the reported changes have nothing to do with the changes
>    introduced in IGTPW_6362, please notify your bug team to allow them
>    to document this new failure mode, which will reduce false positives in
>    CI.
> 
>    External URL:
>    https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6362/index.html
> 
> Participating hosts (36 -> 34)
> 
>    Additional (1): fi-pnv-d510
>    Missing (3): bat-adlp-4 bat-dg1-6 bat-dg1-5
> 
> Possible new issues
> 
>    Here are the unknown changes that may have been introduced in IGTPW_6362:
> 
>   IGT changes
> 
>     Possible regressions
> 
>      * igt at core_hotunplug@unbind-rebind:
> 
>           * fi-kbl-8809g: PASS -> INCOMPLETE
>      * igt at kms_addfb_basic@too-high:
> 
>           * fi-kbl-8809g: PASS -> FAIL +2 similar issues
>      * igt at kms_force_connector_basic@force-connector-state:
> 
>           * fi-kbl-8809g: PASS -> DMESG-FAIL
>      * igt at kms_force_connector_basic@force-edid:
> 
>           * fi-kbl-8809g: PASS -> CRASH

It seems problem occurs on kbl and is not related to test I've changed.

--
Zbigniew


> 
> Known issues
> 
>    Here are the changes found in IGTPW_6362 that come from known issues:
> 
>   IGT changes
> 
>     Issues hit
> 
>      * igt at kms_addfb_basic@unused-modifier:
> 
>           * fi-kbl-8809g: PASS -> SKIP (fdo#109271) +18 similar issues
>      * igt at prime_vgem@basic-userptr:
> 
>           * fi-pnv-d510: NOTRUN -> SKIP (fdo#109271) +53 similar issues
>      * igt at runner@aborted:
> 
>           * fi-kbl-8809g: NOTRUN -> FAIL (i915#2283 / i915#2426 / i915#3363 /
>             i915#4312)
> 
>     Possible fixes
> 
>      * igt at gem_exec_suspend@basic-s3:
> 
>           * fi-tgl-1115g4: FAIL (i915#1888) -> PASS
>      * igt at kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-b:
> 
>           * fi-kbl-8809g: SKIP (fdo#109271) -> PASS +15 similar issues
>      * igt at kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
> 
>           * fi-kbl-8809g: SKIP (fdo#109271 / i915#533) -> PASS
> 
> Build changes
> 
>      * CI: CI-20190529 -> None
>      * IGT: IGT_6264 -> IGTPW_6362
> 
>    CI-20190529: 20190529
>    CI_DRM_10809: 9959c5de92d04f2336d749a5a331799aa41cfb1f @
>    git://anongit.freedesktop.org/gfx-ci/linux
>    IGTPW_6362: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6362/index.html
>    IGT_6264: 3458490c14afe3cb8aa873fa9e520e1c815ea068 @
>    https://gitlab.freedesktop.org/drm/igt-gpu-tools.git