* [igt-dev] [PATCH i-g-t] tests/kms_hdr: Fix failure to read output_bpc on AMD hardware
@ 2021-10-01 8:53 Stylon Wang
2021-10-02 15:15 ` Rodrigo Siqueira
` (3 more replies)
0 siblings, 4 replies; 16+ messages in thread
From: Stylon Wang @ 2021-10-01 8:53 UTC (permalink / raw)
To: igt-dev; +Cc: nicholas.choi, rodrigo.siqueira, Stylon Wang
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
^ permalink raw reply related [flat|nested] 16+ messages in thread* Re: [igt-dev] [PATCH i-g-t] tests/kms_hdr: Fix failure to read output_bpc on AMD hardware 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 12:00 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork ` (2 subsequent siblings) 3 siblings, 1 reply; 16+ messages in thread From: Rodrigo Siqueira @ 2021-10-02 15:15 UTC (permalink / raw) To: Stylon Wang, Petri Latvala, Lakshminarayana Vudum; +Cc: igt-dev, nicholas.choi 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://patchwork.freedesktop.org/series/95313/ 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://siqueira.tech ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [igt-dev] [PATCH i-g-t] tests/kms_hdr: Fix failure to read output_bpc on AMD hardware 2021-10-02 15:15 ` Rodrigo Siqueira @ 2021-10-04 11:13 ` Petri Latvala 2021-10-04 14:18 ` Rodrigo Siqueira 0 siblings, 1 reply; 16+ messages in thread From: Petri Latvala @ 2021-10-04 11:13 UTC (permalink / raw) To: Rodrigo Siqueira Cc: Stylon Wang, Lakshminarayana Vudum, igt-dev, nicholas.choi 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://patchwork.freedesktop.org/series/95313/ CI was down for a bit due to server cert issues, testing that and the other affected series happening in a bit. -- 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://siqueira.tech ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [igt-dev] [PATCH i-g-t] tests/kms_hdr: Fix failure to read output_bpc on AMD hardware 2021-10-04 11:13 ` Petri Latvala @ 2021-10-04 14:18 ` Rodrigo Siqueira 2021-10-04 15:42 ` Vudum, Lakshminarayana 0 siblings, 1 reply; 16+ messages in thread From: Rodrigo Siqueira @ 2021-10-04 14:18 UTC (permalink / raw) To: Petri Latvala, Lakshminarayana Vudum; +Cc: Stylon Wang, igt-dev, nicholas.choi 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%2Fpatchwork.freedesktop.org%2Fseries%2F95313%2F&data=04%7C01%7CRodrigo.Siqueira%40amd.com%7C43b5d7ab0731407a2f9008d987278e48%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637689426230154758%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=NIEF78%2B74hVRdQPhcCEPVlp4To3iDjkpkkv8VjSC0%2BE%3D&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%2Fsiqueira.tech%2F&data=04%7C01%7CRodrigo.Siqueira%40amd.com%7C43b5d7ab0731407a2f9008d987278e48%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637689426230154758%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=VvCEWNlBkZnAm9M1JYeheIlVaUVMkeDiallVz0uUM8o%3D&reserved=0 -- Rodrigo Siqueira https://siqueira.tech ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [igt-dev] [PATCH i-g-t] tests/kms_hdr: Fix failure to read output_bpc on AMD hardware 2021-10-04 14:18 ` Rodrigo Siqueira @ 2021-10-04 15:42 ` Vudum, Lakshminarayana 2021-10-04 17:07 ` Saarinen, Jani 0 siblings, 1 reply; 16+ messages in thread From: Vudum, Lakshminarayana @ 2021-10-04 15:42 UTC (permalink / raw) To: Rodrigo Siqueira, Latvala, Petri; +Cc: Stylon Wang, igt-dev, nicholas.choi 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&data=04%7C01%7CRodri > > go.Siqueira%40amd.com%7C43b5d7ab0731407a2f9008d987278e48%7C3dd8961fe > > 4884e608e11a82d994e183d%7C0%7C0%7C637689426230154758%7CUnknown%7CTWF > > pbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI > > 6Mn0%3D%7C1000&sdata=NIEF78%2B74hVRdQPhcCEPVlp4To3iDjkpkkv8VjSC0 > > %2BE%3D&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&data=04%7C01%7CRodrigo.Siqueira%40amd.com%7C43b5d > > 7ab0731407a2f9008d987278e48%7C3dd8961fe4884e608e11a82d994e183d%7C0%7 > > C0%7C637689426230154758%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAi > > LCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=VvCE > > WNlBkZnAm9M1JYeheIlVaUVMkeDiallVz0uUM8o%3D&reserved=0 -- Rodrigo Siqueira https://siqueira.tech ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [igt-dev] [PATCH i-g-t] tests/kms_hdr: Fix failure to read output_bpc on AMD hardware 2021-10-04 15:42 ` Vudum, Lakshminarayana @ 2021-10-04 17:07 ` Saarinen, Jani 2021-10-07 14:40 ` Rodrigo Siqueira 0 siblings, 1 reply; 16+ messages in thread From: Saarinen, Jani @ 2021-10-04 17:07 UTC (permalink / raw) To: Vudum, Lakshminarayana, Rodrigo Siqueira, Latvala, Petri, Simon Ser Cc: Stylon Wang, igt-dev, nicholas.choi +Simon. > -----Original Message----- > From: igt-dev <igt-dev-bounces@lists.freedesktop.org> On Behalf Of Vudum, > Lakshminarayana > Sent: maanantai 4. lokakuuta 2021 18.42 > 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; > nicholas.choi@amd.com > Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_hdr: Fix failure to read output_bpc on > AMD hardware > > 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&data=04%7C01%7CRodri > > > > go.Siqueira%40amd.com%7C43b5d7ab0731407a2f9008d987278e48%7C3dd8961fe > > > > 4884e608e11a82d994e183d%7C0%7C0%7C637689426230154758%7CUnknown%7C > TWF > > > pbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI > > > > 6Mn0%3D%7C1000&sdata=NIEF78%2B74hVRdQPhcCEPVlp4To3iDjkpkkv8VjSC0 > > > %2BE%3D&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&data=04%7C01%7CRodrigo.Siqueira%40amd.com%7C43b5d > > > > 7ab0731407a2f9008d987278e48%7C3dd8961fe4884e608e11a82d994e183d%7C0% > 7 > > > > C0%7C637689426230154758%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwM > DAi > > > LCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=VvCE > > > WNlBkZnAm9M1JYeheIlVaUVMkeDiallVz0uUM8o%3D&reserved=0 > > -- > Rodrigo Siqueira > https://siqueira.tech ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [igt-dev] [PATCH i-g-t] tests/kms_hdr: Fix failure to read output_bpc on AMD hardware 2021-10-04 17:07 ` Saarinen, Jani @ 2021-10-07 14:40 ` Rodrigo Siqueira 2021-10-07 14:49 ` Simon Ser 0 siblings, 1 reply; 16+ messages in thread From: Rodrigo Siqueira @ 2021-10-07 14:40 UTC (permalink / raw) To: Saarinen, Jani Cc: Vudum, Lakshminarayana, Latvala, Petri, Simon Ser, Stylon Wang, igt-dev, nicholas.choi, Mark Yacoub, Wentland, Harry Hi, I noticed that the patch looks good from the CI perspective [1] and I don't see any problem on that, so: Reviewed-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com> 1. https://patchwork.freedesktop.org/series/95313/ On 10/04, Saarinen, Jani wrote: > +Simon. > > > -----Original Message----- > > From: igt-dev <igt-dev-bounces@lists.freedesktop.org> On Behalf Of Vudum, > > Lakshminarayana > > Sent: maanantai 4. lokakuuta 2021 18.42 > > 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; > > nicholas.choi@amd.com > > Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_hdr: Fix failure to read output_bpc on > > AMD hardware > > > > Filed https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.freedesktop.org%2Fdrm%2Fintel%2F-%2Fissues%2F4262&data=04%7C01%7CRodrigo.Siqueira%40amd.com%7C8c3f22f5fa6c48f0166808d9875c3133%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637689652302229936%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=sK0l9HWKszTbO75F%2FTaS7Swv%2FegjwVP0M8q%2FRlFg0Ys%3D&reserved=0 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&data=04%7C01%7CRodri > > > > > > go.Siqueira%40amd.com%7C43b5d7ab0731407a2f9008d987278e48%7C3dd8961fe > > > > > > 4884e608e11a82d994e183d%7C0%7C0%7C637689426230154758%7CUnknown%7C > > TWF > > > > pbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI > > > > > > 6Mn0%3D%7C1000&sdata=NIEF78%2B74hVRdQPhcCEPVlp4To3iDjkpkkv8VjSC0 > > > > %2BE%3D&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://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatchwork.freedesktop.org%2Fseries%2F95313%2F&data=04%7C01%7CRodrigo.Siqueira%40amd.com%7C8c3f22f5fa6c48f0166808d9875c3133%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637689652302229936%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=zJ74sNT%2B6yOcR3%2BH6w%2B2A8tYx84ge1c4ij%2FpCkOQoT8%3D&reserved=0 > > > > 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&data=04%7C01%7CRodrigo.Siqueira%40amd.com%7C43b5d > > > > > > 7ab0731407a2f9008d987278e48%7C3dd8961fe4884e608e11a82d994e183d%7C0% > > 7 > > > > > > C0%7C637689426230154758%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwM > > DAi > > > > LCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=VvCE > > > > WNlBkZnAm9M1JYeheIlVaUVMkeDiallVz0uUM8o%3D&reserved=0 > > > > -- > > Rodrigo Siqueira > > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsiqueira.tech%2F&data=04%7C01%7CRodrigo.Siqueira%40amd.com%7C8c3f22f5fa6c48f0166808d9875c3133%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637689652302229936%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ahQpaPpbX2AQtBhiQJU2zF25iWO%2FnWU3Vnx%2F640yRfU%3D&reserved=0 -- Rodrigo Siqueira https://siqueira.tech ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [igt-dev] [PATCH i-g-t] tests/kms_hdr: Fix failure to read output_bpc on AMD hardware 2021-10-07 14:40 ` Rodrigo Siqueira @ 2021-10-07 14:49 ` Simon Ser 2021-10-07 14:54 ` Kazlauskas, Nicholas 0 siblings, 1 reply; 16+ messages in thread From: Simon Ser @ 2021-10-07 14:49 UTC (permalink / raw) To: Rodrigo Siqueira Cc: Saarinen, Jani, Vudum, Lakshminarayana, Latvala, Petri, Stylon Wang, igt-dev, nicholas.choi, Mark Yacoub, Wentland, Harry, Nicholas Kazlauskas I don't think removing TEST_ONLY is correct? bafd90661c26 ("tests/kms_hdr: Add bpc switch subtests") reads: v4: -Plane size back to CRTC size, regression observed in hsw again "Plane must cover entire CRTC" because of plane size restriction to 512x512. Petri/Ville suggested to use TEST_ONLY in try_commit() to probe whether we can use a smaller than fullscreen plane. cc Nicholas ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [igt-dev] [PATCH i-g-t] tests/kms_hdr: Fix failure to read output_bpc on AMD hardware 2021-10-07 14:49 ` Simon Ser @ 2021-10-07 14:54 ` Kazlauskas, Nicholas 2021-10-07 14:56 ` Harry Wentland 0 siblings, 1 reply; 16+ messages in thread From: Kazlauskas, Nicholas @ 2021-10-07 14:54 UTC (permalink / raw) To: Siqueira, Rodrigo, Simon Ser Cc: Saarinen, Jani, Vudum, Lakshminarayana, Latvala, Petri, Wang, Chao-kai (Stylon), igt-dev, Choi, Nicholas, Mark Yacoub, Wentland, Harry [-- Attachment #1: Type: text/plain, Size: 1527 bytes --] [AMD Official Use Only] I don't have the commits in front of me, but there was an issue with the port from amd_hdr to kms_hdr where the test would do a TEST_ONLY commit that change the output bpc to 10 but then the debugfs check after would try and verify that the output bpc was 10 - which doesn't work if the output bpc was previously 8 because the commit wasn't actually applied. Regards, Nicholas Kazlauskas ________________________________ From: Simon Ser <contact@emersion.fr> Sent: Thursday, October 7, 2021 10:49 AM To: Siqueira, Rodrigo <Rodrigo.Siqueira@amd.com> Cc: Saarinen, Jani <jani.saarinen@intel.com>; Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>; Latvala, Petri <petri.latvala@intel.com>; Wang, Chao-kai (Stylon) <Stylon.Wang@amd.com>; igt-dev@lists.freedesktop.org <igt-dev@lists.freedesktop.org>; Choi, Nicholas <Nicholas.Choi@amd.com>; Mark Yacoub <markyacoub@google.com>; Wentland, Harry <Harry.Wentland@amd.com>; Kazlauskas, Nicholas <Nicholas.Kazlauskas@amd.com> Subject: Re: [PATCH i-g-t] tests/kms_hdr: Fix failure to read output_bpc on AMD hardware I don't think removing TEST_ONLY is correct? bafd90661c26 ("tests/kms_hdr: Add bpc switch subtests") reads: v4: -Plane size back to CRTC size, regression observed in hsw again "Plane must cover entire CRTC" because of plane size restriction to 512x512. Petri/Ville suggested to use TEST_ONLY in try_commit() to probe whether we can use a smaller than fullscreen plane. cc Nicholas [-- Attachment #2: Type: text/html, Size: 2952 bytes --] ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [igt-dev] [PATCH i-g-t] tests/kms_hdr: Fix failure to read output_bpc on AMD hardware 2021-10-07 14:54 ` Kazlauskas, Nicholas @ 2021-10-07 14:56 ` Harry Wentland 2021-10-07 14:59 ` Kazlauskas, Nicholas 0 siblings, 1 reply; 16+ messages in thread From: Harry Wentland @ 2021-10-07 14:56 UTC (permalink / raw) To: Kazlauskas, Nicholas, Siqueira, Rodrigo, Simon Ser Cc: Saarinen, Jani, Vudum, Lakshminarayana, Latvala, Petri, Wang, Chao-kai (Stylon), igt-dev, Choi, Nicholas, Mark Yacoub On 2021-10-07 10:54, Kazlauskas, Nicholas wrote: > [AMD Official Use Only] > > > I don't have the commits in front of me, but there was an issue with the port from amd_hdr to kms_hdr where the test would do a TEST_ONLY commit that change the output bpc to 10 but then the debugfs check /after /would try and verify that the output bpc was 10 - which doesn't work if the output bpc was previously 8 because the commit wasn't actually applied. > https://patchwork.freedesktop.org/patch/456663/?series=95313&rev=1 Stylon, is that what is happening? If so, please make sure the commit description reflects that. The existing description doesn't explain why switching from TEST_ONLY to ALLOW_MODESET fixes things. Harry > Regards, > Nicholas Kazlauskas > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > *From:* Simon Ser <contact@emersion.fr> > *Sent:* Thursday, October 7, 2021 10:49 AM > *To:* Siqueira, Rodrigo <Rodrigo.Siqueira@amd.com> > *Cc:* Saarinen, Jani <jani.saarinen@intel.com>; Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>; Latvala, Petri <petri.latvala@intel.com>; Wang, Chao-kai (Stylon) <Stylon.Wang@amd.com>; igt-dev@lists.freedesktop.org <igt-dev@lists.freedesktop.org>; Choi, Nicholas <Nicholas.Choi@amd.com>; Mark Yacoub <markyacoub@google.com>; Wentland, Harry <Harry.Wentland@amd.com>; Kazlauskas, Nicholas <Nicholas.Kazlauskas@amd.com> > *Subject:* Re: [PATCH i-g-t] tests/kms_hdr: Fix failure to read output_bpc on AMD hardware > > I don't think removing TEST_ONLY is correct? bafd90661c26 ("tests/kms_hdr: Add > bpc switch subtests") reads: > > v4: -Plane size back to CRTC size, regression observed in hsw again > "Plane must cover entire CRTC" because of plane size restriction > to 512x512. Petri/Ville suggested to use TEST_ONLY in try_commit() > to probe whether we can use a smaller than fullscreen plane. > > cc Nicholas ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [igt-dev] [PATCH i-g-t] tests/kms_hdr: Fix failure to read output_bpc on AMD hardware 2021-10-07 14:56 ` Harry Wentland @ 2021-10-07 14:59 ` Kazlauskas, Nicholas 2021-10-08 5:45 ` Wang, Chao-kai (Stylon) 0 siblings, 1 reply; 16+ messages in thread From: Kazlauskas, Nicholas @ 2021-10-07 14:59 UTC (permalink / raw) To: Harry Wentland, Siqueira, Rodrigo, Simon Ser Cc: Saarinen, Jani, Vudum, Lakshminarayana, Latvala, Petri, Wang, Chao-kai (Stylon), igt-dev, Choi, Nicholas, Mark Yacoub On 2021-10-07 10:56 a.m., Harry Wentland wrote: > > > On 2021-10-07 10:54, Kazlauskas, Nicholas wrote: >> [AMD Official Use Only] >> >> >> I don't have the commits in front of me, but there was an issue with the port from amd_hdr to kms_hdr where the test would do a TEST_ONLY commit that change the output bpc to 10 but then the debugfs check /after /would try and verify that the output bpc was 10 - which doesn't work if the output bpc was previously 8 because the commit wasn't actually applied. >> > > https://patchwork.freedesktop.org/patch/456663/?series=95313&rev=1 > > Stylon, is that what is happening? > > If so, please make sure the commit description reflects that. The existing > description doesn't explain why switching from TEST_ONLY to ALLOW_MODESET > fixes things. > > Harry Thanks for linking it - it looks like it's actually the reverse, where it tries to change bpc to 8 but the connector may not currently be in 8 nor is there a requirement for it to be before the test starts. Userspace might have already been running with an uncapped max bpc before the test starts. Regards, Nicholas Kazlauskas > > >> Regards, >> Nicholas Kazlauskas >> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ >> *From:* Simon Ser <contact@emersion.fr> >> *Sent:* Thursday, October 7, 2021 10:49 AM >> *To:* Siqueira, Rodrigo <Rodrigo.Siqueira@amd.com> >> *Cc:* Saarinen, Jani <jani.saarinen@intel.com>; Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>; Latvala, Petri <petri.latvala@intel.com>; Wang, Chao-kai (Stylon) <Stylon.Wang@amd.com>; igt-dev@lists.freedesktop.org <igt-dev@lists.freedesktop.org>; Choi, Nicholas <Nicholas.Choi@amd.com>; Mark Yacoub <markyacoub@google.com>; Wentland, Harry <Harry.Wentland@amd.com>; Kazlauskas, Nicholas <Nicholas.Kazlauskas@amd.com> >> *Subject:* Re: [PATCH i-g-t] tests/kms_hdr: Fix failure to read output_bpc on AMD hardware >> >> I don't think removing TEST_ONLY is correct? bafd90661c26 ("tests/kms_hdr: Add >> bpc switch subtests") reads: >> >> v4: -Plane size back to CRTC size, regression observed in hsw again >> "Plane must cover entire CRTC" because of plane size restriction >> to 512x512. Petri/Ville suggested to use TEST_ONLY in try_commit() >> to probe whether we can use a smaller than fullscreen plane. >> >> cc Nicholas > ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [igt-dev] [PATCH i-g-t] tests/kms_hdr: Fix failure to read output_bpc on AMD hardware 2021-10-07 14:59 ` Kazlauskas, Nicholas @ 2021-10-08 5:45 ` Wang, Chao-kai (Stylon) 2021-10-08 6:33 ` Simon Ser 0 siblings, 1 reply; 16+ messages in thread From: Wang, Chao-kai (Stylon) @ 2021-10-08 5:45 UTC (permalink / raw) To: Kazlauskas, Nicholas, Wentland, Harry, Siqueira, Rodrigo, Simon Ser Cc: Saarinen, Jani, Vudum, Lakshminarayana, Latvala, Petri, igt-dev, Choi, Nicholas, Mark Yacoub [-- Attachment #1: Type: text/plain, Size: 4795 bytes --] [AMD Official Use Only] I wanna propose to break down this patch into 2 changes: 1. Keep theTEST_ONLY commit to check if 512x512 plane works. If not, change the plane size to cover full CRTC. 2. Add a real commit after TEST_ONLY to set output bpc to 8. This should satisfy the first check that the output bpc is indeed 8 Regards Stylon Wang MTS Software Development Eng. | AMD Display Solution Team O +(886) 2-3789-3667 ext. 23667 C +(886) 921-897-142 ---------------------------------------------------------------------------------------------------------------------------------- 6F, 3, YuanCyu St (NanKang Software Park) Taipei, Taiwan Facebook<https://www.facebook.com/AMD> | Twitter<https://twitter.com/AMD> | amd.com<http://www.amd.com/> ________________________________ From: Kazlauskas, Nicholas <Nicholas.Kazlauskas@amd.com> Sent: October 7, 2021 10:59 PM To: Wentland, Harry <Harry.Wentland@amd.com>; Siqueira, Rodrigo <Rodrigo.Siqueira@amd.com>; Simon Ser <contact@emersion.fr> Cc: Saarinen, Jani <jani.saarinen@intel.com>; Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>; Latvala, Petri <petri.latvala@intel.com>; Wang, Chao-kai (Stylon) <Stylon.Wang@amd.com>; igt-dev@lists.freedesktop.org <igt-dev@lists.freedesktop.org>; Choi, Nicholas <Nicholas.Choi@amd.com>; Mark Yacoub <markyacoub@google.com> Subject: Re: [PATCH i-g-t] tests/kms_hdr: Fix failure to read output_bpc on AMD hardware On 2021-10-07 10:56 a.m., Harry Wentland wrote: > > > On 2021-10-07 10:54, Kazlauskas, Nicholas wrote: >> [AMD Official Use Only] >> >> >> I don't have the commits in front of me, but there was an issue with the port from amd_hdr to kms_hdr where the test would do a TEST_ONLY commit that change the output bpc to 10 but then the debugfs check /after /would try and verify that the output bpc was 10 - which doesn't work if the output bpc was previously 8 because the commit wasn't actually applied. >> > > https://patchwork.freedesktop.org/patch/456663/?series=95313&rev=1 > > Stylon, is that what is happening? > > If so, please make sure the commit description reflects that. The existing > description doesn't explain why switching from TEST_ONLY to ALLOW_MODESET > fixes things. > > Harry Thanks for linking it - it looks like it's actually the reverse, where it tries to change bpc to 8 but the connector may not currently be in 8 nor is there a requirement for it to be before the test starts. Userspace might have already been running with an uncapped max bpc before the test starts. Regards, Nicholas Kazlauskas > > >> Regards, >> Nicholas Kazlauskas >> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ >> *From:* Simon Ser <contact@emersion.fr> >> *Sent:* Thursday, October 7, 2021 10:49 AM >> *To:* Siqueira, Rodrigo <Rodrigo.Siqueira@amd.com> >> *Cc:* Saarinen, Jani <jani.saarinen@intel.com>; Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>; Latvala, Petri <petri.latvala@intel.com>; Wang, Chao-kai (Stylon) <Stylon.Wang@amd.com>; igt-dev@lists.freedesktop.org <igt-dev@lists.freedesktop.org>; Choi, Nicholas <Nicholas.Choi@amd.com>; Mark Yacoub <markyacoub@google.com>; Wentland, Harry <Harry.Wentland@amd.com>; Kazlauskas, Nicholas <Nicholas.Kazlauskas@amd.com> >> *Subject:* Re: [PATCH i-g-t] tests/kms_hdr: Fix failure to read output_bpc on AMD hardware >> >> I don't think removing TEST_ONLY is correct? bafd90661c26 ("tests/kms_hdr: Add >> bpc switch subtests") reads: >> >> v4: -Plane size back to CRTC size, regression observed in hsw again >> "Plane must cover entire CRTC" because of plane size restriction >> to 512x512. Petri/Ville suggested to use TEST_ONLY in try_commit() >> to probe whether we can use a smaller than fullscreen plane. >> >> cc Nicholas > [-- Attachment #2: Type: text/html, Size: 10063 bytes --] ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [igt-dev] [PATCH i-g-t] tests/kms_hdr: Fix failure to read output_bpc on AMD hardware 2021-10-08 5:45 ` Wang, Chao-kai (Stylon) @ 2021-10-08 6:33 ` Simon Ser 0 siblings, 0 replies; 16+ messages in thread From: Simon Ser @ 2021-10-08 6:33 UTC (permalink / raw) To: Wang, Chao-kai (Stylon) Cc: Kazlauskas, Nicholas, Wentland, Harry, Siqueira, Rodrigo, Saarinen, Jani, Vudum, Lakshminarayana, Latvala, Petri, igt-dev, Choi, Nicholas, Mark Yacoub On Friday, October 8th, 2021 at 07:45, Wang, Chao-kai (Stylon) <Stylon.Wang@amd.com> wrote: > I wanna propose to break down this patch into 2 changes: > > 1. Keep theTEST_ONLY commit to check if 512x512 plane works. If not, change the plane size to cover full CRTC. > 2. Add a real commit after TEST_ONLY to set output bpc to 8. This should satisfy the first check that the output bpc is indeed 8 Looks like a good idea to me. ^ permalink raw reply [flat|nested] 16+ messages in thread
* [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_hdr: Fix failure to read output_bpc on AMD hardware 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 12:00 ` 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 3 siblings, 0 replies; 16+ messages in thread From: Patchwork @ 2021-10-04 12:00 UTC (permalink / raw) To: Stylon Wang; +Cc: igt-dev [-- Attachment #1: Type: text/plain, Size: 5711 bytes --] == Series Details == Series: tests/kms_hdr: Fix failure to read output_bpc on AMD hardware URL : https://patchwork.freedesktop.org/series/95313/ State : success == Summary == CI Bug Log - changes from IGT_6229 -> IGTPW_6274 ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/index.html Known issues ------------ Here are the changes found in IGTPW_6274 that come from known issues: ### IGT changes ### #### Issues hit #### * igt@amdgpu/amd_basic@query-info: - fi-kbl-soraka: NOTRUN -> [SKIP][1] ([fdo#109271]) [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/fi-kbl-soraka/igt@amdgpu/amd_basic@query-info.html * igt@amdgpu/amd_cs_nop@nop-compute0: - fi-ilk-650: NOTRUN -> [SKIP][2] ([fdo#109271]) +35 similar issues [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/fi-ilk-650/igt@amdgpu/amd_cs_nop@nop-compute0.html * igt@amdgpu/amd_cs_nop@sync-fork-compute0: - fi-snb-2600: NOTRUN -> [SKIP][3] ([fdo#109271]) +17 similar issues [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/fi-snb-2600/igt@amdgpu/amd_cs_nop@sync-fork-compute0.html * igt@core_hotunplug@unbind-rebind: - fi-bdw-samus: NOTRUN -> [WARN][4] ([i915#3718]) [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/fi-bdw-samus/igt@core_hotunplug@unbind-rebind.html * igt@kms_chamelium@dp-hpd-fast: - fi-ilk-650: NOTRUN -> [SKIP][5] ([fdo#109271] / [fdo#111827]) +8 similar issues [5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/fi-ilk-650/igt@kms_chamelium@dp-hpd-fast.html * igt@kms_chamelium@hdmi-edid-read: - fi-bdw-samus: NOTRUN -> [SKIP][6] ([fdo#109271] / [fdo#111827]) +8 similar issues [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/fi-bdw-samus/igt@kms_chamelium@hdmi-edid-read.html * igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d: - fi-bdw-samus: NOTRUN -> [SKIP][7] ([fdo#109271]) +29 similar issues [7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/fi-bdw-samus/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html * igt@prime_vgem@basic-userptr: - fi-pnv-d510: NOTRUN -> [SKIP][8] ([fdo#109271]) +48 similar issues [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/fi-pnv-d510/igt@prime_vgem@basic-userptr.html #### Possible fixes #### * igt@gem_exec_parallel@engines@userptr: - fi-pnv-d510: [INCOMPLETE][9] ([i915#299]) -> [PASS][10] [9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/fi-pnv-d510/igt@gem_exec_parallel@engines@userptr.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/fi-pnv-d510/igt@gem_exec_parallel@engines@userptr.html * igt@gem_exec_suspend@basic-s3: - fi-bdw-samus: [INCOMPLETE][11] ([i915#146] / [i915#4173]) -> [PASS][12] [11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/fi-bdw-samus/igt@gem_exec_suspend@basic-s3.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/fi-bdw-samus/igt@gem_exec_suspend@basic-s3.html - fi-tgl-1115g4: [FAIL][13] ([i915#1888]) -> [PASS][14] [13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/fi-tgl-1115g4/igt@gem_exec_suspend@basic-s3.html [14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/fi-tgl-1115g4/igt@gem_exec_suspend@basic-s3.html * igt@i915_selftest@live@hangcheck: - fi-snb-2600: [INCOMPLETE][15] ([i915#3921]) -> [PASS][16] [15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/fi-snb-2600/igt@i915_selftest@live@hangcheck.html [16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/fi-snb-2600/igt@i915_selftest@live@hangcheck.html * igt@kms_chamelium@hdmi-edid-read: - fi-kbl-7500u: [FAIL][17] ([i915#3449]) -> [PASS][18] [17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/fi-kbl-7500u/igt@kms_chamelium@hdmi-edid-read.html [18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/fi-kbl-7500u/igt@kms_chamelium@hdmi-edid-read.html * igt@kms_frontbuffer_tracking@basic: - fi-cml-u2: [DMESG-WARN][19] ([i915#95]) -> [PASS][20] [19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/fi-cml-u2/igt@kms_frontbuffer_tracking@basic.html [20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/fi-cml-u2/igt@kms_frontbuffer_tracking@basic.html [fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271 [fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827 [i915#146]: https://gitlab.freedesktop.org/drm/intel/issues/146 [i915#1888]: https://gitlab.freedesktop.org/drm/intel/issues/1888 [i915#299]: https://gitlab.freedesktop.org/drm/intel/issues/299 [i915#3449]: https://gitlab.freedesktop.org/drm/intel/issues/3449 [i915#3718]: https://gitlab.freedesktop.org/drm/intel/issues/3718 [i915#3921]: https://gitlab.freedesktop.org/drm/intel/issues/3921 [i915#4173]: https://gitlab.freedesktop.org/drm/intel/issues/4173 [i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95 Participating hosts (33 -> 33) ------------------------------ Additional (1): fi-ilk-650 Missing (1): fi-bsw-cyan Build changes ------------- * CI: CI-20190529 -> None * IGT: IGT_6229 -> IGTPW_6274 CI-20190529: 20190529 CI_DRM_10681: fe9b639a95a08713c8ee4ef110ce6a6388c9f9f2 @ git://anongit.freedesktop.org/gfx-ci/linux IGTPW_6274: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/index.html IGT_6229: dff598c339a2da647f15c86d0015e16378c7ea9b @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/index.html [-- Attachment #2: Type: text/html, Size: 7119 bytes --] ^ permalink raw reply [flat|nested] 16+ messages in thread
* [igt-dev] ✗ Fi.CI.IGT: failure for tests/kms_hdr: Fix failure to read output_bpc on AMD hardware 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 12:00 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork @ 2021-10-04 14:08 ` Patchwork 2021-10-04 15:36 ` [igt-dev] ✓ Fi.CI.IGT: success " Patchwork 3 siblings, 0 replies; 16+ messages in thread From: Patchwork @ 2021-10-04 14:08 UTC (permalink / raw) To: Stylon Wang; +Cc: igt-dev [-- Attachment #1: Type: text/plain, Size: 30279 bytes --] == Series Details == Series: tests/kms_hdr: Fix failure to read output_bpc on AMD hardware URL : https://patchwork.freedesktop.org/series/95313/ State : failure == Summary == CI Bug Log - changes from IGT_6229_full -> IGTPW_6274_full ==================================================== Summary ------- **FAILURE** Serious unknown changes coming with IGTPW_6274_full absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in IGTPW_6274_full, 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_6274/index.html Possible new issues ------------------- Here are the unknown changes that may have been introduced in IGTPW_6274_full: ### IGT changes ### #### Possible regressions #### * igt@kms_lease@invalid-create-leases: - shard-kbl: NOTRUN -> [FAIL][1] [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl6/igt@kms_lease@invalid-create-leases.html - shard-apl: NOTRUN -> [FAIL][2] [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl7/igt@kms_lease@invalid-create-leases.html Known issues ------------ Here are the changes found in IGTPW_6274_full that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_ctx_persistence@legacy-engines-queued: - shard-snb: NOTRUN -> [SKIP][3] ([fdo#109271] / [i915#1099]) +7 similar issues [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-snb6/igt@gem_ctx_persistence@legacy-engines-queued.html * igt@gem_eio@unwedge-stress: - shard-snb: NOTRUN -> [FAIL][4] ([i915#3354]) [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-snb2/igt@gem_eio@unwedge-stress.html * igt@gem_exec_fair@basic-deadline: - shard-kbl: [PASS][5] -> [FAIL][6] ([i915#2846]) [5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-kbl4/igt@gem_exec_fair@basic-deadline.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl6/igt@gem_exec_fair@basic-deadline.html - shard-apl: NOTRUN -> [FAIL][7] ([i915#2846]) [7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl7/igt@gem_exec_fair@basic-deadline.html * igt@gem_exec_fair@basic-none-solo@rcs0: - shard-kbl: NOTRUN -> [FAIL][8] ([i915#2842]) [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl4/igt@gem_exec_fair@basic-none-solo@rcs0.html * igt@gem_exec_fair@basic-pace-solo@rcs0: - shard-kbl: [PASS][9] -> [FAIL][10] ([i915#2842]) [9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-kbl3/igt@gem_exec_fair@basic-pace-solo@rcs0.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl6/igt@gem_exec_fair@basic-pace-solo@rcs0.html * igt@gem_exec_fair@basic-pace@vcs1: - shard-tglb: [PASS][11] -> [FAIL][12] ([i915#2842]) [11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-tglb5/igt@gem_exec_fair@basic-pace@vcs1.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@gem_exec_fair@basic-pace@vcs1.html * igt@gem_exec_fair@basic-pace@vecs0: - shard-glk: [PASS][13] -> [FAIL][14] ([i915#2842]) +2 similar issues [13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-glk7/igt@gem_exec_fair@basic-pace@vecs0.html [14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-glk5/igt@gem_exec_fair@basic-pace@vecs0.html * igt@gem_exec_fair@basic-throttle@rcs0: - shard-tglb: NOTRUN -> [FAIL][15] ([i915#2842]) [15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb5/igt@gem_exec_fair@basic-throttle@rcs0.html * igt@gem_exec_flush@basic-batch-kernel-default-cmd: - shard-snb: NOTRUN -> [SKIP][16] ([fdo#109271]) +484 similar issues [16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-snb6/igt@gem_exec_flush@basic-batch-kernel-default-cmd.html - shard-iclb: NOTRUN -> [SKIP][17] ([fdo#109313]) [17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb8/igt@gem_exec_flush@basic-batch-kernel-default-cmd.html - shard-tglb: NOTRUN -> [SKIP][18] ([fdo#109313]) [18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb8/igt@gem_exec_flush@basic-batch-kernel-default-cmd.html * igt@gem_exec_reloc@basic-wc-cpu-active: - shard-apl: [PASS][19] -> [DMESG-WARN][20] ([i915#62]) +6 similar issues [19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-apl3/igt@gem_exec_reloc@basic-wc-cpu-active.html [20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl1/igt@gem_exec_reloc@basic-wc-cpu-active.html * igt@gem_huc_copy@huc-copy: - shard-tglb: [PASS][21] -> [SKIP][22] ([i915#2190]) [21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-tglb5/igt@gem_huc_copy@huc-copy.html [22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb6/igt@gem_huc_copy@huc-copy.html * igt@gem_render_copy@y-tiled-to-vebox-linear: - shard-iclb: NOTRUN -> [SKIP][23] ([i915#768]) [23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb2/igt@gem_render_copy@y-tiled-to-vebox-linear.html * igt@gem_userptr_blits@input-checking: - shard-apl: NOTRUN -> [DMESG-WARN][24] ([i915#3002]) [24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl6/igt@gem_userptr_blits@input-checking.html * igt@gen3_render_linear_blits: - shard-tglb: NOTRUN -> [SKIP][25] ([fdo#109289]) +2 similar issues [25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb8/igt@gen3_render_linear_blits.html * igt@gen3_render_mixed_blits: - shard-iclb: NOTRUN -> [SKIP][26] ([fdo#109289]) [26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb4/igt@gen3_render_mixed_blits.html * igt@gen9_exec_parse@bb-chained: - shard-tglb: NOTRUN -> [SKIP][27] ([i915#2856]) [27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb2/igt@gen9_exec_parse@bb-chained.html * igt@i915_pm_backlight@fade_with_suspend: - shard-tglb: [PASS][28] -> [INCOMPLETE][29] ([i915#4173] / [i915#456]) [28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-tglb1/igt@i915_pm_backlight@fade_with_suspend.html [29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb7/igt@i915_pm_backlight@fade_with_suspend.html * igt@i915_pm_dc@dc6-dpms: - shard-kbl: NOTRUN -> [FAIL][30] ([i915#454]) [30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl3/igt@i915_pm_dc@dc6-dpms.html - shard-tglb: NOTRUN -> [FAIL][31] ([i915#454]) [31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb6/igt@i915_pm_dc@dc6-dpms.html * igt@i915_pm_rpm@gem-execbuf-stress-pc8: - shard-iclb: NOTRUN -> [SKIP][32] ([fdo#109293] / [fdo#109506]) [32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb3/igt@i915_pm_rpm@gem-execbuf-stress-pc8.html - shard-tglb: NOTRUN -> [SKIP][33] ([fdo#109506] / [i915#2411]) [33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb2/igt@i915_pm_rpm@gem-execbuf-stress-pc8.html * igt@kms_atomic_transition@plane-all-modeset-transition: - shard-iclb: NOTRUN -> [SKIP][34] ([i915#1769]) [34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb6/igt@kms_atomic_transition@plane-all-modeset-transition.html * igt@kms_big_fb@linear-32bpp-rotate-180: - shard-glk: [PASS][35] -> [DMESG-WARN][36] ([i915#118] / [i915#95]) +2 similar issues [35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-glk5/igt@kms_big_fb@linear-32bpp-rotate-180.html [36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-glk9/igt@kms_big_fb@linear-32bpp-rotate-180.html * igt@kms_big_fb@x-tiled-16bpp-rotate-90: - shard-iclb: NOTRUN -> [SKIP][37] ([fdo#110725] / [fdo#111614]) [37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb1/igt@kms_big_fb@x-tiled-16bpp-rotate-90.html * igt@kms_big_fb@x-tiled-8bpp-rotate-270: - shard-tglb: NOTRUN -> [SKIP][38] ([fdo#111614]) +1 similar issue [38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@kms_big_fb@x-tiled-8bpp-rotate-270.html * igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0-hflip: - shard-kbl: NOTRUN -> [SKIP][39] ([fdo#109271] / [i915#3777]) [39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl6/igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0-hflip.html * igt@kms_big_fb@yf-tiled-64bpp-rotate-0: - shard-iclb: NOTRUN -> [SKIP][40] ([fdo#110723]) [40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb1/igt@kms_big_fb@yf-tiled-64bpp-rotate-0.html * igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0-hflip: - shard-apl: NOTRUN -> [SKIP][41] ([fdo#109271] / [i915#3777]) +3 similar issues [41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl8/igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0-hflip.html * igt@kms_big_joiner@2x-modeset: - shard-iclb: NOTRUN -> [SKIP][42] ([i915#2705]) [42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb1/igt@kms_big_joiner@2x-modeset.html - shard-tglb: NOTRUN -> [SKIP][43] ([i915#2705]) [43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@kms_big_joiner@2x-modeset.html * igt@kms_ccs@pipe-a-bad-pixel-format-y_tiled_gen12_mc_ccs: - shard-tglb: NOTRUN -> [SKIP][44] ([i915#3689] / [i915#3886]) +1 similar issue [44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb1/igt@kms_ccs@pipe-a-bad-pixel-format-y_tiled_gen12_mc_ccs.html * igt@kms_ccs@pipe-a-bad-rotation-90-y_tiled_gen12_rc_ccs_cc: - shard-kbl: NOTRUN -> [SKIP][45] ([fdo#109271] / [i915#3886]) +8 similar issues [45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl3/igt@kms_ccs@pipe-a-bad-rotation-90-y_tiled_gen12_rc_ccs_cc.html * igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_rc_ccs_cc: - shard-apl: NOTRUN -> [SKIP][46] ([fdo#109271] / [i915#3886]) +12 similar issues [46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl3/igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_rc_ccs_cc.html * igt@kms_ccs@pipe-a-random-ccs-data-yf_tiled_ccs: - shard-tglb: NOTRUN -> [SKIP][47] ([i915#3689]) +14 similar issues [47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb5/igt@kms_ccs@pipe-a-random-ccs-data-yf_tiled_ccs.html * igt@kms_ccs@pipe-c-bad-pixel-format-y_tiled_gen12_rc_ccs_cc: - shard-glk: NOTRUN -> [SKIP][48] ([fdo#109271] / [i915#3886]) [48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-glk9/igt@kms_ccs@pipe-c-bad-pixel-format-y_tiled_gen12_rc_ccs_cc.html - shard-iclb: NOTRUN -> [SKIP][49] ([fdo#109278] / [i915#3886]) [49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb4/igt@kms_ccs@pipe-c-bad-pixel-format-y_tiled_gen12_rc_ccs_cc.html * igt@kms_chamelium@dp-hpd-fast: - shard-glk: NOTRUN -> [SKIP][50] ([fdo#109271] / [fdo#111827]) +6 similar issues [50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-glk6/igt@kms_chamelium@dp-hpd-fast.html * igt@kms_chamelium@hdmi-audio: - shard-iclb: NOTRUN -> [SKIP][51] ([fdo#109284] / [fdo#111827]) +6 similar issues [51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb8/igt@kms_chamelium@hdmi-audio.html * igt@kms_chamelium@hdmi-edid-change-during-suspend: - shard-apl: NOTRUN -> [SKIP][52] ([fdo#109271] / [fdo#111827]) +21 similar issues [52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl3/igt@kms_chamelium@hdmi-edid-change-during-suspend.html * igt@kms_chamelium@hdmi-hpd-enable-disable-mode: - shard-snb: NOTRUN -> [SKIP][53] ([fdo#109271] / [fdo#111827]) +24 similar issues [53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-snb6/igt@kms_chamelium@hdmi-hpd-enable-disable-mode.html * igt@kms_chamelium@hdmi-hpd-for-each-pipe: - shard-kbl: NOTRUN -> [SKIP][54] ([fdo#109271] / [fdo#111827]) +21 similar issues [54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl6/igt@kms_chamelium@hdmi-hpd-for-each-pipe.html * igt@kms_color@pipe-d-ctm-blue-to-red: - shard-iclb: NOTRUN -> [SKIP][55] ([fdo#109278] / [i915#1149]) [55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb4/igt@kms_color@pipe-d-ctm-blue-to-red.html * igt@kms_color_chamelium@pipe-b-ctm-limited-range: - shard-tglb: NOTRUN -> [SKIP][56] ([fdo#109284] / [fdo#111827]) +6 similar issues [56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@kms_color_chamelium@pipe-b-ctm-limited-range.html * igt@kms_color_chamelium@pipe-d-ctm-blue-to-red: - shard-iclb: NOTRUN -> [SKIP][57] ([fdo#109278] / [fdo#109284] / [fdo#111827]) [57]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb2/igt@kms_color_chamelium@pipe-d-ctm-blue-to-red.html * igt@kms_concurrent@pipe-d: - shard-tglb: NOTRUN -> [FAIL][58] ([i915#1385]) [58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb6/igt@kms_concurrent@pipe-d.html * igt@kms_content_protection@dp-mst-lic-type-0: - shard-iclb: NOTRUN -> [SKIP][59] ([i915#3116]) [59]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb8/igt@kms_content_protection@dp-mst-lic-type-0.html - shard-tglb: NOTRUN -> [SKIP][60] ([i915#3116]) [60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb7/igt@kms_content_protection@dp-mst-lic-type-0.html * igt@kms_content_protection@legacy: - shard-kbl: NOTRUN -> [TIMEOUT][61] ([i915#1319]) +1 similar issue [61]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl3/igt@kms_content_protection@legacy.html - shard-apl: NOTRUN -> [TIMEOUT][62] ([i915#1319]) [62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl7/igt@kms_content_protection@legacy.html * igt@kms_content_protection@lic: - shard-tglb: NOTRUN -> [SKIP][63] ([fdo#111828]) [63]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb5/igt@kms_content_protection@lic.html * igt@kms_cursor_crc@pipe-a-cursor-512x512-rapid-movement: - shard-iclb: NOTRUN -> [SKIP][64] ([fdo#109278] / [fdo#109279]) +2 similar issues [64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb6/igt@kms_cursor_crc@pipe-a-cursor-512x512-rapid-movement.html * igt@kms_cursor_crc@pipe-a-cursor-suspend: - shard-kbl: [PASS][65] -> [DMESG-WARN][66] ([i915#180]) +2 similar issues [65]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-kbl1/igt@kms_cursor_crc@pipe-a-cursor-suspend.html [66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl7/igt@kms_cursor_crc@pipe-a-cursor-suspend.html * igt@kms_cursor_crc@pipe-b-cursor-32x10-random: - shard-tglb: NOTRUN -> [SKIP][67] ([i915#3359]) +3 similar issues [67]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb8/igt@kms_cursor_crc@pipe-b-cursor-32x10-random.html * igt@kms_cursor_crc@pipe-b-cursor-alpha-opaque: - shard-apl: NOTRUN -> [FAIL][68] ([i915#3444]) [68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl3/igt@kms_cursor_crc@pipe-b-cursor-alpha-opaque.html - shard-kbl: NOTRUN -> [FAIL][69] ([i915#3444]) [69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl6/igt@kms_cursor_crc@pipe-b-cursor-alpha-opaque.html * igt@kms_cursor_crc@pipe-d-cursor-256x256-onscreen: - shard-kbl: NOTRUN -> [SKIP][70] ([fdo#109271]) +208 similar issues [70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl4/igt@kms_cursor_crc@pipe-d-cursor-256x256-onscreen.html * igt@kms_cursor_crc@pipe-d-cursor-32x32-onscreen: - shard-tglb: NOTRUN -> [SKIP][71] ([i915#3319]) +3 similar issues [71]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb5/igt@kms_cursor_crc@pipe-d-cursor-32x32-onscreen.html * igt@kms_cursor_crc@pipe-d-cursor-512x512-rapid-movement: - shard-tglb: NOTRUN -> [SKIP][72] ([fdo#109279] / [i915#3359]) +2 similar issues [72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb1/igt@kms_cursor_crc@pipe-d-cursor-512x512-rapid-movement.html * igt@kms_cursor_edge_walk@pipe-d-256x256-left-edge: - shard-iclb: NOTRUN -> [SKIP][73] ([fdo#109278]) +23 similar issues [73]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb8/igt@kms_cursor_edge_walk@pipe-d-256x256-left-edge.html * igt@kms_cursor_legacy@cursorb-vs-flipb-atomic: - shard-tglb: NOTRUN -> [SKIP][74] ([fdo#111825]) +32 similar issues [74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@kms_cursor_legacy@cursorb-vs-flipb-atomic.html - shard-iclb: NOTRUN -> [SKIP][75] ([fdo#109274] / [fdo#109278]) +3 similar issues [75]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb5/igt@kms_cursor_legacy@cursorb-vs-flipb-atomic.html * igt@kms_cursor_legacy@short-flip-before-cursor-toggle: - shard-apl: NOTRUN -> [DMESG-WARN][76] ([i915#62]) +6 similar issues [76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl1/igt@kms_cursor_legacy@short-flip-before-cursor-toggle.html * igt@kms_dither@fb-8bpc-vs-panel-8bpc@edp-1-pipe-a: - shard-tglb: NOTRUN -> [SKIP][77] ([i915#3788]) [77]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@kms_dither@fb-8bpc-vs-panel-8bpc@edp-1-pipe-a.html * igt@kms_fbcon_fbt@fbc-suspend: - shard-tglb: [PASS][78] -> [INCOMPLETE][79] ([i915#2411] / [i915#4173] / [i915#456]) +1 similar issue [78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-tglb3/igt@kms_fbcon_fbt@fbc-suspend.html [79]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb7/igt@kms_fbcon_fbt@fbc-suspend.html - shard-kbl: [PASS][80] -> [INCOMPLETE][81] ([i915#155] / [i915#180] / [i915#636]) [80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-kbl1/igt@kms_fbcon_fbt@fbc-suspend.html [81]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl6/igt@kms_fbcon_fbt@fbc-suspend.html * igt@kms_flip@2x-flip-vs-wf_vblank-interruptible: - shard-iclb: NOTRUN -> [SKIP][82] ([fdo#109274]) +6 similar issues [82]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb1/igt@kms_flip@2x-flip-vs-wf_vblank-interruptible.html * igt@kms_flip@flip-vs-expired-vblank-interruptible@c-hdmi-a2: - shard-glk: [PASS][83] -> [FAIL][84] ([i915#79]) [83]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-glk2/igt@kms_flip@flip-vs-expired-vblank-interruptible@c-hdmi-a2.html [84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-glk1/igt@kms_flip@flip-vs-expired-vblank-interruptible@c-hdmi-a2.html * igt@kms_flip@flip-vs-suspend@b-dp1: - shard-apl: [PASS][85] -> [DMESG-WARN][86] ([i915#180]) [85]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-apl2/igt@kms_flip@flip-vs-suspend@b-dp1.html [86]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl3/igt@kms_flip@flip-vs-suspend@b-dp1.html * igt@kms_frontbuffer_tracking@psr-2p-primscrn-pri-shrfb-draw-mmap-wc: - shard-iclb: NOTRUN -> [SKIP][87] ([fdo#109280]) +16 similar issues [87]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb6/igt@kms_frontbuffer_tracking@psr-2p-primscrn-pri-shrfb-draw-mmap-wc.html * igt@kms_hdr@bpc-switch-suspend: - shard-tglb: [PASS][88] -> [INCOMPLETE][89] ([i915#1373] / [i915#2828] / [i915#4173]) [88]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-tglb1/igt@kms_hdr@bpc-switch-suspend.html [89]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb7/igt@kms_hdr@bpc-switch-suspend.html * igt@kms_plane_alpha_blend@pipe-b-alpha-transparent-fb: - shard-glk: NOTRUN -> [FAIL][90] ([i915#265]) [90]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-glk9/igt@kms_plane_alpha_blend@pipe-b-alpha-transparent-fb.html - shard-apl: NOTRUN -> [FAIL][91] ([i915#265]) [91]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl2/igt@kms_plane_alpha_blend@pipe-b-alpha-transparent-fb.html - shard-kbl: NOTRUN -> [FAIL][92] ([i915#265]) [92]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl3/igt@kms_plane_alpha_blend@pipe-b-alpha-transparent-fb.html * igt@kms_plane_alpha_blend@pipe-c-alpha-7efc: - shard-kbl: NOTRUN -> [FAIL][93] ([fdo#108145] / [i915#265]) +4 similar issues [93]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl7/igt@kms_plane_alpha_blend@pipe-c-alpha-7efc.html * igt@kms_plane_alpha_blend@pipe-c-alpha-basic: - shard-apl: NOTRUN -> [FAIL][94] ([fdo#108145] / [i915#265]) +3 similar issues [94]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl1/igt@kms_plane_alpha_blend@pipe-c-alpha-basic.html * igt@kms_plane_alpha_blend@pipe-c-constant-alpha-max: - shard-glk: NOTRUN -> [FAIL][95] ([fdo#108145] / [i915#265]) +1 similar issue [95]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-glk4/igt@kms_plane_alpha_blend@pipe-c-constant-alpha-max.html * igt@kms_plane_cursor@pipe-d-viewport-size-256: - shard-glk: NOTRUN -> [SKIP][96] ([fdo#109271]) +67 similar issues [96]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-glk3/igt@kms_plane_cursor@pipe-d-viewport-size-256.html * igt@kms_plane_lowres@pipe-a-tiling-y: - shard-iclb: NOTRUN -> [SKIP][97] ([i915#3536]) +1 similar issue [97]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb7/igt@kms_plane_lowres@pipe-a-tiling-y.html * igt@kms_plane_lowres@pipe-b-tiling-none: - shard-tglb: NOTRUN -> [SKIP][98] ([i915#3536]) +3 similar issues [98]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb5/igt@kms_plane_lowres@pipe-b-tiling-none.html * igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-2: - shard-glk: NOTRUN -> [SKIP][99] ([fdo#109271] / [i915#658]) [99]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-glk3/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-2.html * igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-4: - shard-tglb: NOTRUN -> [SKIP][100] ([i915#2920]) +2 similar issues [100]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-4.html * igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-4: - shard-apl: NOTRUN -> [SKIP][101] ([fdo#109271] / [i915#658]) +3 similar issues [101]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl6/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-4.html * igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-2: - shard-kbl: NOTRUN -> [SKIP][102] ([fdo#109271] / [i915#658]) [102]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl3/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-2.html * igt@kms_psr@psr2_primary_mmap_cpu: - shard-iclb: NOTRUN -> [SKIP][103] ([fdo#109441]) +4 similar issues [103]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb4/igt@kms_psr@psr2_primary_mmap_cpu.html * igt@kms_psr@psr2_sprite_mmap_cpu: - shard-tglb: NOTRUN -> [FAIL][104] ([i915#132] / [i915#3467]) +3 similar issues [104]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb2/igt@kms_psr@psr2_sprite_mmap_cpu.html * igt@kms_psr@psr2_sprite_plane_onoff: - shard-iclb: [PASS][105] -> [SKIP][106] ([fdo#109441]) [105]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-iclb2/igt@kms_psr@psr2_sprite_plane_onoff.html [106]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb1/igt@kms_psr@psr2_sprite_plane_onoff.html * igt@kms_rotation_crc@primary-yf-tiled-reflect-x-0: - shard-tglb: NOTRUN -> [SKIP][107] ([fdo#111615]) +6 similar issues [107]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb1/igt@kms_rotation_crc@primary-yf-tiled-reflect-x-0.html * igt@kms_setmode@basic: - shard-snb: NOTRUN -> [FAIL][108] ([i915#31]) [108]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-snb2/igt@kms_setmode@basic.html * igt@kms_vblank@pipe-a-ts-continuation-suspend: - shard-kbl: [PASS][109] -> [DMESG-WARN][110] ([i915#180] / [i915#295]) [109]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-kbl1/igt@kms_vblank@pipe-a-ts-continuation-suspend.html [110]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl4/igt@kms_vblank@pipe-a-ts-continuation-suspend.html * igt@kms_vblank@pipe-d-ts-continuation-idle: - shard-apl: NOTRUN -> [SKIP][111] ([fdo#109271]) +284 similar issues [111]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl2/igt@kms_vblank@pipe-d-ts-continuation-idle.html * igt@kms_vblank@pipe-d-wait-idle: - shard-kbl: NOTRUN -> [SKIP][112] ([fdo#109271] / [i915#533]) +1 similar issue [112]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl3/igt@kms_vblank@pipe-d-wait-idle.html - shard-apl: NOTRUN -> [SKIP][113] ([fdo#109271] / [i915#533]) +2 similar issues [113]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl7/igt@kms_vblank@pipe-d-wait-idle.html * igt@kms_writeback@writeback-fb-id: - shard-glk: NOTRUN -> [SKIP][114] ([fdo#109271] / [i915#2437]) [114]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-glk3/igt@kms_writeback@writeback-fb-id.html - shard-tglb: NOTRUN -> [SKIP][115] ([i915#2437]) [115]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@kms_writeback@writeback-fb-id.html * igt@kms_writeback@writeback-pixel-formats: - shard-kbl: NOTRUN -> [SKIP][116] ([fdo#109271] / [i915#2437]) [116]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl6/igt@kms_writeback@writeback-pixel-formats.html - shard-apl: NOTRUN -> [SKIP][117] ([fdo#109271] / [i915#2437]) [117]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl7/igt@kms_writeback@writeback-pixel-formats.html * igt@nouveau_crc@pipe-c-source-rg: - shard-iclb: NOTRUN -> [SKIP][118] ([i915#2530]) +1 similar issue [118]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb6/igt@nouveau_crc@pipe-c-source-rg.html - shard-tglb: NOTRUN -> [SKIP][119] ([i915#2530]) [119]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb8/igt@nouveau_crc@pipe-c-source-rg.html * igt@perf_pmu@event-wait@rcs0: - shard-tglb: NOTRUN -> [SKIP][120] ([fdo#112283]) [120]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@perf_pmu@event-wait@rcs0.html * igt@prime_nv_pcopy@test3_5: - shard-tglb: NOTRUN -> [SKIP][121] ([fdo#109291]) +2 similar issues [121]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@prime_nv_pcopy@test3_5.html * igt@sysfs_clients@fair-3: - shard-kbl: NOTRUN -> [SKIP][122] ([fdo#109271] / [i915#2994]) [122]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl6/igt@sysfs_clients@fair-3.html * igt@sysfs_clients@recycle-many: - shard-apl: NOTRUN -> [SKIP][123] ([fdo#109271] / [i915#2994]) +2 similar issues [123]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl6/igt@sysfs_clients@recycle-many.html #### Possible fixes #### * igt@gem_eio@unwedge-stress: - shard-iclb: [TIMEOUT][124] ([i915#2369] / [i915#2481] / [i915#3070]) -> [PASS][125] [124]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-iclb5/igt@gem_eio@unwedge-stress.html [125]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb8/igt@gem_eio@unwedge-stress.html * igt@gem_exec_fair@basic-none@vcs1: - shard-kbl: [FAIL][126] ([i915#2842]) -> [PASS][127] [126]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-kbl6/igt@gem_exec_fair@basic-none@vcs1.html [127]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl1/igt@gem_exec_fair@basic-none@vcs1.html * igt@gem_exec_fair@basic-pace@rcs0: - shard-tglb: [FAIL][128] ([i915#2842]) -> [PASS][129] [128]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-tglb5/igt@gem_exec_fair@basic-pace@rcs0.html [129]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@gem_exec_fair@basic-pace@rcs0.html * igt@gem_exec_fair@basic-pace@vecs0: - shard-iclb: [FAIL][130] ([i915#2842]) -> [PASS][131] [130]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-iclb2/igt@gem_exec_fair@basic-pace@vecs0.html [131]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb2/igt@gem_exec_fair@basic-pace@vecs0.html * igt@kms_flip@flip-vs-suspend-interruptible@a-dp1: - shard-apl: [DMESG-WARN][132] ([i915#180]) -> [PASS][133] +2 similar issues [132]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-apl2/igt@kms_flip@flip-vs-suspend-interruptible@a-dp1.html [133]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl7/igt@kms_flip@flip-vs-suspend-interruptible@a-dp1.html * igt@kms_flip@flip-vs-suspend-interruptible@a-edp1: - shard-tglb: [INCOMPLETE][134] ([i915#2411] / [i915#4173] / [i915#456]) -> [PASS][135] [134]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-tglb7/igt@kms_flip@flip-vs-suspend-interruptible@a-edp1.html [135]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb2/igt@kms_flip@flip-vs-su == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/index.html [-- Attachment #2: Type: text/html, Size: 33916 bytes --] ^ permalink raw reply [flat|nested] 16+ messages in thread
* [igt-dev] ✓ Fi.CI.IGT: success for tests/kms_hdr: Fix failure to read output_bpc on AMD hardware 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 ` (2 preceding siblings ...) 2021-10-04 14:08 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork @ 2021-10-04 15:36 ` Patchwork 3 siblings, 0 replies; 16+ messages in thread From: Patchwork @ 2021-10-04 15:36 UTC (permalink / raw) To: Stylon Wang; +Cc: igt-dev [-- Attachment #1: Type: text/plain, Size: 30278 bytes --] == Series Details == Series: tests/kms_hdr: Fix failure to read output_bpc on AMD hardware URL : https://patchwork.freedesktop.org/series/95313/ State : success == Summary == CI Bug Log - changes from IGT_6229_full -> IGTPW_6274_full ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/index.html Known issues ------------ Here are the changes found in IGTPW_6274_full that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_ctx_persistence@legacy-engines-queued: - shard-snb: NOTRUN -> [SKIP][1] ([fdo#109271] / [i915#1099]) +7 similar issues [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-snb6/igt@gem_ctx_persistence@legacy-engines-queued.html * igt@gem_eio@unwedge-stress: - shard-snb: NOTRUN -> [FAIL][2] ([i915#3354]) [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-snb2/igt@gem_eio@unwedge-stress.html * igt@gem_exec_fair@basic-deadline: - shard-kbl: [PASS][3] -> [FAIL][4] ([i915#2846]) [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-kbl4/igt@gem_exec_fair@basic-deadline.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl6/igt@gem_exec_fair@basic-deadline.html - shard-apl: NOTRUN -> [FAIL][5] ([i915#2846]) [5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl7/igt@gem_exec_fair@basic-deadline.html * igt@gem_exec_fair@basic-none-solo@rcs0: - shard-kbl: NOTRUN -> [FAIL][6] ([i915#2842]) [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl4/igt@gem_exec_fair@basic-none-solo@rcs0.html * igt@gem_exec_fair@basic-pace-solo@rcs0: - shard-kbl: [PASS][7] -> [FAIL][8] ([i915#2842]) [7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-kbl3/igt@gem_exec_fair@basic-pace-solo@rcs0.html [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl6/igt@gem_exec_fair@basic-pace-solo@rcs0.html * igt@gem_exec_fair@basic-pace@vcs1: - shard-tglb: [PASS][9] -> [FAIL][10] ([i915#2842]) [9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-tglb5/igt@gem_exec_fair@basic-pace@vcs1.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@gem_exec_fair@basic-pace@vcs1.html * igt@gem_exec_fair@basic-pace@vecs0: - shard-glk: [PASS][11] -> [FAIL][12] ([i915#2842]) +2 similar issues [11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-glk7/igt@gem_exec_fair@basic-pace@vecs0.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-glk5/igt@gem_exec_fair@basic-pace@vecs0.html * igt@gem_exec_fair@basic-throttle@rcs0: - shard-tglb: NOTRUN -> [FAIL][13] ([i915#2842]) [13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb5/igt@gem_exec_fair@basic-throttle@rcs0.html * igt@gem_exec_flush@basic-batch-kernel-default-cmd: - shard-snb: NOTRUN -> [SKIP][14] ([fdo#109271]) +484 similar issues [14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-snb6/igt@gem_exec_flush@basic-batch-kernel-default-cmd.html - shard-iclb: NOTRUN -> [SKIP][15] ([fdo#109313]) [15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb8/igt@gem_exec_flush@basic-batch-kernel-default-cmd.html - shard-tglb: NOTRUN -> [SKIP][16] ([fdo#109313]) [16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb8/igt@gem_exec_flush@basic-batch-kernel-default-cmd.html * igt@gem_exec_reloc@basic-wc-cpu-active: - shard-apl: [PASS][17] -> [DMESG-WARN][18] ([i915#62]) +6 similar issues [17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-apl3/igt@gem_exec_reloc@basic-wc-cpu-active.html [18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl1/igt@gem_exec_reloc@basic-wc-cpu-active.html * igt@gem_huc_copy@huc-copy: - shard-tglb: [PASS][19] -> [SKIP][20] ([i915#2190]) [19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-tglb5/igt@gem_huc_copy@huc-copy.html [20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb6/igt@gem_huc_copy@huc-copy.html * igt@gem_render_copy@y-tiled-to-vebox-linear: - shard-iclb: NOTRUN -> [SKIP][21] ([i915#768]) [21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb2/igt@gem_render_copy@y-tiled-to-vebox-linear.html * igt@gem_userptr_blits@input-checking: - shard-apl: NOTRUN -> [DMESG-WARN][22] ([i915#3002]) [22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl6/igt@gem_userptr_blits@input-checking.html * igt@gen3_render_linear_blits: - shard-tglb: NOTRUN -> [SKIP][23] ([fdo#109289]) +2 similar issues [23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb8/igt@gen3_render_linear_blits.html * igt@gen3_render_mixed_blits: - shard-iclb: NOTRUN -> [SKIP][24] ([fdo#109289]) [24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb4/igt@gen3_render_mixed_blits.html * igt@gen9_exec_parse@bb-chained: - shard-tglb: NOTRUN -> [SKIP][25] ([i915#2856]) [25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb2/igt@gen9_exec_parse@bb-chained.html * igt@i915_pm_backlight@fade_with_suspend: - shard-tglb: [PASS][26] -> [INCOMPLETE][27] ([i915#4173] / [i915#456]) [26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-tglb1/igt@i915_pm_backlight@fade_with_suspend.html [27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb7/igt@i915_pm_backlight@fade_with_suspend.html * igt@i915_pm_dc@dc6-dpms: - shard-kbl: NOTRUN -> [FAIL][28] ([i915#454]) [28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl3/igt@i915_pm_dc@dc6-dpms.html - shard-tglb: NOTRUN -> [FAIL][29] ([i915#454]) [29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb6/igt@i915_pm_dc@dc6-dpms.html * igt@i915_pm_rpm@gem-execbuf-stress-pc8: - shard-iclb: NOTRUN -> [SKIP][30] ([fdo#109293] / [fdo#109506]) [30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb3/igt@i915_pm_rpm@gem-execbuf-stress-pc8.html - shard-tglb: NOTRUN -> [SKIP][31] ([fdo#109506] / [i915#2411]) [31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb2/igt@i915_pm_rpm@gem-execbuf-stress-pc8.html * igt@kms_atomic_transition@plane-all-modeset-transition: - shard-iclb: NOTRUN -> [SKIP][32] ([i915#1769]) [32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb6/igt@kms_atomic_transition@plane-all-modeset-transition.html * igt@kms_big_fb@linear-32bpp-rotate-180: - shard-glk: [PASS][33] -> [DMESG-WARN][34] ([i915#118] / [i915#95]) +2 similar issues [33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-glk5/igt@kms_big_fb@linear-32bpp-rotate-180.html [34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-glk9/igt@kms_big_fb@linear-32bpp-rotate-180.html * igt@kms_big_fb@x-tiled-16bpp-rotate-90: - shard-iclb: NOTRUN -> [SKIP][35] ([fdo#110725] / [fdo#111614]) [35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb1/igt@kms_big_fb@x-tiled-16bpp-rotate-90.html * igt@kms_big_fb@x-tiled-8bpp-rotate-270: - shard-tglb: NOTRUN -> [SKIP][36] ([fdo#111614]) +1 similar issue [36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@kms_big_fb@x-tiled-8bpp-rotate-270.html * igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0-hflip: - shard-kbl: NOTRUN -> [SKIP][37] ([fdo#109271] / [i915#3777]) [37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl6/igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0-hflip.html * igt@kms_big_fb@yf-tiled-64bpp-rotate-0: - shard-iclb: NOTRUN -> [SKIP][38] ([fdo#110723]) [38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb1/igt@kms_big_fb@yf-tiled-64bpp-rotate-0.html * igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0-hflip: - shard-apl: NOTRUN -> [SKIP][39] ([fdo#109271] / [i915#3777]) +3 similar issues [39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl8/igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0-hflip.html * igt@kms_big_joiner@2x-modeset: - shard-iclb: NOTRUN -> [SKIP][40] ([i915#2705]) [40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb1/igt@kms_big_joiner@2x-modeset.html - shard-tglb: NOTRUN -> [SKIP][41] ([i915#2705]) [41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@kms_big_joiner@2x-modeset.html * igt@kms_ccs@pipe-a-bad-pixel-format-y_tiled_gen12_mc_ccs: - shard-tglb: NOTRUN -> [SKIP][42] ([i915#3689] / [i915#3886]) +1 similar issue [42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb1/igt@kms_ccs@pipe-a-bad-pixel-format-y_tiled_gen12_mc_ccs.html * igt@kms_ccs@pipe-a-bad-rotation-90-y_tiled_gen12_rc_ccs_cc: - shard-kbl: NOTRUN -> [SKIP][43] ([fdo#109271] / [i915#3886]) +8 similar issues [43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl3/igt@kms_ccs@pipe-a-bad-rotation-90-y_tiled_gen12_rc_ccs_cc.html * igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_rc_ccs_cc: - shard-apl: NOTRUN -> [SKIP][44] ([fdo#109271] / [i915#3886]) +12 similar issues [44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl3/igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_rc_ccs_cc.html * igt@kms_ccs@pipe-a-random-ccs-data-yf_tiled_ccs: - shard-tglb: NOTRUN -> [SKIP][45] ([i915#3689]) +14 similar issues [45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb5/igt@kms_ccs@pipe-a-random-ccs-data-yf_tiled_ccs.html * igt@kms_ccs@pipe-c-bad-pixel-format-y_tiled_gen12_rc_ccs_cc: - shard-glk: NOTRUN -> [SKIP][46] ([fdo#109271] / [i915#3886]) [46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-glk9/igt@kms_ccs@pipe-c-bad-pixel-format-y_tiled_gen12_rc_ccs_cc.html - shard-iclb: NOTRUN -> [SKIP][47] ([fdo#109278] / [i915#3886]) [47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb4/igt@kms_ccs@pipe-c-bad-pixel-format-y_tiled_gen12_rc_ccs_cc.html * igt@kms_chamelium@dp-hpd-fast: - shard-glk: NOTRUN -> [SKIP][48] ([fdo#109271] / [fdo#111827]) +6 similar issues [48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-glk6/igt@kms_chamelium@dp-hpd-fast.html * igt@kms_chamelium@hdmi-audio: - shard-iclb: NOTRUN -> [SKIP][49] ([fdo#109284] / [fdo#111827]) +6 similar issues [49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb8/igt@kms_chamelium@hdmi-audio.html * igt@kms_chamelium@hdmi-edid-change-during-suspend: - shard-apl: NOTRUN -> [SKIP][50] ([fdo#109271] / [fdo#111827]) +21 similar issues [50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl3/igt@kms_chamelium@hdmi-edid-change-during-suspend.html * igt@kms_chamelium@hdmi-hpd-enable-disable-mode: - shard-snb: NOTRUN -> [SKIP][51] ([fdo#109271] / [fdo#111827]) +24 similar issues [51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-snb6/igt@kms_chamelium@hdmi-hpd-enable-disable-mode.html * igt@kms_chamelium@hdmi-hpd-for-each-pipe: - shard-kbl: NOTRUN -> [SKIP][52] ([fdo#109271] / [fdo#111827]) +21 similar issues [52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl6/igt@kms_chamelium@hdmi-hpd-for-each-pipe.html * igt@kms_color@pipe-d-ctm-blue-to-red: - shard-iclb: NOTRUN -> [SKIP][53] ([fdo#109278] / [i915#1149]) [53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb4/igt@kms_color@pipe-d-ctm-blue-to-red.html * igt@kms_color_chamelium@pipe-b-ctm-limited-range: - shard-tglb: NOTRUN -> [SKIP][54] ([fdo#109284] / [fdo#111827]) +6 similar issues [54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@kms_color_chamelium@pipe-b-ctm-limited-range.html * igt@kms_color_chamelium@pipe-d-ctm-blue-to-red: - shard-iclb: NOTRUN -> [SKIP][55] ([fdo#109278] / [fdo#109284] / [fdo#111827]) [55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb2/igt@kms_color_chamelium@pipe-d-ctm-blue-to-red.html * igt@kms_concurrent@pipe-d: - shard-tglb: NOTRUN -> [FAIL][56] ([i915#1385]) [56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb6/igt@kms_concurrent@pipe-d.html * igt@kms_content_protection@dp-mst-lic-type-0: - shard-iclb: NOTRUN -> [SKIP][57] ([i915#3116]) [57]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb8/igt@kms_content_protection@dp-mst-lic-type-0.html - shard-tglb: NOTRUN -> [SKIP][58] ([i915#3116]) [58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb7/igt@kms_content_protection@dp-mst-lic-type-0.html * igt@kms_content_protection@legacy: - shard-kbl: NOTRUN -> [TIMEOUT][59] ([i915#1319]) +1 similar issue [59]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl3/igt@kms_content_protection@legacy.html - shard-apl: NOTRUN -> [TIMEOUT][60] ([i915#1319]) [60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl7/igt@kms_content_protection@legacy.html * igt@kms_content_protection@lic: - shard-tglb: NOTRUN -> [SKIP][61] ([fdo#111828]) [61]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb5/igt@kms_content_protection@lic.html * igt@kms_cursor_crc@pipe-a-cursor-512x512-rapid-movement: - shard-iclb: NOTRUN -> [SKIP][62] ([fdo#109278] / [fdo#109279]) +2 similar issues [62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb6/igt@kms_cursor_crc@pipe-a-cursor-512x512-rapid-movement.html * igt@kms_cursor_crc@pipe-a-cursor-suspend: - shard-kbl: [PASS][63] -> [DMESG-WARN][64] ([i915#180]) +2 similar issues [63]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-kbl1/igt@kms_cursor_crc@pipe-a-cursor-suspend.html [64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl7/igt@kms_cursor_crc@pipe-a-cursor-suspend.html * igt@kms_cursor_crc@pipe-b-cursor-32x10-random: - shard-tglb: NOTRUN -> [SKIP][65] ([i915#3359]) +3 similar issues [65]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb8/igt@kms_cursor_crc@pipe-b-cursor-32x10-random.html * igt@kms_cursor_crc@pipe-b-cursor-alpha-opaque: - shard-apl: NOTRUN -> [FAIL][66] ([i915#3444]) [66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl3/igt@kms_cursor_crc@pipe-b-cursor-alpha-opaque.html - shard-kbl: NOTRUN -> [FAIL][67] ([i915#3444]) [67]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl6/igt@kms_cursor_crc@pipe-b-cursor-alpha-opaque.html * igt@kms_cursor_crc@pipe-d-cursor-256x256-onscreen: - shard-kbl: NOTRUN -> [SKIP][68] ([fdo#109271]) +208 similar issues [68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl4/igt@kms_cursor_crc@pipe-d-cursor-256x256-onscreen.html * igt@kms_cursor_crc@pipe-d-cursor-32x32-onscreen: - shard-tglb: NOTRUN -> [SKIP][69] ([i915#3319]) +3 similar issues [69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb5/igt@kms_cursor_crc@pipe-d-cursor-32x32-onscreen.html * igt@kms_cursor_crc@pipe-d-cursor-512x512-rapid-movement: - shard-tglb: NOTRUN -> [SKIP][70] ([fdo#109279] / [i915#3359]) +2 similar issues [70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb1/igt@kms_cursor_crc@pipe-d-cursor-512x512-rapid-movement.html * igt@kms_cursor_edge_walk@pipe-d-256x256-left-edge: - shard-iclb: NOTRUN -> [SKIP][71] ([fdo#109278]) +23 similar issues [71]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb8/igt@kms_cursor_edge_walk@pipe-d-256x256-left-edge.html * igt@kms_cursor_legacy@cursorb-vs-flipb-atomic: - shard-tglb: NOTRUN -> [SKIP][72] ([fdo#111825]) +32 similar issues [72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@kms_cursor_legacy@cursorb-vs-flipb-atomic.html - shard-iclb: NOTRUN -> [SKIP][73] ([fdo#109274] / [fdo#109278]) +3 similar issues [73]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb5/igt@kms_cursor_legacy@cursorb-vs-flipb-atomic.html * igt@kms_cursor_legacy@short-flip-before-cursor-toggle: - shard-apl: NOTRUN -> [DMESG-WARN][74] ([i915#62]) +6 similar issues [74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl1/igt@kms_cursor_legacy@short-flip-before-cursor-toggle.html * igt@kms_dither@fb-8bpc-vs-panel-8bpc@edp-1-pipe-a: - shard-tglb: NOTRUN -> [SKIP][75] ([i915#3788]) [75]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@kms_dither@fb-8bpc-vs-panel-8bpc@edp-1-pipe-a.html * igt@kms_fbcon_fbt@fbc-suspend: - shard-tglb: [PASS][76] -> [INCOMPLETE][77] ([i915#2411] / [i915#4173] / [i915#456]) +1 similar issue [76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-tglb3/igt@kms_fbcon_fbt@fbc-suspend.html [77]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb7/igt@kms_fbcon_fbt@fbc-suspend.html - shard-kbl: [PASS][78] -> [INCOMPLETE][79] ([i915#155] / [i915#180] / [i915#636]) [78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-kbl1/igt@kms_fbcon_fbt@fbc-suspend.html [79]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl6/igt@kms_fbcon_fbt@fbc-suspend.html * igt@kms_flip@2x-flip-vs-wf_vblank-interruptible: - shard-iclb: NOTRUN -> [SKIP][80] ([fdo#109274]) +6 similar issues [80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb1/igt@kms_flip@2x-flip-vs-wf_vblank-interruptible.html * igt@kms_flip@flip-vs-expired-vblank-interruptible@c-hdmi-a2: - shard-glk: [PASS][81] -> [FAIL][82] ([i915#79]) [81]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-glk2/igt@kms_flip@flip-vs-expired-vblank-interruptible@c-hdmi-a2.html [82]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-glk1/igt@kms_flip@flip-vs-expired-vblank-interruptible@c-hdmi-a2.html * igt@kms_flip@flip-vs-suspend@b-dp1: - shard-apl: [PASS][83] -> [DMESG-WARN][84] ([i915#180]) [83]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-apl2/igt@kms_flip@flip-vs-suspend@b-dp1.html [84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl3/igt@kms_flip@flip-vs-suspend@b-dp1.html * igt@kms_frontbuffer_tracking@psr-2p-primscrn-pri-shrfb-draw-mmap-wc: - shard-iclb: NOTRUN -> [SKIP][85] ([fdo#109280]) +16 similar issues [85]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb6/igt@kms_frontbuffer_tracking@psr-2p-primscrn-pri-shrfb-draw-mmap-wc.html * igt@kms_hdr@bpc-switch-suspend: - shard-tglb: [PASS][86] -> [INCOMPLETE][87] ([i915#1373] / [i915#2828] / [i915#4173]) [86]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-tglb1/igt@kms_hdr@bpc-switch-suspend.html [87]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb7/igt@kms_hdr@bpc-switch-suspend.html * igt@kms_lease@invalid-create-leases: - shard-kbl: NOTRUN -> [FAIL][88] ([i915#4262]) [88]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl6/igt@kms_lease@invalid-create-leases.html - shard-apl: NOTRUN -> [FAIL][89] ([i915#4262]) [89]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl7/igt@kms_lease@invalid-create-leases.html * igt@kms_plane_alpha_blend@pipe-b-alpha-transparent-fb: - shard-glk: NOTRUN -> [FAIL][90] ([i915#265]) [90]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-glk9/igt@kms_plane_alpha_blend@pipe-b-alpha-transparent-fb.html - shard-apl: NOTRUN -> [FAIL][91] ([i915#265]) [91]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl2/igt@kms_plane_alpha_blend@pipe-b-alpha-transparent-fb.html - shard-kbl: NOTRUN -> [FAIL][92] ([i915#265]) [92]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl3/igt@kms_plane_alpha_blend@pipe-b-alpha-transparent-fb.html * igt@kms_plane_alpha_blend@pipe-c-alpha-7efc: - shard-kbl: NOTRUN -> [FAIL][93] ([fdo#108145] / [i915#265]) +4 similar issues [93]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl7/igt@kms_plane_alpha_blend@pipe-c-alpha-7efc.html * igt@kms_plane_alpha_blend@pipe-c-alpha-basic: - shard-apl: NOTRUN -> [FAIL][94] ([fdo#108145] / [i915#265]) +3 similar issues [94]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl1/igt@kms_plane_alpha_blend@pipe-c-alpha-basic.html * igt@kms_plane_alpha_blend@pipe-c-constant-alpha-max: - shard-glk: NOTRUN -> [FAIL][95] ([fdo#108145] / [i915#265]) +1 similar issue [95]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-glk4/igt@kms_plane_alpha_blend@pipe-c-constant-alpha-max.html * igt@kms_plane_cursor@pipe-d-viewport-size-256: - shard-glk: NOTRUN -> [SKIP][96] ([fdo#109271]) +67 similar issues [96]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-glk3/igt@kms_plane_cursor@pipe-d-viewport-size-256.html * igt@kms_plane_lowres@pipe-a-tiling-y: - shard-iclb: NOTRUN -> [SKIP][97] ([i915#3536]) +1 similar issue [97]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb7/igt@kms_plane_lowres@pipe-a-tiling-y.html * igt@kms_plane_lowres@pipe-b-tiling-none: - shard-tglb: NOTRUN -> [SKIP][98] ([i915#3536]) +3 similar issues [98]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb5/igt@kms_plane_lowres@pipe-b-tiling-none.html * igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-2: - shard-glk: NOTRUN -> [SKIP][99] ([fdo#109271] / [i915#658]) [99]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-glk3/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-2.html * igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-4: - shard-tglb: NOTRUN -> [SKIP][100] ([i915#2920]) +2 similar issues [100]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-4.html * igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-4: - shard-apl: NOTRUN -> [SKIP][101] ([fdo#109271] / [i915#658]) +3 similar issues [101]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl6/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-4.html * igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-2: - shard-kbl: NOTRUN -> [SKIP][102] ([fdo#109271] / [i915#658]) [102]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl3/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-2.html * igt@kms_psr@psr2_primary_mmap_cpu: - shard-iclb: NOTRUN -> [SKIP][103] ([fdo#109441]) +4 similar issues [103]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb4/igt@kms_psr@psr2_primary_mmap_cpu.html * igt@kms_psr@psr2_sprite_mmap_cpu: - shard-tglb: NOTRUN -> [FAIL][104] ([i915#132] / [i915#3467]) +3 similar issues [104]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb2/igt@kms_psr@psr2_sprite_mmap_cpu.html * igt@kms_psr@psr2_sprite_plane_onoff: - shard-iclb: [PASS][105] -> [SKIP][106] ([fdo#109441]) [105]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-iclb2/igt@kms_psr@psr2_sprite_plane_onoff.html [106]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb1/igt@kms_psr@psr2_sprite_plane_onoff.html * igt@kms_rotation_crc@primary-yf-tiled-reflect-x-0: - shard-tglb: NOTRUN -> [SKIP][107] ([fdo#111615]) +6 similar issues [107]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb1/igt@kms_rotation_crc@primary-yf-tiled-reflect-x-0.html * igt@kms_setmode@basic: - shard-snb: NOTRUN -> [FAIL][108] ([i915#31]) [108]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-snb2/igt@kms_setmode@basic.html * igt@kms_vblank@pipe-a-ts-continuation-suspend: - shard-kbl: [PASS][109] -> [DMESG-WARN][110] ([i915#180] / [i915#295]) [109]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-kbl1/igt@kms_vblank@pipe-a-ts-continuation-suspend.html [110]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl4/igt@kms_vblank@pipe-a-ts-continuation-suspend.html * igt@kms_vblank@pipe-d-ts-continuation-idle: - shard-apl: NOTRUN -> [SKIP][111] ([fdo#109271]) +284 similar issues [111]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl2/igt@kms_vblank@pipe-d-ts-continuation-idle.html * igt@kms_vblank@pipe-d-wait-idle: - shard-kbl: NOTRUN -> [SKIP][112] ([fdo#109271] / [i915#533]) +1 similar issue [112]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl3/igt@kms_vblank@pipe-d-wait-idle.html - shard-apl: NOTRUN -> [SKIP][113] ([fdo#109271] / [i915#533]) +2 similar issues [113]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl7/igt@kms_vblank@pipe-d-wait-idle.html * igt@kms_writeback@writeback-fb-id: - shard-glk: NOTRUN -> [SKIP][114] ([fdo#109271] / [i915#2437]) [114]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-glk3/igt@kms_writeback@writeback-fb-id.html - shard-tglb: NOTRUN -> [SKIP][115] ([i915#2437]) [115]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@kms_writeback@writeback-fb-id.html * igt@kms_writeback@writeback-pixel-formats: - shard-kbl: NOTRUN -> [SKIP][116] ([fdo#109271] / [i915#2437]) [116]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl6/igt@kms_writeback@writeback-pixel-formats.html - shard-apl: NOTRUN -> [SKIP][117] ([fdo#109271] / [i915#2437]) [117]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl7/igt@kms_writeback@writeback-pixel-formats.html * igt@nouveau_crc@pipe-c-source-rg: - shard-iclb: NOTRUN -> [SKIP][118] ([i915#2530]) +1 similar issue [118]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb6/igt@nouveau_crc@pipe-c-source-rg.html - shard-tglb: NOTRUN -> [SKIP][119] ([i915#2530]) [119]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb8/igt@nouveau_crc@pipe-c-source-rg.html * igt@perf_pmu@event-wait@rcs0: - shard-tglb: NOTRUN -> [SKIP][120] ([fdo#112283]) [120]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@perf_pmu@event-wait@rcs0.html * igt@prime_nv_pcopy@test3_5: - shard-tglb: NOTRUN -> [SKIP][121] ([fdo#109291]) +2 similar issues [121]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@prime_nv_pcopy@test3_5.html * igt@sysfs_clients@fair-3: - shard-kbl: NOTRUN -> [SKIP][122] ([fdo#109271] / [i915#2994]) [122]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl6/igt@sysfs_clients@fair-3.html * igt@sysfs_clients@recycle-many: - shard-apl: NOTRUN -> [SKIP][123] ([fdo#109271] / [i915#2994]) +2 similar issues [123]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl6/igt@sysfs_clients@recycle-many.html #### Possible fixes #### * igt@gem_eio@unwedge-stress: - shard-iclb: [TIMEOUT][124] ([i915#2369] / [i915#2481] / [i915#3070]) -> [PASS][125] [124]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-iclb5/igt@gem_eio@unwedge-stress.html [125]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb8/igt@gem_eio@unwedge-stress.html * igt@gem_exec_fair@basic-none@vcs1: - shard-kbl: [FAIL][126] ([i915#2842]) -> [PASS][127] [126]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-kbl6/igt@gem_exec_fair@basic-none@vcs1.html [127]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl1/igt@gem_exec_fair@basic-none@vcs1.html * igt@gem_exec_fair@basic-pace@rcs0: - shard-tglb: [FAIL][128] ([i915#2842]) -> [PASS][129] [128]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-tglb5/igt@gem_exec_fair@basic-pace@rcs0.html [129]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@gem_exec_fair@basic-pace@rcs0.html * igt@gem_exec_fair@basic-pace@vecs0: - shard-iclb: [FAIL][130] ([i915#2842]) -> [PASS][131] [130]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-iclb2/igt@gem_exec_fair@basic-pace@vecs0.html [131]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb2/igt@gem_exec_fair@basic-pace@vecs0.html * igt@kms_flip@flip-vs-suspend-interruptible@a-dp1: - shard-apl: [DMESG-WARN][132] ([i915#180]) -> [PASS][133] +2 similar issues [132]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-apl2/igt@kms_flip@flip-vs-suspend-interruptible@a-dp1.html [133]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl7/igt@kms_flip@flip-vs-suspend-interruptible@a-dp1.html * igt@kms_flip@flip-vs-suspend-interruptible@a-edp1: - shard-tglb: [INCOMPLETE][134] ([i915#2411] / [i915#4173] / [i915#456]) -> [PASS][135] [134]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-tglb7/igt@kms_flip@flip-vs-suspend-interruptible@a-edp1.html [135]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb2/igt@kms_flip@flip-vs-suspend-interruptible@a-edp1.html * igt@kms_flip@flip-vs-suspend@c-dp1: - shard-kbl: [DMESG-WARN][136] ([i915#180]) -> [PASS][137] +5 similar issues [136]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6229/shard-kbl7/igt@kms_flip@flip-vs-suspend@c-dp1.html [137]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl3/igt@kms_flip@flip-vs-suspend@c-dp1.html * igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile: == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/index.html [-- Attachment #2: Type: text/html, Size: 33934 bytes --] ^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2021-10-08 6:33 UTC | newest] Thread overview: 16+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 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 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
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.