The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* fi-icl-u4: igt@kms_ccs@pipe-b-bad-aux-stride - skip - Test requirement: !(width <= 1024),  FB already has the smallest possible stride, SKIP
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_338/fi-icl-u4/igt@kms_ccs@pipe-b-bad-aux-stride.html

Looks like DP-3 is connected to Pipe B and while listing the supported modes of DP-3, we found:
Modeline "1024x768": 60 65000 1024 1048 1184 1344 768 771 777 806 0x40 0xa
Modeline "800x600": 60 40000 800 840 968 1056 600 601 605 628 0x40 0x5
Modeline "800x600": 56 36000 800 824 896 1024 600 601 603 625 0x40 0x5
Modeline "848x480": 60 33750 848 864 976 1088 480 486 494 517 0x40 0x5
Modeline "640x480": 60 25175 640 656 752 800 480 490 492 525 0x40 0xa

Here the width <= 1024 for the above listed modes and inside IGT there is skip asserted for this condition.

so it might be valid skip according to the developer.

A CI Bug Log filter associated to this bug has been updated:

{- fi-icl-u4: igt@kms_ccs@pipe-b-bad-aux-stride - skip - Test requirement: !(width <= 1024),  FB already has the smallest possible stride, SKIP -}
{+ fi-icl-u2 fi-icl-u4: igt@kms_ccs@pipe-[ab]-bad-aux-stride - skip - Test requirement: !(width <= 1024),  FB already has the smallest possible stride, SKIP +}


  No new failures caught with the new filter

A CI Bug Log filter associated to this bug has been updated:

{- fi-icl-u2 fi-icl-u4: igt@kms_ccs@pipe-[ab]-bad-aux-stride - skip - Test requirement: !(width <= 1024),  FB already has the smallest possible stride, SKIP -}
{+ fi-icl-u2 fi-icl-u4: igt@kms_ccs@pipe-[ab]-bad-aux-stride - skip - Test requirement: !(width <= 1024),  FB already has the smallest possible stride, SKIP +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_348/fi-icl-u2/igt@kms_ccs@pipe-c-bad-aux-stride.html

In a test for a width, we select the minimum of

min(MAX_SPRITE_PLANE_WIDTH, drm_mode->hdisplay)

and we have defined the MAX_SPRITE_WIDTH 

"
/*
 * Limit maximum used sprite plane width so this test will not mistakenly
 * fail on hardware limitations which are not interesting to this test.
 * On this test too wide sprite plane may fail during creation with dmesg
 * comment saying:
 * "Requested display configuration exceeds system watermark limitations"
 */
#define MAX_SPRITE_PLANE_WIDTH 2000
"

As Jyoti mentioned earlier, the test has selected MAX_SPRITE_PLANE_WIDTH is limited to 2000 on purpose in order to avoid possible hw limitations.

Maybe we could try to set the limit to 512 to avoid skips?

(In reply to Mika Kahola from comment #5)
> In a test for a width, we select the minimum of
> 
> min(MAX_SPRITE_PLANE_WIDTH, drm_mode->hdisplay)
> 
> and we have defined the MAX_SPRITE_WIDTH 
> 
> "
> /*
>  * Limit maximum used sprite plane width so this test will not mistakenly
>  * fail on hardware limitations which are not interesting to this test.
>  * On this test too wide sprite plane may fail during creation with dmesg
>  * comment saying:
>  * "Requested display configuration exceeds system watermark limitations"
>  */
> #define MAX_SPRITE_PLANE_WIDTH 2000
> "
> 
> As Jyoti mentioned earlier, the test has selected MAX_SPRITE_PLANE_WIDTH is
> limited to 2000 on purpose in order to avoid possible hw limitations.
> 
> Maybe we could try to set the limit to 512 to avoid skips?

I sent a patch to test with lower MAX_SPRITE_PLANE_WIDTH

https://patchwork.freedesktop.org/series/67396/

This now poassing on ICL systems. Resolving.

Still skipping, reopening the issue.
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_392/fi-icl-u4/igt@kms_ccs@pipe-c-bad-aux-stride.html
IGT-Version: 1.24-gda9abbab6 (x86_64) (Linux: 5.4.0-rc4-g87aff128f9ba-drmtip_392+ x86_64)
Starting subtest: pipe-C-bad-aux-stride
Test requirement not met in function generate_fb, file ../tests/kms_ccs.c:139:
Test requirement: !(width <= 1024)
FB already has the smallest possible stride
Subtest pipe-C-bad-aux-stride: SKIP (0.000s)

From Mika: This is expected skip as the run has pruned out all other modes except 1024x768. The mode width 1024 is is equal to hardcoded stride length limit in the test and therefore a skip. 

Lakshmi, not a bug.

(In reply to Jani Saarinen from comment #9)
> From Mika: This is expected skip as the run has pruned out all other modes
> except 1024x768. The mode width 1024 is is equal to hardcoded stride length
> limit in the test and therefore a skip. 
> 
> Lakshmi, not a bug.

Thanks. Marking this issue as expected.