Skip to contentSkip to conversation

tests/kms_hdr: Fix failure to read output_bpc on AMD hardware

PATCH Superseded Stylon Wang 9 participants 16 messages Oct 1, 2021 – Oct 8, 2021

v1 of 2 Superseded Latest is v2 →

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 tests/kms_hdr: Fix failure to read output_bpc on AMD hardware

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.

---
 tests/kms_hdr.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
tests/kms_hdr.c +1 -1
index 5b8529c8..a4983b9a 100644
@@ -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;
Signature · 1 line
2.32.0
#1 lore raw

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

Quoted 27 lines · 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.

---
 tests/kms_hdr.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
tests/kms_hdr.c +1 -1
index 5b8529c8..a4983b9a 100644
@@ -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;
Signature · 1 line
2.32.0
Signature · 2 lines
Rodrigo Siqueira
https://siqueira.tech
#2 lore raw
Quoted 6 lines · Rodrigo Siqueira

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.

Signature · 1 line
Petri Latvala
Quoted 36 lines

Thanks
Siqueira

Quoted 27 lines · 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.

---
 tests/kms_hdr.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
tests/kms_hdr.c +1 -1
index 5b8529c8..a4983b9a 100644
@@ -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;
Signature · 1 line
2.32.0
Signature · 2 lines
Rodrigo Siqueira
https://siqueira.tech
#3 lore raw
Quoted 10 lines · Petri Latvala
Quoted 6 lines · Rodrigo Siqueira

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

Quoted 41 lines
Signature · 2 lines
-- 
Petri Latvala
Quoted 36 lines

Thanks
Siqueira

Quoted 27 lines · 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.

---
 tests/kms_hdr.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
tests/kms_hdr.c +1 -1
index 5b8529c8..a4983b9a 100644
@@ -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;
Signature · 1 line
2.32.0
Signature · 2 lines
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
Signature · 2 lines
Rodrigo Siqueira
https://siqueira.tech
#4 lore raw

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 <[email protected]>
Sent: Monday, October 4, 2021 7:19 AM
To: Latvala, Petri <[email protected]>; Vudum, Lakshminarayana <[email protected]>
Cc: Stylon Wang <[email protected]>; [email protected]; [email protected]
Subject: Re: [PATCH i-g-t] tests/kms_hdr: Fix failure to read output_bpc on AMD hardware

Quoted 15 lines · Petri Latvala
Quoted 5 lines · Rodrigo Siqueira

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?

Quoted 8 lines

1.
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpa
tchwork.freedesktop.org%2Fseries%2F95313%2F&amp;data=04%7C01%7CRodri go.Siqueira%40amd.com%7C43b5d7ab0731407a2f9008d987278e48%7C3dd8961fe 4884e608e11a82d994e183d%7C0%7C0%7C637689426230154758%7CUnknown%7CTWF pbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI 6Mn0%3D%7C1000&amp;sdata=NIEF78%2B74hVRdQPhcCEPVlp4To3iDjkpkkv8VjSC0 %2BE%3D&amp;reserved=0

Quoted 2 lines

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

Quoted 47 lines

--
Petri Latvala

Quoted 42 lines

Thanks
Siqueira

Quoted 26 lines · 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.

---
 tests/kms_hdr.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
tests/kms_hdr.c index renamed from tests/kms_hdr.c +0 -0

5b8529c8..a4983b9a 100644

tests/kms_hdr.c +2 -2
@@ -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;
--
Quoted 2 lines

2.32.0

--
Rodrigo Siqueira
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsi
queira.tech%2F&amp;data=04%7C01%7CRodrigo.Siqueira%40amd.com%7C43b5d 7ab0731407a2f9008d987278e48%7C3dd8961fe4884e608e11a82d994e183d%7C0%7 C0%7C637689426230154758%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAi LCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=VvCE WNlBkZnAm9M1JYeheIlVaUVMkeDiallVz0uUM8o%3D&amp;reserved=0

--
Rodrigo Siqueira
https://siqueira.tech

#5 lore raw

+Simon.

Quoted 125 lines

-----Original Message-----
From: igt-dev <[email protected]> On Behalf Of Vudum, Lakshminarayana
Sent: maanantai 4. lokakuuta 2021 18.42
To: Rodrigo Siqueira <[email protected]>; Latvala, Petri <[email protected]>
Cc: Stylon Wang <[email protected]>; [email protected]; [email protected]
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-

