Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Vudum, Lakshminarayana" <lakshminarayana.vudum@intel.com>
To: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>,
	"Latvala, Petri" <petri.latvala@intel.com>
Cc: Stylon Wang <stylon.wang@amd.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
	"nicholas.choi@amd.com" <nicholas.choi@amd.com>
Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_hdr: Fix failure to read output_bpc on AMD hardware
Date: Mon, 4 Oct 2021 15:42:28 +0000	[thread overview]
Message-ID: <7c206aba165a465aa14b465c72b6802c@intel.com> (raw)
In-Reply-To: <20211004141835.uzqrsamqgdstee2q@outlook.office365.com>

Filed https://gitlab.freedesktop.org/drm/intel/-/issues/4262 and re-reported.
igt@kms_lease@invalid-create-leases - fail - Failed assertion: create_lease(data->master.fd, &mcl) == -22

Lakshmi.

-----Original Message-----
From: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com> 
Sent: Monday, October 4, 2021 7:19 AM
To: Latvala, Petri <petri.latvala@intel.com>; Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>
Cc: Stylon Wang <stylon.wang@amd.com>; igt-dev@lists.freedesktop.org; nicholas.choi@amd.com
Subject: Re: [PATCH i-g-t] tests/kms_hdr: Fix failure to read output_bpc on AMD hardware

On 10/04, Petri Latvala wrote:
> On Sat, Oct 02, 2021 at 11:15:11AM -0400, Rodrigo Siqueira wrote:
> > Hi Lakshminarayana and Petri,
> > 
> > I noticed that the CI was not triggered for this patch [1]. Do you 
> > know why? Is it possible to trigger it?
> > 
> > 1. 
> > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpa
> > tchwork.freedesktop.org%2Fseries%2F95313%2F&amp;data=04%7C01%7CRodri
> > go.Siqueira%40amd.com%7C43b5d7ab0731407a2f9008d987278e48%7C3dd8961fe
> > 4884e608e11a82d994e183d%7C0%7C0%7C637689426230154758%7CUnknown%7CTWF
> > pbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI
> > 6Mn0%3D%7C1000&amp;sdata=NIEF78%2B74hVRdQPhcCEPVlp4To3iDjkpkkv8VjSC0
> > %2BE%3D&amp;reserved=0
> 
> CI was down for a bit due to server cert issues, testing that and the 
> other affected series happening in a bit.

Thanks Petri,

I noticed that the CI was triggered for this patch.

Lakshminarayana,

It looks like that we have a false positive	in the result:

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

Notice that this patch only changes kms_hdr, but we have a failure in the igt@kms_lease.

Thanks
Siqueira
 
> 
> --
> Petri Latvala
> 
> 
> > 
> > Thanks
> > Siqueira
> > 
> > On 10/01, Stylon Wang wrote:
> > > The first commit with TEST_ONLY flag in bpc-switch subtests could 
> > > in some cases cause reading of output_bpc on connectors to fail on 
> > > AMD hardware.
> > > 
> > > Use ALLOW_MODESET to prevent this from happening.
> > > 
> > > Signed-off-by: Stylon Wang <stylon.wang@amd.com>
> > > ---
> > >  tests/kms_hdr.c | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/tests/kms_hdr.c b/tests/kms_hdr.c index 
> > > 5b8529c8..a4983b9a 100644
> > > --- a/tests/kms_hdr.c
> > > +++ b/tests/kms_hdr.c
> > > @@ -217,7 +217,7 @@ static void test_bpc_switch_on_output(data_t *data, igt_output_t *output,
> > >  		igt_plane_set_fb(data->primary, &afb);
> > >  		igt_plane_set_size(data->primary, data->w, data->h);
> > >  		igt_output_set_prop_value(data->output, IGT_CONNECTOR_MAX_BPC, 8);
> > > -		ret = igt_display_try_commit_atomic(display, DRM_MODE_ATOMIC_TEST_ONLY, NULL);
> > > +		ret = igt_display_try_commit_atomic(display, 
> > > +DRM_MODE_ATOMIC_ALLOW_MODESET, NULL);
> > >  		if (!ret) {
> > >  			data->w = afb.width;
> > >  			data->h = afb.height;
> > > --
> > > 2.32.0
> > > 
> > 
> > --
> > Rodrigo Siqueira
> > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsi
> > queira.tech%2F&amp;data=04%7C01%7CRodrigo.Siqueira%40amd.com%7C43b5d
> > 7ab0731407a2f9008d987278e48%7C3dd8961fe4884e608e11a82d994e183d%7C0%7
> > C0%7C637689426230154758%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAi
> > LCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=VvCE
> > WNlBkZnAm9M1JYeheIlVaUVMkeDiallVz0uUM8o%3D&amp;reserved=0

--
Rodrigo Siqueira
https://siqueira.tech

  reply	other threads:[~2021-10-04 15:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-01  8:53 [igt-dev] [PATCH i-g-t] tests/kms_hdr: Fix failure to read output_bpc on AMD hardware Stylon Wang
2021-10-02 15:15 ` Rodrigo Siqueira
2021-10-04 11:13   ` Petri Latvala
2021-10-04 14:18     ` Rodrigo Siqueira
2021-10-04 15:42       ` Vudum, Lakshminarayana [this message]
2021-10-04 17:07         ` Saarinen, Jani
2021-10-07 14:40           ` Rodrigo Siqueira
2021-10-07 14:49             ` Simon Ser
2021-10-07 14:54               ` Kazlauskas, Nicholas
2021-10-07 14:56                 ` Harry Wentland
2021-10-07 14:59                   ` Kazlauskas, Nicholas
2021-10-08  5:45                     ` Wang, Chao-kai (Stylon)
2021-10-08  6:33                       ` Simon Ser
2021-10-04 12:00 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2021-10-04 14:08 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2021-10-04 15:36 ` [igt-dev] ✓ Fi.CI.IGT: success " Patchwork

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=7c206aba165a465aa14b465c72b6802c@intel.com \
    --to=lakshminarayana.vudum@intel.com \
    --cc=Rodrigo.Siqueira@amd.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=nicholas.choi@amd.com \
    --cc=petri.latvala@intel.com \
    --cc=stylon.wang@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox