From: "Kahola, Mika" <mika.kahola@intel.com>
To: "Latvala, Petri" <petri.latvala@intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t v2] tests/kms_concurrent: Move bandwidth calculation to igt_fixture
Date: Mon, 30 Mar 2020 10:06:40 +0000 [thread overview]
Message-ID: <b4b323c452084747aa4a0b52e985662c@intel.com> (raw)
In-Reply-To: <20200330090752.GC9497@platvala-desk.ger.corp.intel.com>
-----Original Message-----
From: Latvala, Petri <petri.latvala@intel.com>
Sent: Monday, March 30, 2020 12:08 PM
To: Kahola, Mika <mika.kahola@intel.com>
Cc: igt-dev@lists.freedesktop.org; juhapekka.heikkila@gmail.com; Lisovskiy, Stanislav <stanislav.lisovskiy@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
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-03-30 10:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 8:17 [igt-dev] [PATCH i-g-t v2] tests/kms_concurrent: Move bandwidth calculation to igt_fixture Mika Kahola
2020-03-30 8:52 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_concurrent: Move bandwidth calculation to igt_fixture (rev3) Patchwork
2020-03-30 9:07 ` [igt-dev] [PATCH i-g-t v2] tests/kms_concurrent: Move bandwidth calculation to igt_fixture Petri Latvala
2020-03-30 10:06 ` Kahola, Mika [this message]
2020-03-30 11:40 ` Petri Latvala
2020-03-30 12:11 ` Kahola, Mika
2020-03-30 9:59 ` [igt-dev] ✗ Fi.CI.IGT: failure for tests/kms_concurrent: Move bandwidth calculation to igt_fixture (rev3) Patchwork
2020-03-30 10:29 ` Kahola, Mika
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b4b323c452084747aa4a0b52e985662c@intel.com \
--to=mika.kahola@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=petri.latvala@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.