Quoted 1 line

master.fd, &mcl) == -22

Lakshmi.

-----Original Message-----
From: Rodrigo Siqueira <[email protected]>
Sent: Monday, October 4, 2021 7:19 AM
To: Latvala, Petri <[email protected]>; Vudum, Lakshminarayana <[email protected]>
Cc: Stylon Wang <[email protected]>; [email protected]; [email protected]
Subject: Re: [PATCH i-g-t] tests/kms_hdr: Fix failure to read output_bpc on AMD hardware

Quoted 10 lines · Petri Latvala
Quoted 9 lines · Rodrigo Siqueira

Hi Lakshminarayana and Petri,

I noticed that the CI was not triggered for this patch [1]. Do you know why? Is it possible to trigger it?

1.
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpa
tchwork.freedesktop.org%2Fseries%2F95313%2F&amp;data=04%7C01%7CRodri

go.Siqueira%40amd.com%7C43b5d7ab0731407a2f9008d987278e48%7C3dd8961fe

Quoted 1 line
Quoted 1 line

4884e608e11a82d994e183d%7C0%7C0%7C637689426230154758%7CUnknown%7C TWF

Quoted 2 lines
Quoted 2 lines

pbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI

6Mn0%3D%7C1000&amp;sdata=NIEF78%2B74hVRdQPhcCEPVlp4To3iDjkpkkv8VjSC0

Quoted 4 lines
Quoted 1 line

%2BE%3D&amp;reserved=0

CI was down for a bit due to server cert issues, testing that and the other affected series happening in a bit.

Thanks Petri,

I noticed that the CI was triggered for this patch.

Lakshminarayana,

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

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

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

Thanks
Siqueira

Quoted 21 lines

--
Petri Latvala

Quoted 16 lines

Thanks
Siqueira

Quoted 11 lines · 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.

---
 tests/kms_hdr.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Quoted 5 lines
Quoted 5 lines

