Skip to contentSkip to conversation

Fix issues on benchmarks

PATCH In review Mauro Carvalho Chehab 3 participants 9 messages May 31, 2022 – Jun 14, 2022

lore
Share & tools
lore
#0 lore raw

v2 cover Fix issues on benchmarks

From: Mauro Carvalho Chehab <[email protected]>

There are two benchmarks that aren't work properly:

- gem_blt is not estimating a loop count that would be close to 0.1 ms. The current calculus provide a value that would take ~23 days to complete (tested on ADL-P):

	$ sudo timeout 100 ./build/benchmarks/gem_blt || echo "Timeout!"
	Timeout!

- gem_syslatency crashes with SIGSEGV, if the environment is not ready to use realtime priority. The root cause is that setting realtime now requires some CGroup changes nowadays:

	$ sudo ./build/benchmarks/gem_syslatency
	Received signal SIGSEGV.
	Stack trace:
	 #0 [fatal_sig_handler+0x163]
	 #1 [__sigaction+0x50]
	 #2 [__pthread_clockjoin_ex+0x22]
	 #3 [main+0x346]
	 #4 [__libc_start_call_main+0x80]
	 #5 [__libc_start_main+0x89]
	 #6 [_start+0x25]
	Segmentation fault

This series addresses such issues.

Mauro Carvalho Chehab (3):
benchmarks/gem_blt: fix baseline estimation benchmarks/gem_syslatency: don't die with SIGSEGV benchmarks/gem_syslatency: make realtime mode optional

 benchmarks/gem_blt.c        | 18 +++++-------------
 benchmarks/gem_syslatency.c | 28 +++++++++++++++++++++-------
 2 files changed, 26 insertions(+), 20 deletions(-)
Signature · 1 line
2.36.1
#1 lore raw

PATCH v2 1/3 benchmarks/gem_blt: fix baseline estimation

From: Mauro Carvalho Chehab <[email protected]>

This test is expected to run under a certain time defined by a command line parameter (by default, 2s).

In order to achive the specified time, the baseline() function tries to estimate the value of a counter that will get the minimal amount of interaction to wait for > 0.1s.

However, currently, the baseline estimation is broken, returning a too big number, as it is measuring the memcpy() time, instead of actually gem_execbuf().

Due to that, a default test without passing any command line parameter would take more than 1.5 years to output the first benchmark data!

Fix it by using the same logic that it is inside run() at the baseline time estimation.

Before this patch, baseline could return 399242693. After it, it now return 20. That means an interval of about 120 ms at the code which runs a gem_execbuf() loop, which should be good enough to ensure that the tests won't take too long, and will approximately match the time specified by the excecution parameter '-t'.

---
 benchmarks/gem_blt.c | 18 +++++-------------
 1 file changed, 5 insertions(+), 13 deletions(-)
benchmarks/gem_blt.c +5 -13
index 424ce8e75913..bd8264b4e896 100644
@@ -57,29 +57,21 @@ elapsed(const struct timespec *start, const struct timespec *end)
 	return (end->tv_sec - start->tv_sec) + 1e-9*(end->tv_nsec - start->tv_nsec);
 }
 
