[igt-dev] [PATCH i-g-t v2] tests/kms_concurrent: Move bandwidth calculation to igt_fixture

[Kahola, Mika]

-----Original Message-----
From: Latvala, Petri <petri.latvala at intel.com> 
Sent: Monday, March 30, 2020 12:08 PM
To: Kahola, Mika <mika.kahola at intel.com>
Cc: igt-dev at lists.freedesktop.org; juhapekka.heikkila at gmail.com; Lisovskiy, Stanislav <stanislav.lisovskiy at intel.com>
Subject: Re: [PATCH i-g-t v2] tests/kms_concurrent: Move bandwidth calculation to igt_fixture

On Mon, Mar 30, 2020 at 11:17:07AM +0300, Mika Kahola wrote:
> The commit 153b34b5353df8c18a87d ("tests/kms_concurrent:
> Test maximum number of planes supported by the platform") caused 
> regression on HSW pipe B testing such as.
> 
> IGT-Version: 1.25-gfd8248084 (x86_64) (Linux: 
> 5.6.0-rc7-CI-CI_DRM_8194+ x86_64) Starting subtest: pipe-B Testing 
> resolution with connector VGA-1 using pipe B with seed 1585245074 
> child 0 died with signal 11, Segmentation fault Subtest pipe-B: FAIL 
> (0.330s)

What was the crash reason? Why does doing this in fixture help?

I noticed that pipe B was failing with other platforms as well, not just with HSW. Bandwidth calculation within fixture fixed the other platforms that was failing as well as my local HSW machine. I think it is unnecessary to calculate bandwidth for older platforms. We have seen these issues only with gen11+.
 


--
Petri Latvala