tests/kms_hdr.c static void test_bpc_switch_on_output(data_t *data,

Quoted 5 lines
tests/kms_hdr.c index renamed from tests/kms_hdr.c +0 -0

5b8529c8..a4983b9a 100644

tests/kms_hdr.c +0 -0
@@ -217,7 +217,7 @@ static void test_bpc_switch_on_output(data_t *data,

igt_output_t *output,

Quoted 3 lines
Quoted 3 lines

tests/kms_hdr.c static void test_bpc_switch_on_output(data_t *data, igt_output_t *output,

Quoted 3 lines
tests/kms_hdr.c +0 -0
 		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);

Quoted 1 line
Quoted 1 line

tests/kms_hdr.c static void test_bpc_switch_on_output(data_t *data, · line 220

Quoted 1 line
tests/kms_hdr.c +0 -1
-		ret = igt_display_try_commit_atomic(display,

DRM_MODE_ATOMIC_TEST_ONLY, NULL);

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
tests/kms_hdr.c +2 -0
+		ret = igt_display_try_commit_atomic(display,
+DRM_MODE_ATOMIC_ALLOW_MODESET, NULL);
 		if (!ret) {
 			data->w = afb.width;
 			data->h = afb.height;
Quoted 8 lines
Quoted 8 lines
Quoted 3 lines

--
2.32.0

--
Rodrigo Siqueira
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsi

queira.tech%2F&amp;data=04%7C01%7CRodrigo.Siqueira%40amd.com%7C43b5d

Quoted 1 line
Quoted 1 line

7ab0731407a2f9008d987278e48%7C3dd8961fe4884e608e11a82d994e183d%7C0% 7

Quoted 1 line
Quoted 1 line

C0%7C637689426230154758%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwM DAi

Quoted 2 lines
Quoted 2 lines

LCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=VvCE WNlBkZnAm9M1JYeheIlVaUVMkeDiallVz0uUM8o%3D&amp;reserved=0

--
Rodrigo Siqueira
https://siqueira.tech

Reviewed-by
#6 lore raw

Hi,

I noticed that the patch looks good from the CI perspective [1] and I don't see any problem on that, so:

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

Quoted 127 lines · Jani

+Simon.

Quoted 125 lines

-----Original Message-----
From: igt-dev <[email protected]> On Behalf Of Vudum, Lakshminarayana
Sent: maanantai 4. lokakuuta 2021 18.42
To: Rodrigo Siqueira <[email protected]>; Latvala, Petri <[email protected]>
Cc: Stylon Wang <[email protected]>; [email protected]; [email protected]
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&amp;data=04%7C01%7CRodrigo.Siqueira%40amd.com%7C8c3f22f5fa6c48f0166808d9875c3133%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637689652302229936%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=sK0l9HWKszTbO75F%2FTaS7Swv%2FegjwVP0M8q%2FRlFg0Ys%3D&amp;reserved=0 and re-reported. igt@kms_lease@invalid-create-leases - fail - Failed assertion: create_lease(data-

Quoted 1 line

master.fd, &mcl) == -22

Lakshmi.

-----Original Message-----
From: Rodrigo Siqueira <[email protected]>
Sent: Monday, October 4, 2021 7:19 AM
To: Latvala, Petri <[email protected]>; Vudum, Lakshminarayana <[email protected]>
Cc: Stylon Wang <[email protected]>; [email protected]; [email protected]
Subject: Re: [PATCH i-g-t] tests/kms_hdr: Fix failure to read output_bpc on AMD hardware

Quoted 10 lines · Petri Latvala
Quoted 9 lines · Rodrigo Siqueira

Hi Lakshminarayana and Petri,

I noticed that the CI was not triggered for this patch [1]. Do you know why? Is it possible to trigger it?

1.
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpa
tchwork.freedesktop.org%2Fseries%2F95313%2F&amp;data=04%7C01%7CRodri

go.Siqueira%40amd.com%7C43b5d7ab0731407a2f9008d987278e48%7C3dd8961fe

Quoted 1 line
Quoted 1 line

4884e608e11a82d994e183d%7C0%7C0%7C637689426230154758%7CUnknown%7C TWF

Quoted 2 lines
Quoted 2 lines

pbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI

6Mn0%3D%7C1000&amp;sdata=NIEF78%2B74hVRdQPhcCEPVlp4To3iDjkpkkv8VjSC0

Quoted 4 lines
Quoted 1 line

%2BE%3D&amp;reserved=0

CI was down for a bit due to server cert issues, testing that and the other affected series happening in a bit.

Thanks Petri,

I noticed that the CI was triggered for this patch.

Lakshminarayana,

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

https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatchwork.freedesktop.org%2Fseries%2F95313%2F&amp;data=04%7C01%7CRodrigo.Siqueira%40amd.com%7C8c3f22f5fa6c48f0166808d9875c3133%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637689652302229936%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=zJ74sNT%2B6yOcR3%2BH6w%2B2A8tYx84ge1c4ij%2FpCkOQoT8%3D&amp;reserved=0

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

Thanks
Siqueira

Quoted 21 lines

--
Petri Latvala

Quoted 16 lines

Thanks
Siqueira

Quoted 11 lines · 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.

---
 tests/kms_hdr.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Quoted 5 lines
Quoted 5 lines

tests/kms_hdr.c static void test_bpc_switch_on_output(data_t *data,

Quoted 5 lines
tests/kms_hdr.c index renamed from tests/kms_hdr.c +0 -0

5b8529c8..a4983b9a 100644

tests/kms_hdr.c +0 -0
@@ -217,7 +217,7 @@ static void test_bpc_switch_on_output(data_t *data,

igt_output_t *output,

Quoted 3 lines
Quoted 3 lines

tests/kms_hdr.c static void test_bpc_switch_on_output(data_t *data, igt_output_t *output,

Quoted 3 lines
tests/kms_hdr.c +0 -0
 		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);

Quoted 1 line
Quoted 1 line

tests/kms_hdr.c static void test_bpc_switch_on_output(data_t *data, · line 220

Quoted 1 line
tests/kms_hdr.c +0 -1
-		ret = igt_display_try_commit_atomic(display,

DRM_MODE_ATOMIC_TEST_ONLY, NULL);

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
tests/kms_hdr.c +2 -0
+		ret = igt_display_try_commit_atomic(display,
+DRM_MODE_ATOMIC_ALLOW_MODESET, NULL);
 		if (!ret) {
 			data->w = afb.width;
 			data->h = afb.height;
Quoted 8 lines
Quoted 8 lines
Quoted 3 lines

--
2.32.0

--
Rodrigo Siqueira
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsi

queira.tech%2F&amp;data=04%7C01%7CRodrigo.Siqueira%40amd.com%7C43b5d

Quoted 1 line
Quoted 1 line

7ab0731407a2f9008d987278e48%7C3dd8961fe4884e608e11a82d994e183d%7C0% 7

Quoted 1 line
Quoted 1 line

C0%7C637689426230154758%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwM DAi

Quoted 2 lines
Quoted 2 lines

LCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=VvCE WNlBkZnAm9M1JYeheIlVaUVMkeDiallVz0uUM8o%3D&amp;reserved=0

--
Rodrigo Siqueira
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsiqueira.tech%2F&amp;data=04%7C01%7CRodrigo.Siqueira%40amd.com%7C8c3f22f5fa6c48f0166808d9875c3133%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637689652302229936%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=ahQpaPpbX2AQtBhiQJU2zF25iWO%2FnWU3Vnx%2F640yRfU%3D&amp;reserved=0

Signature · 2 lines
Rodrigo Siqueira
https://siqueira.tech
#7 lore raw

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

#8 lore raw

[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 <[email protected]>
Sent: Thursday, October 7, 2021 10:49 AM
To: Siqueira, Rodrigo <[email protected]>
Cc: Saarinen, Jani <[email protected]>; Vudum, Lakshminarayana <[email protected]>; Latvala, Petri <[email protected]>; Wang, Chao-kai (Stylon) <[email protected]>; [email protected] <[email protected]>; Choi, Nicholas <[email protected]>; Mark Yacoub <[email protected]>; Wentland, Harry <[email protected]>; Kazlauskas, Nicholas <[email protected]>
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

#9 lore raw
Quoted 5 lines · Nicholas

[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

Quoted 18 lines

Regards,
Nicholas Kazlauskas
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
*From:* Simon Ser <[email protected]>
*Sent:* Thursday, October 7, 2021 10:49 AM
*To:* Siqueira, Rodrigo <[email protected]>
*Cc:* Saarinen, Jani <[email protected]>; Vudum, Lakshminarayana <[email protected]>; Latvala, Petri <[email protected]>; Wang, Chao-kai (Stylon) <[email protected]>; [email protected] <[email protected]>; Choi, Nicholas <[email protected]>; Mark Yacoub <[email protected]>; Wentland, Harry <[email protected]>; Kazlauskas, Nicholas <[email protected]> *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

#10 lore raw
Quoted 11 lines · Harry Wentland
Quoted 5 lines · Nicholas

[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

Quoted 7 lines

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

Quoted 21 lines
Quoted 20 lines

Regards,
Nicholas Kazlauskas
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
*From:* Simon Ser <[email protected]>
*Sent:* Thursday, October 7, 2021 10:49 AM
*To:* Siqueira, Rodrigo <[email protected]>
*Cc:* Saarinen, Jani <[email protected]>; Vudum, Lakshminarayana <[email protected]>; Latvala, Petri <[email protected]>; Wang, Chao-kai (Stylon) <[email protected]>; [email protected] <[email protected]>; Choi, Nicholas <[email protected]>; Mark Yacoub <[email protected]>; Wentland, Harry <[email protected]>; Kazlauskas, Nicholas <[email protected]> *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

#11 lore raw

[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 <[email protected]>
Sent: October 7, 2021 10:59 PM
To: Wentland, Harry <[email protected]>; Siqueira, Rodrigo <[email protected]>; Simon Ser <[email protected]>
Cc: Saarinen, Jani <[email protected]>; Vudum, Lakshminarayana <[email protected]>; Latvala, Petri <[email protected]>; Wang, Chao-kai (Stylon) <[email protected]>; [email protected] <[email protected]>; Choi, Nicholas <[email protected]>; Mark Yacoub <[email protected]>
Subject: Re: [PATCH i-g-t] tests/kms_hdr: Fix failure to read output_bpc on AMD hardware

Quoted 11 lines · Harry Wentland
Quoted 5 lines · Nicholas

[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

Quoted 7 lines

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

Quoted 21 lines
Quoted 20 lines

Regards,
Nicholas Kazlauskas
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
*From:* Simon Ser <[email protected]>
*Sent:* Thursday, October 7, 2021 10:49 AM
*To:* Siqueira, Rodrigo <[email protected]>
*Cc:* Saarinen, Jani <[email protected]>; Vudum, Lakshminarayana <[email protected]>; Latvala, Petri <[email protected]>; Wang, Chao-kai (Stylon) <[email protected]>; [email protected] <[email protected]>; Choi, Nicholas <[email protected]>; Mark Yacoub <[email protected]>; Wentland, Harry <[email protected]>; Kazlauskas, Nicholas <[email protected]> *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

#12 lore raw
Quoted 4 lines · Chao-kai (Stylon)

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.

#13 lore raw

[igt-dev] ✓ Fi.CI.BAT: success for tests/kms_hdr: Fix failure to read output_bpc on AMD hardware

In reply to Stylon Wang
== Series Details ==

== 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/[email protected]

* 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/[email protected]

* 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/[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

#### 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@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/fi-pnv-d510/igt@gem_exec_parallel@[email protected]

* 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@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/fi-bdw-samus/igt@[email protected]
- 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@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/fi-tgl-1115g4/igt@[email protected]

* 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@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/fi-snb-2600/igt@i915_selftest@[email protected]

* 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@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/fi-kbl-7500u/igt@[email protected]

* 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@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/fi-cml-u2/igt@[email protected]

[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

#14 lore raw

[igt-dev] ✗ Fi.CI.IGT: failure for tests/kms_hdr: Fix failure to read output_bpc on AMD hardware

In reply to Stylon Wang
== Series Details ==

== 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@[email protected]
- shard-apl: NOTRUN -> [FAIL][2]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl7/igt@[email protected]

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@[email protected]

* 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@[email protected]

* 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@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl6/igt@[email protected]
- shard-apl: NOTRUN -> [FAIL][7] ([i915#2846])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl7/igt@[email protected]

* 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@[email protected]

* 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@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl6/igt@gem_exec_fair@[email protected]

* 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@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@gem_exec_fair@[email protected]

* 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@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-glk5/igt@gem_exec_fair@[email protected]

* 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@[email protected]

* 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@[email protected]
- shard-iclb: NOTRUN -> [SKIP][17] ([fdo#109313])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb8/igt@[email protected]
- shard-tglb: NOTRUN -> [SKIP][18] ([fdo#109313])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb8/igt@[email protected]

* 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@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl1/igt@[email protected]

* 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@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb6/igt@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]
- shard-tglb: NOTRUN -> [FAIL][31] ([i915#454])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb6/igt@[email protected]

* 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@[email protected]
- shard-tglb: NOTRUN -> [SKIP][33] ([fdo#109506] / [i915#2411])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb2/igt@[email protected]

* 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@[email protected]

* 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@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-glk9/igt@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]
- shard-tglb: NOTRUN -> [SKIP][43] ([i915#2705])
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]
- shard-tglb: NOTRUN -> [SKIP][60] ([i915#3116])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb7/igt@[email protected]

* 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@[email protected]
- shard-apl: NOTRUN -> [TIMEOUT][62] ([i915#1319])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl7/igt@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl7/igt@[email protected]

* 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@[email protected]

* 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@[email protected]
- shard-kbl: NOTRUN -> [FAIL][69] ([i915#3444])
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl6/igt@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]
- 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb7/igt@[email protected]
- 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@[email protected]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl6/igt@[email protected]

* 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@[email protected]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-glk1/igt@kms_flip@[email protected]

* 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@[email protected]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl3/igt@kms_flip@[email protected]

* 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@[email protected]
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb7/igt@[email protected]

* 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@[email protected]
- shard-apl: NOTRUN -> [FAIL][91] ([i915#265])
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl2/igt@[email protected]
- shard-kbl: NOTRUN -> [FAIL][92] ([i915#265])
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl3/igt@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl4/igt@[email protected]

* 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@[email protected]

* 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@[email protected]
- 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@[email protected]

* 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@[email protected]
- shard-tglb: NOTRUN -> [SKIP][115] ([i915#2437])
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@[email protected]

* 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@[email protected]
- shard-apl: NOTRUN -> [SKIP][117] ([fdo#109271] / [i915#2437])
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl7/igt@[email protected]

* 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@[email protected]
- shard-tglb: NOTRUN -> [SKIP][119] ([i915#2530])
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb8/igt@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

#### 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@[email protected]
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb8/igt@[email protected]

* 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@[email protected]
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl1/igt@gem_exec_fair@[email protected]

* 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@[email protected]
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@gem_exec_fair@[email protected]

* 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@[email protected]
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb2/igt@gem_exec_fair@[email protected]

* 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@[email protected]
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl7/igt@kms_flip@[email protected]

* 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@[email protected]
[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

#15 lore raw

[igt-dev] ✓ Fi.CI.IGT: success for tests/kms_hdr: Fix failure to read output_bpc on AMD hardware

In reply to Stylon Wang
== Series Details ==

== 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@[email protected]

* 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@[email protected]

* 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@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl6/igt@[email protected]
- shard-apl: NOTRUN -> [FAIL][5] ([i915#2846])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl7/igt@[email protected]

* 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@[email protected]

* 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@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl6/igt@gem_exec_fair@[email protected]

* 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@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@gem_exec_fair@[email protected]

* 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@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-glk5/igt@gem_exec_fair@[email protected]

* 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@[email protected]

* 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@[email protected]
- shard-iclb: NOTRUN -> [SKIP][15] ([fdo#109313])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb8/igt@[email protected]
- shard-tglb: NOTRUN -> [SKIP][16] ([fdo#109313])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb8/igt@[email protected]

* 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@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl1/igt@[email protected]

* 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@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb6/igt@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]
- shard-tglb: NOTRUN -> [FAIL][29] ([i915#454])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb6/igt@[email protected]

* 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@[email protected]
- shard-tglb: NOTRUN -> [SKIP][31] ([fdo#109506] / [i915#2411])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb2/igt@[email protected]

* 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@[email protected]

* 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@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-glk9/igt@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]
- shard-tglb: NOTRUN -> [SKIP][41] ([i915#2705])
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]
- shard-tglb: NOTRUN -> [SKIP][58] ([i915#3116])
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb7/igt@[email protected]

* 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@[email protected]
- shard-apl: NOTRUN -> [TIMEOUT][60] ([i915#1319])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl7/igt@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl7/igt@[email protected]

* 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@[email protected]

* 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@[email protected]
- shard-kbl: NOTRUN -> [FAIL][67] ([i915#3444])
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl6/igt@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]
- 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb7/igt@[email protected]
- 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@[email protected]
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl6/igt@[email protected]

* 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@[email protected]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-glk1/igt@kms_flip@[email protected]

* 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@[email protected]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl3/igt@kms_flip@[email protected]

* 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@[email protected]
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb7/igt@[email protected]

* 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@[email protected]
- shard-apl: NOTRUN -> [FAIL][89] ([i915#4262])
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl7/igt@[email protected]

* 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@[email protected]
- shard-apl: NOTRUN -> [FAIL][91] ([i915#265])
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl2/igt@[email protected]
- shard-kbl: NOTRUN -> [FAIL][92] ([i915#265])
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl3/igt@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl4/igt@[email protected]

* 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@[email protected]

* 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@[email protected]
- 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@[email protected]

* 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@[email protected]
- shard-tglb: NOTRUN -> [SKIP][115] ([i915#2437])
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@[email protected]

* 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@[email protected]
- shard-apl: NOTRUN -> [SKIP][117] ([fdo#109271] / [i915#2437])
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl7/igt@[email protected]

* 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@[email protected]
- shard-tglb: NOTRUN -> [SKIP][119] ([i915#2530])
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb8/igt@[email protected]

* 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@[email protected]

* 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@[email protected]

* 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@[email protected]

#### 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@[email protected]
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb8/igt@[email protected]

* 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@[email protected]
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl1/igt@gem_exec_fair@[email protected]

* 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@[email protected]
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb3/igt@gem_exec_fair@[email protected]

* 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@[email protected]
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-iclb2/igt@gem_exec_fair@[email protected]

* 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@[email protected]
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-apl7/igt@kms_flip@[email protected]

* 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@[email protected]
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-tglb2/igt@kms_flip@[email protected]

* 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@[email protected]
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6274/shard-kbl3/igt@kms_flip@[email protected]

* 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