-static int baseline(uint64_t bytes, int milliseconds)
+static int baseline(int fd, struct drm_i915_gem_execbuffer2 execbuf, int milliseconds)
 {
 	struct timespec start, end;
-	const int size = 64*1024*1024;
 	int count = 0;
-	void *mem;
-
-	mem = malloc(size);
-	if (mem == NULL)
-		return 1;
 
 	clock_gettime(CLOCK_MONOTONIC, &start);
 	do {
-		memset(mem, count, size);
+		gem_execbuf(fd, &execbuf);
 		count++;
 		clock_gettime(CLOCK_MONOTONIC, &end);
-		if (elapsed(&start, &end) > 0.1)
+		if (elapsed(&start, &end) > (milliseconds / 1000.))
 			break;
 	} while (1);
 
-	free(mem);
-
-	return ceil(1e-3*milliseconds/elapsed(&start, &end) * count * size / bytes);
+	return count;
 }
 
 static int gem_linear_blt(int fd,
@@ -260,7 +252,7 @@ static int run(int object, int batch, int time, int reps, int ncpus, unsigned fl
 		execbuf.flags |= I915_EXEC_NO_RELOC;
 
 	/* Guess how many loops we need for 0.1s */
-	count = baseline((uint64_t)object * batch, 100) / ncpus;
+	count = baseline(fd, execbuf, 100) / ncpus;
 	if (flags & SYNC) {
 		time *= count / 2;
 		count = 1;
Signature · 1 line
2.36.1
#2 lore raw

PATCH v2 2/3 benchmarks/gem_syslatency: don't die with SIGSEGV

In reply to Mauro Carvalho Chehab

From: Mauro Carvalho Chehab <[email protected]>

Fix the pthread_create() logic for it to properly handle temporary issues returned with EAGAIN and ensure that thread creation won't fail, as, if it fails, it will cause a Segmentation fault:

	Received signal SIGSEGV.
	Stack trace:
	 #0 [fatal_sig_handler+0x163]
	 #1 [__sigaction+0x50]
	 #2 [__pthread_clockjoin_ex+0x22]
	 #3 [main+0x346]
	 #4 [__libc_start_call_main+0x80]
	 #5 [__libc_start_main+0x89]
	 #6 [_start+0x25]
	Segmentation fault
---
 benchmarks/gem_syslatency.c | 14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)
benchmarks/gem_syslatency.c +10 -4
index 035ee9346251..4b097e1c9316 100644
@@ -351,7 +351,7 @@ int main(int argc, char **argv)
 	bool leak = false;
 	bool interrupts = false;
 	long batch = 0;
-	int n, c;
+	int ret, n, c;
 
 	while ((c = getopt(argc, argv, "r:t:f:bmni1")) != -1) {
 		switch (c) {
@@ -409,8 +409,11 @@ int main(int argc, char **argv)
 			busy[n].sz = batch;
 			busy[n].leak = leak;
 			busy[n].interrupts = interrupts;
-			pthread_create(&busy[n].thread, &attr,
-				       gem_busyspin, &busy[n]);
+			do {
+				ret = pthread_create(&busy[n].thread, &attr,
+						     gem_busyspin, &busy[n]);
+			} while (ret == EAGAIN);
+			igt_assert_f(!ret, "Can't create task on CPU#%d\n", n);
 		}
 	}
 
@@ -420,7 +423,10 @@ int main(int argc, char **argv)
 	for (n = 0; n < ncpus; n++) {
 		igt_mean_init(&wait[n].mean);
 		bind_cpu(&attr, n);
-		pthread_create(&wait[n].thread, &attr, sys_fn, &wait[n]);
+		do {
+			ret = pthread_create(&wait[n].thread, &attr, sys_fn, &wait[n]);
+		} while (ret == EAGAIN);
+		igt_assert_f(!ret, "Can't create task on CPU#%d\n", n);
 	}
 
 	sleep(time);
Signature · 1 line
2.36.1
#3 lore raw

Re: [igt-dev] [i-g-t, v2, 2/3] benchmarks/gem_syslatency: don't die with SIGSEGV

Quoted 36 lines · Mauro Carvalho Chehab

From: Mauro Carvalho Chehab <[email protected]>

Fix the pthread_create() logic for it to properly handle temporary issues returned with EAGAIN and ensure that thread creation won't fail, as, if it fails, it will cause a Segmentation fault:

	Received signal SIGSEGV.
	Stack trace:
	 #0 [fatal_sig_handler+0x163]
	 #1 [__sigaction+0x50]
	 #2 [__pthread_clockjoin_ex+0x22]
	 #3 [main+0x346]
	 #4 [__libc_start_call_main+0x80]
	 #5 [__libc_start_main+0x89]
	 #6 [_start+0x25]
	Segmentation fault
---
 benchmarks/gem_syslatency.c | 14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)
benchmarks/gem_syslatency.c +1 -1
index 035ee9346251..4b097e1c9316 100644
@@ -351,7 +351,7 @@ int main(int argc, char **argv)
 	bool leak = false;
 	bool interrupts = false;
 	long batch = 0;
-	int n, c;
+	int ret, n, c;
 
 	while ((c = getopt(argc, argv, "r:t:f:bmni1")) != -1) {
 		switch (c) {

benchmarks/gem_syslatency.c int main(int argc, char **argv) · line 415

Quoted 9 lines
benchmarks/gem_syslatency.c +4 -2
@@ -409,8 +409,11 @@ int main(int argc, char **argv)
 			busy[n].sz = batch;
 			busy[n].leak = leak;
 			busy[n].interrupts = interrupts;
-			pthread_create(&busy[n].thread, &attr,
-				       gem_busyspin, &busy[n]);
+			do {
+				ret = pthread_create(&busy[n].thread, &attr,
+						     gem_busyspin, &busy[n]);
+			} while (ret == EAGAIN);

Should we make this loop and wait for other error indefinitly ? imho it is better to make some counter after which it fails ?

benchmarks/gem_syslatency.c int main(int argc, char **argv) · line 429

Quoted 13 lines
benchmarks/gem_syslatency.c +5 -1
+			igt_assert_f(!ret, "Can't create task on CPU#%d\n", n);
 		}
 	}
 
@@ -420,7 +423,10 @@ int main(int argc, char **argv)
 	for (n = 0; n < ncpus; n++) {
 		igt_mean_init(&wait[n].mean);
 		bind_cpu(&attr, n);
-		pthread_create(&wait[n].thread, &attr, sys_fn, &wait[n]);
+		do {
+			ret = pthread_create(&wait[n].thread, &attr, sys_fn, &wait[n]);
+		} while (ret == EAGAIN);
+		igt_assert_f(!ret, "Can't create task on CPU#%d\n", n);

This is the same code, maybe it should be placed in igt lib as a macro or function ?

--
Kamil

Quoted 3 lines
benchmarks/gem_syslatency.c +0 -0
 	}
 
 	sleep(time);
#4 lore raw

PATCH v2 3/3 benchmarks/gem_syslatency: make realtime mode optional

In reply to Mauro Carvalho Chehab

From: Mauro Carvalho Chehab <[email protected]>

Use a logic similar to the one at gem_latency in order to setup the device to realtime, as, depending on the Kernel and on CGroup settings, trying to setup realtime may return EPERM. For more details, see:

https://www.kernel.org/doc/html/latest/scheduler/sched-rt-group.html?highlight=cgroup%20realtime

---
 benchmarks/gem_syslatency.c | 14 +++++++++++---
 1 file changed, 11 insertions(+), 3 deletions(-)
benchmarks/gem_syslatency.c +11 -3
index 4b097e1c9316..db95cbcc6048 100644
@@ -47,6 +47,8 @@
 #include "i915/gem_create.h"
 #include "i915/gem_ring.h"
 
+#define REALTIME	0x1
+
 #define sigev_notify_thread_id _sigev_un._tid
 
 static volatile int done;
@@ -234,7 +236,7 @@ static void bind_cpu(pthread_attr_t *attr, int cpu)
 static void rtprio(pthread_attr_t *attr, int prio)
 {
 #ifdef PTHREAD_EXPLICIT_SCHED
-	struct sched_param param = { .sched_priority = 99 };
+	struct sched_param param = { .sched_priority = prio };
 	pthread_attr_setinheritsched(attr, PTHREAD_EXPLICIT_SCHED);
 	pthread_attr_setschedpolicy(attr, SCHED_FIFO);
 	pthread_attr_setschedparam(attr, &param);
@@ -344,6 +346,7 @@ int main(int argc, char **argv)
 	pthread_t bg_fs = 0;
 	int ncpus = sysconf(_SC_NPROCESSORS_ONLN);
 	igt_stats_t cycles, mean, max;
+	unsigned flags = 0;
 	double min;
 	int time = 10;
 	int field = -1;
@@ -353,7 +356,7 @@ int main(int argc, char **argv)
 	long batch = 0;
 	int ret, n, c;
 
-	while ((c = getopt(argc, argv, "r:t:f:bmni1")) != -1) {
+	while ((c = getopt(argc, argv, "r:t:f:bmni1R")) != -1) {
 		switch (c) {
 		case '1':
 			ncpus = 1;
@@ -374,6 +377,10 @@ int main(int argc, char **argv)
 			/* Duration of each batch (microseconds) */
 			batch = atoi(optarg);
 			break;
+		case 'R':
+			/* Run the producers at RealTime priority */
+			flags |= REALTIME;
+			break;
 		case 'f':
 			/* Select an output field */
 			field = atoi(optarg);
@@ -419,7 +426,8 @@ int main(int argc, char **argv)
 
 	wait = calloc(ncpus, sizeof(*wait));
 	pthread_attr_init(&attr);
-	rtprio(&attr, 99);
+	if (flags & REALTIME)
+		rtprio(&attr, 99);
 	for (n = 0; n < ncpus; n++) {
 		igt_mean_init(&wait[n].mean);
 		bind_cpu(&attr, n);
Signature · 1 line
2.36.1
#5 lore raw

Re: [igt-dev] [i-g-t, v2, 3/3] benchmarks/gem_syslatency: make realtime mode optional

Hi Mauro,

Quoted 5 lines · Mauro Carvalho Chehab

From: Mauro Carvalho Chehab <[email protected]>

Use a logic similar to the one at gem_latency in order to setup the device to realtime, as, depending on the Kernel and on CGroup settings, trying to setup realtime may return EPERM.

All gem_* tests and benchmarks are meant to be run by root. Maybe just add error checks there ?

Quoted 23 lines

For more details, see:

https://www.kernel.org/doc/html/latest/scheduler/sched-rt-group.html?highlight=cgroup%20realtime

---
 benchmarks/gem_syslatency.c | 14 +++++++++++---
 1 file changed, 11 insertions(+), 3 deletions(-)
benchmarks/gem_syslatency.c +2 -0
index 4b097e1c9316..db95cbcc6048 100644
@@ -47,6 +47,8 @@
 #include "i915/gem_create.h"
 #include "i915/gem_ring.h"
 
+#define REALTIME	0x1
+
 #define sigev_notify_thread_id _sigev_un._tid
 
 static volatile int done;

benchmarks/gem_syslatency.c static void bind_cpu(pthread_attr_t *attr, int cpu) · line 239

Quoted 5 lines
benchmarks/gem_syslatency.c +1 -1
@@ -234,7 +236,7 @@ static void bind_cpu(pthread_attr_t *attr, int cpu)
 static void rtprio(pthread_attr_t *attr, int prio)
 {
 #ifdef PTHREAD_EXPLICIT_SCHED
-	struct sched_param param = { .sched_priority = 99 };
+	struct sched_param param = { .sched_priority = prio };

Nice catch.

benchmarks/gem_syslatency.c static void bind_cpu(pthread_attr_t *attr, int cpu) · line 242

Quoted 3 lines
benchmarks/gem_syslatency.c +0 -0
 	pthread_attr_setinheritsched(attr, PTHREAD_EXPLICIT_SCHED);
 	pthread_attr_setschedpolicy(attr, SCHED_FIFO);
 	pthread_attr_setschedparam(attr, &param);

Here there are no error checks.

Quoted 29 lines
benchmarks/gem_syslatency.c +6 -1
@@ -344,6 +346,7 @@ int main(int argc, char **argv)
 	pthread_t bg_fs = 0;
 	int ncpus = sysconf(_SC_NPROCESSORS_ONLN);
 	igt_stats_t cycles, mean, max;
+	unsigned flags = 0;
 	double min;
 	int time = 10;
 	int field = -1;
@@ -353,7 +356,7 @@ int main(int argc, char **argv)
 	long batch = 0;
 	int ret, n, c;
 
-	while ((c = getopt(argc, argv, "r:t:f:bmni1")) != -1) {
+	while ((c = getopt(argc, argv, "r:t:f:bmni1R")) != -1) {
 		switch (c) {
 		case '1':
 			ncpus = 1;
@@ -374,6 +377,10 @@ int main(int argc, char **argv)
 			/* Duration of each batch (microseconds) */
 			batch = atoi(optarg);
 			break;
+		case 'R':
+			/* Run the producers at RealTime priority */
+			flags |= REALTIME;
+			break;
 		case 'f':
 			/* Select an output field */
 			field = atoi(optarg);

benchmarks/gem_syslatency.c int main(int argc, char **argv) · line 430

Quoted 6 lines
benchmarks/gem_syslatency.c +2 -1
@@ -419,7 +426,8 @@ int main(int argc, char **argv)
 
 	wait = calloc(ncpus, sizeof(*wait));
 	pthread_attr_init(&attr);
-	rtprio(&attr, 99);
+	if (flags & REALTIME)
+		rtprio(&attr, 99);

This changes codepath here, imho we should ask Chris about this (added to cc).

Regards,
Kamil

Quoted 3 lines
benchmarks/gem_syslatency.c +0 -0
 	for (n = 0; n < ncpus; n++) {
 		igt_mean_init(&wait[n].mean);
 		bind_cpu(&attr, n);
#6 lore raw

Re: [igt-dev] [i-g-t, v2, 3/3] benchmarks/gem_syslatency: make realtime mode optional

Quoted 11 lines · On Wed, 1 Jun 2022 17:26:51 +0200 Kamil Konieczny…

Hi Mauro,

Quoted 5 lines · Mauro Carvalho Chehab

From: Mauro Carvalho Chehab <[email protected]>

Use a logic similar to the one at gem_latency in order to setup the device to realtime, as, depending on the Kernel and on CGroup settings, trying to setup realtime may return EPERM.

All gem_* tests and benchmarks are meant to be run by root. Maybe just add error checks there ?

igt_runner already checks it (although it doesn't run benchmarks, I guess).

The problem is that, on modern systems, even the root can't set prio 99 without first set cgroup to accept it.

Quoted 31 lines
Quoted 23 lines

For more details, see:

https://www.kernel.org/doc/html/latest/scheduler/sched-rt-group.html?highlight=cgroup%20realtime

---
 benchmarks/gem_syslatency.c | 14 +++++++++++---
 1 file changed, 11 insertions(+), 3 deletions(-)
benchmarks/gem_syslatency.c +2 -0
index 4b097e1c9316..db95cbcc6048 100644
@@ -47,6 +47,8 @@
 #include "i915/gem_create.h"
 #include "i915/gem_ring.h"
 
+#define REALTIME	0x1
+
 #define sigev_notify_thread_id _sigev_un._tid
 
 static volatile int done;

benchmarks/gem_syslatency.c static void bind_cpu(pthread_attr_t *attr, int cpu) · line 239

Quoted 5 lines
benchmarks/gem_syslatency.c +1 -1
@@ -234,7 +236,7 @@ static void bind_cpu(pthread_attr_t *attr, int cpu)
 static void rtprio(pthread_attr_t *attr, int prio)
 {
 #ifdef PTHREAD_EXPLICIT_SCHED
-	struct sched_param param = { .sched_priority = 99 };
+	struct sched_param param = { .sched_priority = prio };  

Nice catch.

Quoted 5 lines

benchmarks/gem_syslatency.c static void bind_cpu(pthread_attr_t *attr, int cpu) · line 242

Quoted 3 lines
benchmarks/gem_syslatency.c +0 -0
 	pthread_attr_setinheritsched(attr, PTHREAD_EXPLICIT_SCHED);
 	pthread_attr_setschedpolicy(attr, SCHED_FIFO);
 	pthread_attr_setschedparam(attr, &param);  

Here there are no error checks.

True. Will add on a next version.

Quoted 31 lines
Quoted 31 lines
benchmarks/gem_syslatency.c +6 -1
@@ -344,6 +346,7 @@ int main(int argc, char **argv)
 	pthread_t bg_fs = 0;
 	int ncpus = sysconf(_SC_NPROCESSORS_ONLN);
 	igt_stats_t cycles, mean, max;
+	unsigned flags = 0;
 	double min;
 	int time = 10;
 	int field = -1;
@@ -353,7 +356,7 @@ int main(int argc, char **argv)
 	long batch = 0;
 	int ret, n, c;
 
-	while ((c = getopt(argc, argv, "r:t:f:bmni1")) != -1) {
+	while ((c = getopt(argc, argv, "r:t:f:bmni1R")) != -1) {
 		switch (c) {
 		case '1':
 			ncpus = 1;
@@ -374,6 +377,10 @@ int main(int argc, char **argv)
 			/* Duration of each batch (microseconds) */
 			batch = atoi(optarg);
 			break;
+		case 'R':
+			/* Run the producers at RealTime priority */
+			flags |= REALTIME;
+			break;
 		case 'f':
 			/* Select an output field */
 			field = atoi(optarg);
@@ -419,7 +426,8 @@ int main(int argc, char **argv)
 
Quoted 8 lines

benchmarks/gem_syslatency.c int main(int argc, char **argv) · line 430

Quoted 5 lines
benchmarks/gem_syslatency.c +2 -1
 	wait = calloc(ncpus, sizeof(*wait));
 	pthread_attr_init(&attr);
-	rtprio(&attr, 99);
+	if (flags & REALTIME)
+		rtprio(&attr, 99);  

This changes codepath here, imho we should ask Chris about this (added to cc).

Sure.

Chris,

Any comments?

Regards,
Mauro

#7 lore raw

Re: [igt-dev] [i-g-t, v2, 3/3] benchmarks/gem_syslatency: make realtime mode optional

In reply to Mauro Carvalho Chehab

Hi Mauro,

Quoted 28 lines · Mauro Carvalho Chehab

From: Mauro Carvalho Chehab <[email protected]>

Use a logic similar to the one at gem_latency in order to setup the device to realtime, as, depending on the Kernel and on CGroup settings, trying to setup realtime may return EPERM. For more details, see:

https://www.kernel.org/doc/html/latest/scheduler/sched-rt-group.html?highlight=cgroup%20realtime

---
 benchmarks/gem_syslatency.c | 14 +++++++++++---
 1 file changed, 11 insertions(+), 3 deletions(-)
benchmarks/gem_syslatency.c +2 -0
index 4b097e1c9316..db95cbcc6048 100644
@@ -47,6 +47,8 @@
 #include "i915/gem_create.h"
 #include "i915/gem_ring.h"
 
+#define REALTIME	0x1
+
 #define sigev_notify_thread_id _sigev_un._tid
 
 static volatile int done;

benchmarks/gem_syslatency.c static void bind_cpu(pthread_attr_t *attr, int cpu) · line 242

Quoted 8 lines
benchmarks/gem_syslatency.c +1 -1
@@ -234,7 +236,7 @@ static void bind_cpu(pthread_attr_t *attr, int cpu)
 static void rtprio(pthread_attr_t *attr, int prio)
 {
 #ifdef PTHREAD_EXPLICIT_SCHED
-	struct sched_param param = { .sched_priority = 99 };
+	struct sched_param param = { .sched_priority = prio };
 	pthread_attr_setinheritsched(attr, PTHREAD_EXPLICIT_SCHED);
 	pthread_attr_setschedpolicy(attr, SCHED_FIFO);
 	pthread_attr_setschedparam(attr, &param);

So the problem still remains here, when you will use -R option it can still fail here, there are no error checks.

Regards,
Kamil

Quoted 38 lines
benchmarks/gem_syslatency.c +8 -2
@@ -344,6 +346,7 @@ int main(int argc, char **argv)
 	pthread_t bg_fs = 0;
 	int ncpus = sysconf(_SC_NPROCESSORS_ONLN);
 	igt_stats_t cycles, mean, max;
+	unsigned flags = 0;
 	double min;
 	int time = 10;
 	int field = -1;
@@ -353,7 +356,7 @@ int main(int argc, char **argv)
 	long batch = 0;
 	int ret, n, c;
 
-	while ((c = getopt(argc, argv, "r:t:f:bmni1")) != -1) {
+	while ((c = getopt(argc, argv, "r:t:f:bmni1R")) != -1) {
 		switch (c) {
 		case '1':
 			ncpus = 1;
@@ -374,6 +377,10 @@ int main(int argc, char **argv)
 			/* Duration of each batch (microseconds) */
 			batch = atoi(optarg);
 			break;
+		case 'R':
+			/* Run the producers at RealTime priority */
+			flags |= REALTIME;
+			break;
 		case 'f':
 			/* Select an output field */
 			field = atoi(optarg);
@@ -419,7 +426,8 @@ int main(int argc, char **argv)
 
 	wait = calloc(ncpus, sizeof(*wait));
 	pthread_attr_init(&attr);
-	rtprio(&attr, 99);
+	if (flags & REALTIME)
+		rtprio(&attr, 99);
 	for (n = 0; n < ncpus; n++) {
 		igt_mean_init(&wait[n].mean);
 		bind_cpu(&attr, n);
#8 lore raw

[igt-dev] ✗ Fi.CI.BAT: failure for Fix issues on benchmarks (rev2)

In reply to Mauro Carvalho Chehab
== Series Details ==

== Series Details ==

Series: Fix issues on benchmarks (rev2)
URL : https://patchwork.freedesktop.org/series/104182/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_11710 -> IGTPW_7194
====================================================

Summary
-------

**FAILURE**

Serious unknown changes coming with IGTPW_7194 absolutely need to be verified manually.

If you think the reported changes have nothing to do with the changes introduced in IGTPW_7194, 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_7194/index.html

Participating hosts (46 -> 47)
------------------------------

Additional (2): fi-icl-u2 bat-dg2-9
Missing (1): bat-dg2-8

Possible new issues
-------------------

Here are the unknown changes that may have been introduced in IGTPW_7194:

### IGT changes ###

#### Possible regressions ####

* igt@kms_force_connector_basic@force-connector-state:
- fi-icl-u2: NOTRUN -> [WARN][1]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7194/fi-icl-u2/igt@[email protected]

#### Suppressed ####

The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.

* igt@gem_exec_suspend@basic-s0@smem:
- {fi-ehl-2}: [PASS][2] -> [DMESG-WARN][3]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11710/fi-ehl-2/igt@gem_exec_suspend@[email protected]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7194/fi-ehl-2/igt@gem_exec_suspend@[email protected]

Known issues
------------

Here are the changes found in IGTPW_7194 that come from known issues:

### IGT changes ###

#### Issues hit ####

* igt@gem_huc_copy@huc-copy:
- fi-icl-u2: NOTRUN -> [SKIP][4] ([i915#2190])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7194/fi-icl-u2/igt@[email protected]

* igt@gem_lmem_swapping@random-engines:
- fi-icl-u2: NOTRUN -> [SKIP][5] ([i915#4613]) +3 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7194/fi-icl-u2/igt@[email protected]

* igt@i915_selftest@live@gt_engines:
- bat-dg1-5: [PASS][6] -> [INCOMPLETE][7] ([i915#4418])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11710/bat-dg1-5/igt@i915_selftest@live@gt_engines.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7194/bat-dg1-5/igt@i915_selftest@live@gt_engines.html

* igt@i915_selftest@live@gt_lrc:
- fi-bsw-n3050: [PASS][8] -> [DMESG-FAIL][9] ([i915#2373])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11710/fi-bsw-n3050/igt@i915_selftest@live@gt_lrc.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7194/fi-bsw-n3050/igt@i915_selftest@live@gt_lrc.html

* igt@i915_selftest@live@hangcheck:
- fi-bdw-5557u: NOTRUN -> [INCOMPLETE][10] ([i915#3921])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7194/fi-bdw-5557u/igt@i915_selftest@[email protected]
- bat-dg1-6: NOTRUN -> [DMESG-FAIL][11] ([i915#4494] / [i915#4957])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7194/bat-dg1-6/igt@i915_selftest@[email protected]

* igt@i915_selftest@live@requests:
- fi-pnv-d510: [PASS][12] -> [DMESG-FAIL][13] ([i915#4528])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11710/fi-pnv-d510/igt@i915_selftest@[email protected]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7194/fi-pnv-d510/igt@i915_selftest@[email protected]

* igt@i915_suspend@basic-s2idle-without-i915:
- bat-dg1-6: NOTRUN -> [INCOMPLETE][14] ([i915#6011])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7194/bat-dg1-6/igt@[email protected]

* igt@i915_suspend@basic-s3-without-i915:
- fi-icl-u2: NOTRUN -> [SKIP][15] ([i915#5903])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7194/fi-icl-u2/igt@[email protected]

* igt@kms_chamelium@common-hpd-after-suspend:
- fi-rkl-11600: NOTRUN -> [SKIP][16] ([fdo#111827])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7194/fi-rkl-11600/igt@[email protected]

* igt@kms_chamelium@hdmi-hpd-fast:
- fi-icl-u2: NOTRUN -> [SKIP][17] ([fdo#111827]) +8 similar issues
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7194/fi-icl-u2/igt@[email protected]

* igt@kms_force_connector_basic@force-load-detect:
- fi-icl-u2: NOTRUN -> [SKIP][18] ([fdo#109285])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7194/fi-icl-u2/igt@[email protected]

* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
- fi-icl-u2: NOTRUN -> [SKIP][19] ([fdo#109278]) +2 similar issues
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7194/fi-icl-u2/igt@[email protected]

* igt@kms_setmode@basic-clone-single-crtc:
- fi-icl-u2: NOTRUN -> [SKIP][20] ([i915#3555])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7194/fi-icl-u2/igt@[email protected]

* igt@prime_vgem@basic-userptr:
- fi-icl-u2: NOTRUN -> [SKIP][21] ([fdo#109295] / [i915#3301])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7194/fi-icl-u2/igt@[email protected]

* igt@runner@aborted:
- fi-pnv-d510: NOTRUN -> [FAIL][22] ([fdo#109271] / [i915#2403] / [i915#4312])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7194/fi-pnv-d510/igt@[email protected]

#### Possible fixes ####

* igt@i915_selftest@live@gt_engines:
- bat-dg1-6: [INCOMPLETE][23] ([i915#4418]) -> [PASS][24]
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11710/bat-dg1-6/igt@i915_selftest@live@gt_engines.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7194/bat-dg1-6/igt@i915_selftest@live@gt_engines.html

* igt@i915_selftest@live@gt_pm:
- fi-tgl-1115g4: [DMESG-FAIL][25] ([i915#3987]) -> [PASS][26]
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11710/fi-tgl-1115g4/igt@i915_selftest@live@gt_pm.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7194/fi-tgl-1115g4/igt@i915_selftest@live@gt_pm.html

* igt@i915_selftest@live@gt_timelines:
- {bat-adlm-1}: [INCOMPLETE][27] ([i915#6132]) -> [PASS][28]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11710/bat-adlm-1/igt@i915_selftest@live@gt_timelines.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7194/bat-adlm-1/igt@i915_selftest@live@gt_timelines.html

* igt@i915_selftest@live@mman:
- fi-bdw-5557u: [INCOMPLETE][29] ([i915#5704]) -> [PASS][30]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11710/fi-bdw-5557u/igt@i915_selftest@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7194/fi-bdw-5557u/igt@i915_selftest@[email protected]

* igt@i915_suspend@basic-s3-without-i915:
- fi-rkl-11600: [INCOMPLETE][31] ([i915#5982]) -> [PASS][32]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11710/fi-rkl-11600/igt@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7194/fi-rkl-11600/igt@[email protected]

{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).

[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278
[fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
[fdo#109295]: https://bugs.freedesktop.org/show_bug.cgi?id=109295
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#1155]: https://gitlab.freedesktop.org/drm/intel/issues/1155
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2373]: https://gitlab.freedesktop.org/drm/intel/issues/2373
[i915#2403]: https://gitlab.freedesktop.org/drm/intel/issues/2403
[i915#3291]: https://gitlab.freedesktop.org/drm/intel/issues/3291
[i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3595]: https://gitlab.freedesktop.org/drm/intel/issues/3595
[i915#3708]: https://gitlab.freedesktop.org/drm/intel/issues/3708
[i915#3921]: https://gitlab.freedesktop.org/drm/intel/issues/3921
[i915#3987]: https://gitlab.freedesktop.org/drm/intel/issues/3987
[i915#4077]: https://gitlab.freedesktop.org/drm/intel/issues/4077
[i915#4079]: https://gitlab.freedesktop.org/drm/intel/issues/4079
[i915#4083]: https://gitlab.freedesktop.org/drm/intel/issues/4083
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
[i915#4212]: https://gitlab.freedesktop.org/drm/intel/issues/4212
[i915#4213]: https://gitlab.freedesktop.org/drm/intel/issues/4213
[i915#4215]: https://gitlab.freedesktop.org/drm/intel/issues/4215
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4418]: https://gitlab.freedesktop.org/drm/intel/issues/4418
[i915#4494]: https://gitlab.freedesktop.org/drm/intel/issues/4494
[i915#4528]: https://gitlab.freedesktop.org/drm/intel/issues/4528
[i915#4579]: https://gitlab.freedesktop.org/drm/intel/issues/4579
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4873]: https://gitlab.freedesktop.org/drm/intel/issues/4873
[i915#4957]: https://gitlab.freedesktop.org/drm/intel/issues/4957
[i915#5190]: https://gitlab.freedesktop.org/drm/intel/issues/5190
[i915#5274]: https://gitlab.freedesktop.org/drm/intel/issues/5274
[i915#5704]: https://gitlab.freedesktop.org/drm/intel/issues/5704
[i915#5763]: https://gitlab.freedesktop.org/drm/intel/issues/5763
[i915#5885]: https://gitlab.freedesktop.org/drm/intel/issues/5885
[i915#5903]: https://gitlab.freedesktop.org/drm/intel/issues/5903
[i915#5982]: https://gitlab.freedesktop.org/drm/intel/issues/5982
[i915#6011]: https://gitlab.freedesktop.org/drm/intel/issues/6011
[i915#6103]: https://gitlab.freedesktop.org/drm/intel/issues/6103
[i915#6132]: https://gitlab.freedesktop.org/drm/intel/issues/6132

Build changes
-------------

* CI: CI-20190529 -> None
* IGT: IGT_6500 -> IGTPW_7194

CI-20190529: 20190529
CI_DRM_11710: d2798c4b9213f0d14080bdeef58e692a2c01a0bf @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_7194: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7194/index.html
IGT_6500: de4c6076a0f38ad3522b08931748f59d59a925ce @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7194/index.html