public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
* [LTP] [PATCH] sched_football: fix false failures on many-CPU systems
@ 2026-04-12 13:05 Soma Das
  2026-04-14 15:54 ` Jan Polensky
  2026-04-14 16:59 ` [LTP] " linuxtestproject.agent
  0 siblings, 2 replies; 10+ messages in thread
From: Soma Das @ 2026-04-12 13:05 UTC (permalink / raw)
  To: ltp; +Cc: somadas1

[-- Attachment #1: Type: text/plain, Size: 7787 bytes --]

Test logs attached — 40+ consecutive runs passing after fix on 80-CPU 
ppc64le LPAR. ---
 From 3fc17dd06907785f5b1b65aebfe150c8ac73d54a Mon Sep 17 00:00:00 2001
From: Soma Das <somadas1@linux.ibm.com>
Date: Sun, 12 Apr 2026 13:13:08 +0000
Subject: [PATCH] sched_football: fix false failures on many-CPU systems
On large SMP systems with CONFIG_RT_GROUP_SCHED=n, four independent
issues cause false failures.
1. RT throttling freezes all SCHED_FIFO threads simultaneously. On
release, the kernel does not always reschedule the highest-priority
thread first on every CPU, so offense briefly runs and increments
the_ball before defense is rescheduled. Fix by saving and disabling
sched_rt_runtime_us in setup and restoring it in a new cleanup
callback.
2. Offense and defense threads were unpinned, allowing the scheduler
to migrate them freely. An offense thread could land on a CPU with
no defense thread present and run unchecked. Fix by passing a CPU
index as the thread arg and calling sched_setaffinity() at thread
start. Pairs are distributed round-robin (i % ncpus) so each
offense thread shares its CPU with a defense thread.
3. game_over was never reset between iterations, causing all threads
to exit immediately on reruns (-i N), making the test a no-op.
Fix by resetting both kickoff_flag and game_over at the top of
do_test().
4. sched_setscheduler() failure for the referee was silently ignored.
If the call fails the test produces meaningless results. Fix by
checking the return value and calling tst_brk(TBROK) on failure.
Signed-off-by: Soma Das <somadas1@linux.ibm.com>
---
.../func/sched_football/sched_football.c | 83 +++++++++++++++++--
1 file changed, 78 insertions(+), 5 deletions(-)
diff --git a/testcases/realtime/func/sched_football/sched_football.c 
b/testcases/realtime/func/sched_football/sched_football.c
index 2cb85322d..43bac9468 100644
--- a/testcases/realtime/func/sched_football/sched_football.c
+++ b/testcases/realtime/func/sched_football/sched_football.c
@@ -3,6 +3,15 @@
* Copyright © International Business Machines Corp., 2007, 2008
* Copyright (c) 2024 Petr Vorel <pvorel@suse.cz>
* Author: John Stultz <jstultz@google.com>
+ *
+ * On many-CPU systems with CONFIG_RT_GROUP_SCHED=n, the global RT
+ * bandwidth limit (sched_rt_runtime_us, default 950000/1000000)
+ * periodically freezes *all* SCHED_FIFO tasks together and then
+ * releases them together. During the release window the kernel does
+ * not always re-pick defense first on every CPU, so lower-priority
+ * offense threads briefly get scheduled and bump the_ball, breaking
+ * the invariant the test checks. Disable RT throttling for the
+ * duration of the test and restore it in cleanup.
*/
/*\
@@ -46,6 +55,8 @@ static int players_per_team = 0;
static int game_length = DEF_GAME_LENGTH;
static tst_atomic_t kickoff_flag;
static tst_atomic_t game_over;
+/* saved before disabling RT throttling so cleanup can restore the 
original value */
+static long saved_rt_runtime_us;
static char *str_game_length;
static char *str_players_per_team;
@@ -77,9 +88,24 @@ void *thread_fan(void *arg LTP_ATTRIBUTE_UNUSED)
}
/* This is the defensive team. They're trying to block the offense */
-void *thread_defense(void *arg LTP_ATTRIBUTE_UNUSED)
+void *thread_defense(void *arg)
{
+ struct thread *t = (struct thread *)arg;
+ int cpu = (int)(intptr_t)t->arg;
+ cpu_set_t cpuset;
+
prctl(PR_SET_NAME, "defense", 0, 0, 0);
+
+ /*
+ * Pin to the designated CPU. When fans (higher priority) temporarily
+ * displace this thread, it re-occupies the same CPU immediately on fan
+ * sleep — no cross-CPU migration delay that could let offense in.
+ */
+ CPU_ZERO(&cpuset);
+ CPU_SET(cpu, &cpuset);
+ if (sched_setaffinity(0, sizeof(cpuset), &cpuset) != 0)
+ tst_brk(TBROK | TERRNO, "sched_setaffinity failed for defense on CPU 
%d", cpu);
+
pthread_barrier_wait(&start_barrier);
while (!tst_atomic_load(&kickoff_flag))
;
@@ -92,9 +118,24 @@ void *thread_defense(void *arg LTP_ATTRIBUTE_UNUSED)
}
/* This is the offensive team. They're trying to move the ball */
-void *thread_offense(void *arg LTP_ATTRIBUTE_UNUSED)
+void *thread_offense(void *arg)
{
+ struct thread *t = (struct thread *)arg;
+ int cpu = (int)(intptr_t)t->arg;
+ cpu_set_t cpuset;
+
prctl(PR_SET_NAME, "offense", 0, 0, 0);
+
+ /*
+ * Pin to the same CPU as the paired defense thread so there is
+ * always a higher-priority defense thread locally available to
+ * preempt this one without requiring cross-CPU migration.
+ */
+ CPU_ZERO(&cpuset);
+ CPU_SET(cpu, &cpuset);
+ if (sched_setaffinity(0, sizeof(cpuset), &cpuset) != 0)
+ tst_brk(TBROK | TERRNO, "sched_setaffinity failed for offense on CPU 
%d", cpu);
+
pthread_barrier_wait(&start_barrier);
while (!tst_atomic_load(&kickoff_flag))
sched_yield();
@@ -154,11 +195,15 @@ static void do_test(void)
{
struct sched_param param;
int priority;
+ int ncpus;
int i;
if (players_per_team == 0)
players_per_team = get_numcpus();
+ /* actual CPU count used for affinity assignment, independent of 
players_per_team */
+ ncpus = get_numcpus();
+
tst_res(TINFO, "players_per_team: %d game_length: %d",
players_per_team, game_length);
@@ -167,8 +212,13 @@ static void do_test(void)
/* We're the ref, so set our priority right */
param.sched_priority = sched_get_priority_min(SCHED_FIFO) + 80;
- sched_setscheduler(0, SCHED_FIFO, &param);
+ /* fail loudly if we can't elevate to SCHED_FIFO — test results would 
be meaningless */
+ if (sched_setscheduler(0, SCHED_FIFO, &param) != 0)
+ tst_brk(TBROK | TERRNO, "sched_setscheduler(SCHED_FIFO) failed");
+
+ /* Reset flags so the test is safe to re-run (e.g. with -i N) */
tst_atomic_store(0, &kickoff_flag);
+ tst_atomic_store(0, &game_over);
/*
* Start the offense
@@ -177,15 +227,17 @@ static void do_test(void)
priority = 15;
tst_res(TINFO, "Starting %d offense threads at priority %d",
players_per_team, priority);
+ /* i % ncpus distributes threads round-robin across CPUs; the CPU index is
+ * passed as the thread arg so offense and defense pairs share the same 
CPU */
for (i = 0; i < players_per_team; i++)
- create_fifo_thread(thread_offense, NULL, priority);
+ create_fifo_thread(thread_offense, (void *)(intptr_t)(i % ncpus), 
priority);
/* Start the defense */
priority = 30;
tst_res(TINFO, "Starting %d defense threads at priority %d",
players_per_team, priority);
for (i = 0; i < players_per_team; i++)
- create_fifo_thread(thread_defense, NULL, priority);
+ create_fifo_thread(thread_defense, (void *)(intptr_t)(i % ncpus), 
priority);
/* Start the crazy fans*/
priority = 50;
@@ -203,6 +255,18 @@ static void do_setup(void)
{
tst_check_rt_group_sched_support();
+ /* save current value so cleanup can restore it regardless of what it 
was */
+ SAFE_FILE_SCANF("/proc/sys/kernel/sched_rt_runtime_us", "%ld",
+ &saved_rt_runtime_us);
+
+ tst_res(TINFO,
+ "Disabling RT throttling (sched_rt_runtime_us was %ld, setting to -1) "
+ "to prevent bandwidth exhaustion that violates SCHED_FIFO priority "
+ "ordering on many-CPU systems",
+ saved_rt_runtime_us);
+
+ SAFE_FILE_PRINTF("/proc/sys/kernel/sched_rt_runtime_us", "%ld", -1L);
+
if (tst_parse_int(str_game_length, &game_length, 1, INT_MAX))
tst_brk(TBROK, "Invalid game length '%s'", str_game_length);
@@ -210,9 +274,18 @@ static void do_setup(void)
tst_brk(TBROK, "Invalid number of players '%s'", str_players_per_team);
}
+static void do_cleanup(void)
+{
+ tst_res(TINFO, "Restoring RT throttling (sched_rt_runtime_us = %ld)",
+ saved_rt_runtime_us);
+ SAFE_FILE_PRINTF("/proc/sys/kernel/sched_rt_runtime_us", "%ld",
+ saved_rt_runtime_us);
+}
+
static struct tst_test test = {
.test_all = do_test,
.setup = do_setup,
+ .cleanup = do_cleanup,
.needs_root = 1,
.options = (struct tst_option[]) {
{"l:", &str_game_length, "Game length in sec (default: "
-- 
2.39.1

[-- Attachment #2: 0001-sched_football-fix-false-failures-on-many-CPU-system.patch --]
[-- Type: text/plain, Size: 7931 bytes --]

From 3fc17dd06907785f5b1b65aebfe150c8ac73d54a Mon Sep 17 00:00:00 2001
From: Soma Das <somadas1@linux.ibm.com>
Date: Sun, 12 Apr 2026 13:13:08 +0000
Subject: [PATCH] sched_football: fix false failures on many-CPU systems

On large SMP systems with CONFIG_RT_GROUP_SCHED=n, four independent
issues cause false failures.

1. RT throttling freezes all SCHED_FIFO threads simultaneously. On
   release, the kernel does not always reschedule the highest-priority
   thread first on every CPU, so offense briefly runs and increments
   the_ball before defense is rescheduled. Fix by saving and disabling
   sched_rt_runtime_us in setup and restoring it in a new cleanup
   callback.

2. Offense and defense threads were unpinned, allowing the scheduler
   to migrate them freely. An offense thread could land on a CPU with
   no defense thread present and run unchecked. Fix by passing a CPU
   index as the thread arg and calling sched_setaffinity() at thread
   start. Pairs are distributed round-robin (i % ncpus) so each
   offense thread shares its CPU with a defense thread.

3. game_over was never reset between iterations, causing all threads
   to exit immediately on reruns (-i N), making the test a no-op.
   Fix by resetting both kickoff_flag and game_over at the top of
   do_test().

4. sched_setscheduler() failure for the referee was silently ignored.
   If the call fails the test produces meaningless results. Fix by
   checking the return value and calling tst_brk(TBROK) on failure.

Signed-off-by: Soma Das <somadas1@linux.ibm.com>
---
 .../func/sched_football/sched_football.c      | 83 +++++++++++++++++--
 1 file changed, 78 insertions(+), 5 deletions(-)

diff --git a/testcases/realtime/func/sched_football/sched_football.c b/testcases/realtime/func/sched_football/sched_football.c
index 2cb85322d..43bac9468 100644
--- a/testcases/realtime/func/sched_football/sched_football.c
+++ b/testcases/realtime/func/sched_football/sched_football.c
@@ -3,6 +3,15 @@
  * Copyright © International Business Machines Corp., 2007, 2008
  * Copyright (c) 2024 Petr Vorel <pvorel@suse.cz>
  * Author: John Stultz <jstultz@google.com>
+ *
+ * On many-CPU systems with CONFIG_RT_GROUP_SCHED=n, the global RT
+ * bandwidth limit (sched_rt_runtime_us, default 950000/1000000)
+ * periodically freezes *all* SCHED_FIFO tasks together and then
+ * releases them together. During the release window the kernel does
+ * not always re-pick defense first on every CPU, so lower-priority
+ * offense threads briefly get scheduled and bump the_ball, breaking
+ * the invariant the test checks. Disable RT throttling for the
+ * duration of the test and restore it in cleanup.
  */
 
 /*\
@@ -46,6 +55,8 @@ static int players_per_team = 0;
 static int game_length = DEF_GAME_LENGTH;
 static tst_atomic_t kickoff_flag;
 static tst_atomic_t game_over;
+/* saved before disabling RT throttling so cleanup can restore the original value */
+static long saved_rt_runtime_us;
 
 static char *str_game_length;
 static char *str_players_per_team;
@@ -77,9 +88,24 @@ void *thread_fan(void *arg LTP_ATTRIBUTE_UNUSED)
 }
 
 /* This is the defensive team. They're trying to block the offense */
-void *thread_defense(void *arg LTP_ATTRIBUTE_UNUSED)
+void *thread_defense(void *arg)
 {
+	struct thread *t = (struct thread *)arg;
+	int cpu = (int)(intptr_t)t->arg;
+	cpu_set_t cpuset;
+
 	prctl(PR_SET_NAME, "defense", 0, 0, 0);
+
+	/*
+	 * Pin to the designated CPU. When fans (higher priority) temporarily
+	 * displace this thread, it re-occupies the same CPU immediately on fan
+	 * sleep — no cross-CPU migration delay that could let offense in.
+	 */
+	CPU_ZERO(&cpuset);
+	CPU_SET(cpu, &cpuset);
+	if (sched_setaffinity(0, sizeof(cpuset), &cpuset) != 0)
+		tst_brk(TBROK | TERRNO, "sched_setaffinity failed for defense on CPU %d", cpu);
+
 	pthread_barrier_wait(&start_barrier);
 	while (!tst_atomic_load(&kickoff_flag))
 		;
@@ -92,9 +118,24 @@ void *thread_defense(void *arg LTP_ATTRIBUTE_UNUSED)
 }
 
 /* This is the offensive team. They're trying to move the ball */
-void *thread_offense(void *arg LTP_ATTRIBUTE_UNUSED)
+void *thread_offense(void *arg)
 {
+	struct thread *t = (struct thread *)arg;
+	int cpu = (int)(intptr_t)t->arg;
+	cpu_set_t cpuset;
+
 	prctl(PR_SET_NAME, "offense", 0, 0, 0);
+
+	/*
+	 * Pin to the same CPU as the paired defense thread so there is
+	 * always a higher-priority defense thread locally available to
+	 * preempt this one without requiring cross-CPU migration.
+	 */
+	CPU_ZERO(&cpuset);
+	CPU_SET(cpu, &cpuset);
+	if (sched_setaffinity(0, sizeof(cpuset), &cpuset) != 0)
+		tst_brk(TBROK | TERRNO, "sched_setaffinity failed for offense on CPU %d", cpu);
+
 	pthread_barrier_wait(&start_barrier);
 	while (!tst_atomic_load(&kickoff_flag))
 		sched_yield();
@@ -154,11 +195,15 @@ static void do_test(void)
 {
 	struct sched_param param;
 	int priority;
+	int ncpus;
 	int i;
 
 	if (players_per_team == 0)
 		players_per_team = get_numcpus();
 
+	/* actual CPU count used for affinity assignment, independent of players_per_team */
+	ncpus = get_numcpus();
+
 	tst_res(TINFO, "players_per_team: %d game_length: %d",
 	       players_per_team, game_length);
 
@@ -167,8 +212,13 @@ static void do_test(void)
 
 	/* We're the ref, so set our priority right */
 	param.sched_priority = sched_get_priority_min(SCHED_FIFO) + 80;
-	sched_setscheduler(0, SCHED_FIFO, &param);
+	/* fail loudly if we can't elevate to SCHED_FIFO — test results would be meaningless */
+	if (sched_setscheduler(0, SCHED_FIFO, &param) != 0)
+		tst_brk(TBROK | TERRNO, "sched_setscheduler(SCHED_FIFO) failed");
+
+	/* Reset flags so the test is safe to re-run (e.g. with -i N) */
 	tst_atomic_store(0, &kickoff_flag);
+	tst_atomic_store(0, &game_over);
 
 	/*
 	 * Start the offense
@@ -177,15 +227,17 @@ static void do_test(void)
 	priority = 15;
 	tst_res(TINFO, "Starting %d offense threads at priority %d",
 	       players_per_team, priority);
+	/* i % ncpus distributes threads round-robin across CPUs; the CPU index is
+	 * passed as the thread arg so offense and defense pairs share the same CPU */
 	for (i = 0; i < players_per_team; i++)
-		create_fifo_thread(thread_offense, NULL, priority);
+		create_fifo_thread(thread_offense, (void *)(intptr_t)(i % ncpus), priority);
 
 	/* Start the defense */
 	priority = 30;
 	tst_res(TINFO, "Starting %d defense threads at priority %d",
 	       players_per_team, priority);
 	for (i = 0; i < players_per_team; i++)
-		create_fifo_thread(thread_defense, NULL, priority);
+		create_fifo_thread(thread_defense, (void *)(intptr_t)(i % ncpus), priority);
 
 	/* Start the crazy fans*/
 	priority = 50;
@@ -203,6 +255,18 @@ static void do_setup(void)
 {
 	tst_check_rt_group_sched_support();
 
+	/* save current value so cleanup can restore it regardless of what it was */
+	SAFE_FILE_SCANF("/proc/sys/kernel/sched_rt_runtime_us", "%ld",
+			&saved_rt_runtime_us);
+
+	tst_res(TINFO,
+		"Disabling RT throttling (sched_rt_runtime_us was %ld, setting to -1) "
+		"to prevent bandwidth exhaustion that violates SCHED_FIFO priority "
+		"ordering on many-CPU systems",
+		saved_rt_runtime_us);
+
+	SAFE_FILE_PRINTF("/proc/sys/kernel/sched_rt_runtime_us", "%ld", -1L);
+
 	if (tst_parse_int(str_game_length, &game_length, 1, INT_MAX))
 		tst_brk(TBROK, "Invalid game length '%s'", str_game_length);
 
@@ -210,9 +274,18 @@ static void do_setup(void)
 		tst_brk(TBROK, "Invalid number of players '%s'", str_players_per_team);
 }
 
+static void do_cleanup(void)
+{
+	tst_res(TINFO, "Restoring RT throttling (sched_rt_runtime_us = %ld)",
+		saved_rt_runtime_us);
+	SAFE_FILE_PRINTF("/proc/sys/kernel/sched_rt_runtime_us", "%ld",
+			 saved_rt_runtime_us);
+}
+
 static struct tst_test test = {
 	.test_all = do_test,
 	.setup = do_setup,
+	.cleanup = do_cleanup,
 	.needs_root = 1,
 	.options = (struct tst_option[]) {
 		{"l:", &str_game_length, "Game length in sec (default: "
-- 
2.39.1


[-- Attachment #3: sched_football_20runs_passed_after_fix_friApril101157PM.txt --]
[-- Type: text/plain, Size: 133834 bytes --]

Logs:

40 runs -- passed:

root@fitlp112:/opt/ltp/kirk cd /opt/ltp/kirk
./kirk --run-suite sched -S sched_football --verbose
for i in $(seq 1 20); do ./kirk --run-suite sched -S sched_football --verbose || break; done
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmpfzhq5hgh

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167848.946284] ./kirk[279800]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 4.463s


                                                                                                                                
Execution time: 4.470s

Suite Name: sched
Total Run: 1
Total Runtime: 4.463s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmp7yk6et6l

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167853.528790] ./kirk[280142]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 5.559s


                                                                                                                                
Execution time: 5.567s

Suite Name: sched
Total Run: 1
Total Runtime: 5.559s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmp8amygp0m

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167859.203296] ./kirk[280489]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 5.594s


                                                                                                                                
Execution time: 5.601s

Suite Name: sched
Total Run: 1
Total Runtime: 5.594s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmp5a6xdbbu

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167864.912216] ./kirk[280831]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 4.615s


                                                                                                                                
Execution time: 4.622s

Suite Name: sched
Total Run: 1
Total Runtime: 4.615s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmpvtdg5s1o

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167869.641924] ./kirk[281179]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 5.616s


                                                                                                                                
Execution time: 5.623s

Suite Name: sched
Total Run: 1
Total Runtime: 5.616s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmp3efz_u23

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167875.372240] ./kirk[281520]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 5.536s


                                                                                                                                
Execution time: 5.543s

Suite Name: sched
Total Run: 1
Total Runtime: 5.536s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmp_114ma8i

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167881.022601] ./kirk[281863]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 4.466s


                                                                                                                                
Execution time: 4.473s

Suite Name: sched
Total Run: 1
Total Runtime: 4.466s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmpzzh80pny

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167885.603515] ./kirk[282205]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 5.505s


                                                                                                                                
Execution time: 5.512s

Suite Name: sched
Total Run: 1
Total Runtime: 5.505s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmp_jd0r_ns

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167891.223668] ./kirk[282553]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 5.465s


                                                                                                                                
Execution time: 5.472s

Suite Name: sched
Total Run: 1
Total Runtime: 5.465s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmp0m_afb7i

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167896.803274] ./kirk[282894]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 5.465s


                                                                                                                                
Execution time: 5.472s

Suite Name: sched
Total Run: 1
Total Runtime: 5.465s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmp2detp7tt

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167902.382809] ./kirk[283242]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 5.575s


                                                                                                                                
Execution time: 5.582s

Suite Name: sched
Total Run: 1
Total Runtime: 5.575s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmppr0o7nwg

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167908.072658] ./kirk[283585]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 5.465s


                                                                                                                                
Execution time: 5.472s

Suite Name: sched
Total Run: 1
Total Runtime: 5.465s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmp6cxf0pok

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167913.652811] ./kirk[283926]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 5.505s


                                                                                                                                
Execution time: 5.512s

Suite Name: sched
Total Run: 1
Total Runtime: 5.505s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmpnqzrbhnd

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167919.272469] ./kirk[284274]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 5.466s


                                                                                                                                
Execution time: 5.473s

Suite Name: sched
Total Run: 1
Total Runtime: 5.466s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmpe_lrvofd

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167924.852553] ./kirk[284615]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 4.475s


                                                                                                                                
Execution time: 4.482s

Suite Name: sched
Total Run: 1
Total Runtime: 4.475s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmpnzz9d55c

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167929.442179] ./kirk[284963]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 5.525s


                                                                                                                                
Execution time: 5.533s

Suite Name: sched
Total Run: 1
Total Runtime: 5.525s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmpmcqwlbyv

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167935.081932] ./kirk[285304]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 5.467s


                                                                                                                                
Execution time: 5.474s

Suite Name: sched
Total Run: 1
Total Runtime: 5.467s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmp9ypi47n9

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167940.663394] ./kirk[285648]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 5.465s


                                                                                                                                
Execution time: 5.472s

Suite Name: sched
Total Run: 1
Total Runtime: 5.465s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmp45x_un3i

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167946.242578] ./kirk[285989]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 5.587s


                                                                                                                                
Execution time: 5.594s

Suite Name: sched
Total Run: 1
Total Runtime: 5.587s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmp_x7htbrp

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167951.943745] ./kirk[286337]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 4.465s


                                                                                                                                
Execution time: 4.472s

Suite Name: sched
Total Run: 1
Total Runtime: 4.465s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmp05e5vj0i

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167956.523308] ./kirk[286678]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 5.535s


                                                                                                                                
Execution time: 5.542s

Suite Name: sched
Total Run: 1
Total Runtime: 5.535s

Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmp0hg2p09w

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167444.484829] ./kirk[274636]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 5.483s


                                                                                                                                
Execution time: 5.498s

Suite Name: sched
Total Run: 1
Total Runtime: 5.483s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
=== Run 2 ===
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmpkehaw0rf

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167450.193215] ./kirk[274991]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 5.476s


                                                                                                                                
Execution time: 5.492s

Suite Name: sched
Total Run: 1
Total Runtime: 5.476s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
=== Run 3 ===
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmpkqb41ezg

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167455.894058] ./kirk[275340]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 4.512s


                                                                                                                                
Execution time: 4.523s

Suite Name: sched
Total Run: 1
Total Runtime: 4.512s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
=== Run 4 ===
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmps4cou1w1

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167460.525926] ./kirk[275691]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 5.470s


                                                                                                                                
Execution time: 5.477s

Suite Name: sched
Total Run: 1
Total Runtime: 5.470s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
=== Run 5 ===
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmpxzsjugvz

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167466.114495] ./kirk[276041]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 5.613s


                                                                                                                                
Execution time: 5.620s

Suite Name: sched
Total Run: 1
Total Runtime: 5.613s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
=== Run 6 ===
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmpyysgckff

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167471.844969] ./kirk[276403]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 5.512s


                                                                                                                                
Execution time: 5.520s

Suite Name: sched
Total Run: 1
Total Runtime: 5.512s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
=== Run 7 ===
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmp6d2llp88

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167477.476030] ./kirk[276753]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 5.471s


                                                                                                                                
Execution time: 5.478s

Suite Name: sched
Total Run: 1
Total Runtime: 5.471s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
=== Run 8 ===
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmpfm1rrfy2

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167483.064684] ./kirk[277101]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 5.493s


                                                                                                                                
Execution time: 5.500s

Suite Name: sched
Total Run: 1
Total Runtime: 5.493s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
=== Run 9 ===
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmpyx45pf8v

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167488.687081] ./kirk[277456]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 5.471s


                                                                                                                                
Execution time: 5.478s

Suite Name: sched
Total Run: 1
Total Runtime: 5.471s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
=== Run 10 ===
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmpq55hzdm2

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167494.279983] ./kirk[277803]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 5.478s


                                                                                                                                
Execution time: 5.485s

Suite Name: sched
Total Run: 1
Total Runtime: 5.478s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
=== Run 11 ===
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmphdm70dkr

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167499.875810] ./kirk[278153]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 4.463s


                                                                                                                                
Execution time: 4.470s

Suite Name: sched
Total Run: 1
Total Runtime: 4.463s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
=== Run 12 ===
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmps80xjbp_

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167504.457208] ./kirk[278501]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 5.491s


                                                                                                                                
Execution time: 5.498s

Suite Name: sched
Total Run: 1
Total Runtime: 5.491s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
=== Run 13 ===
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmpqwbw4al7

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167510.065953] ./kirk[278856]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0

Duration: 5.472s


                                                                                                                                
Execution time: 5.479s

Suite Name: sched
Total Run: 1
Total Runtime: 5.472s
Passed Tests: 1
Failed Tests: 0
Skipped Tests: 0
Broken Tests: 0
Warnings: 0
Kernel Version: Linux 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026
CPU: unknown
Machine Architecture: ppc64le
RAM: 89789312 kB
Swap memory: 13107136 kB
Distro: rhel
Distro Version: 10.2


Disconnecting from SUT: host
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
=== Run 14 ===
Host information

	System: Linux
	Node: fitlp112.isst.tadn.ibm.com
	Kernel Release: 6.12.0-211.1.1.el10_2.ppc64le
	Kernel Version: #1 SMP Tue Mar  3 11:30:56 EST 2026
	Machine Architecture: ppc64le
	Processor: 

	Temporary directory: /tmp/kirk.root/tmp10xrl6zm

Connecting to SUT: host
Starting suite: sched

===== sched_football =====
command: sched_football
[167515.656287] ./kirk[279204]: starting test sched_football (sched_football)
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 05m 24s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 5
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)

Test on Different CPU Counts:

root@fitlp112:~/ltp-fresh/testcases/realtime/func/sched_football sched_football -n 2 -l 5
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57ball sched_football -n 2 -l 5
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 20m 00s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 2 game_length: 5
sched_football.c:225: TINFO: Starting 2 offense threads at priority 15
sched_football.c:232: TINFO: Starting 2 defense threads at priority 30
sched_football.c:239: TINFO: Starting 4 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0                                                       echo "Testing with 2 CPUs:"
sched_football -n 2 -l 5h/testcases/realtime/func/sched_football echo "Testing with 2 CPUs:"
Testing with 2 CPUs:-l 5
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 20m 00s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 2 game_length: 5
sched_football.c:225: TINFO: Starting 2 offense threads at priority 15
sched_football.c:232: TINFO: Starting 2 defense threads at priority 30
sched_football.c:239: TINFO: Starting 4 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
root@fitlp112:~/ltp-fresh/testcases/realtime/func/sched_football echo "Testing with 4 CPUs:"
sched_football -n 4 -l 5h/testcases/realtime/func/sched_football echo "Testing with 4 CPUs:"
Testing with 4 CPUs:-l 5
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 20m 00s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0                                                       echo "Testing with 8 CPUs:"
sched_football -n 8 -l 5h/testcases/realtime/func/sched_football echo "Testing with 8 CPUs:"
Testing with 8 CPUs:-l 5
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 20m 00s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 8 game_length: 5
sched_football.c:225: TINFO: Starting 8 offense threads at priority 15
sched_football.c:232: TINFO: Starting 8 defense threads at priority 30
sched_football.c:239: TINFO: Starting 16 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
root@fitlp112:~/ltp-fresh/testcases/realtime/func/sched_football echo "Testing with 40 CPUs (half of 80):"
sched_football -n 40 -l 5/testcases/realtime/func/sched_football echo "Testing with 40 CPUs (half of 80):"
Testing with 40 CPUs (half of 80):
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 20m 00s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 40 game_length: 5
sched_football.c:225: TINFO: Starting 40 offense threads at priority 15
sched_football.c:232: TINFO: Starting 40 defense threads at priority 30
sched_football.c:239: TINFO: Starting 80 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
root@fitlp112:~/ltp-fresh/testcases/realtime/func/sched_football echo "Testing with 160 CPUs (double 80):"
sched_football -n 160 -l 5testcases/realtime/func/sched_football echo "Testing with 160 CPUs (double 80):"
Testing with 160 CPUs (double 80):
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 20m 00s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   1
failed   0
broken   0
skipped  0
warnings 0


Longer game duration (catches timing bugs):

root@fitlp112:~/ltp-fresh/testcases/realtime/func/sched_football echo "Running 10 iterations with 10-second games:"
sched_football -l 10 -i 10
Running 10 iterations with 10-second games:
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 20m 00s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 80 game_length: 10
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (10 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 80 game_length: 10
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (10 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 80 game_length: 10
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (10 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 80 game_length: 10
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (10 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 80 game_length: 10
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (10 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 80 game_length: 10
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (10 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 80 game_length: 10
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (10 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 80 game_length: 10
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (10 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 80 game_length: 10
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (10 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 80 game_length: 10
sched_football.c:225: TINFO: Starting 80 offense threads at priority 15
sched_football.c:232: TINFO: Starting 80 defense threads at priority 30
sched_football.c:239: TINFO: Starting 160 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (10 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   10
failed   0
broken   0
skipped  0
warnings 0
root@fitlp112:~/ltp-fresh/testcases/realtime/func/sched_football 

Running 30 iterations with 4 CPUs:

root@fitlp112:~/ltp-fresh/testcases/realtime/func/sched_football echo "Running 30 iterations with 4 CPUs:"
sched_football -n 4 -i 30
Running 30 iterations with 4 CPUs:
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 20m 00s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 4 game_length: 5
sched_football.c:225: TINFO: Starting 4 offense threads at priority 15
sched_football.c:232: TINFO: Starting 4 defense threads at priority 30
sched_football.c:239: TINFO: Starting 8 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   30
failed   0
broken   0
skipped  0
warnings 0

Running 30 iterations with 160 CPUs:

root@fitlp112:~/ltp-fresh/testcases/realtime/func/sched_football echo "Running 30 iterations with 160 CPUs:"
sched_football -n 160 -i 30
Running 30 iterations with 160 CPUs:
tst_test.c:2059: TINFO: LTP version: 20260130-119-g5d136dc57
tst_test.c:2062: TINFO: Tested kernel: 6.12.0-211.1.1.el10_2.ppc64le #1 SMP Tue Mar  3 11:30:56 EST 2026 ppc64le
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_test.c:1887: TINFO: Overall timeout per run is 0h 20m 00s
tst_kconfig.c:90: TINFO: Parsing kernel config '/lib/modules/6.12.0-211.1.1.el10_2.ppc64le/build/.config'
tst_kconfig.c:567: TINFO: Constraint 'CONFIG_RT_GROUP_SCHED=y' not satisfied!
tst_kconfig.c:513: TINFO: Variables:
tst_kconfig.c:531: TINFO:  CONFIG_RT_GROUP_SCHED=n
sched_football.c:256: TINFO: Disabling RT throttling (sched_rt_runtime_us was -1, setting to -1) to prevent bandwidth exhaustion that violates SCHED_FIFO priority ordering on many-CPU systems
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:205: TINFO: players_per_team: 160 game_length: 5
sched_football.c:225: TINFO: Starting 160 offense threads at priority 15
sched_football.c:232: TINFO: Starting 160 defense threads at priority 30
sched_football.c:239: TINFO: Starting 320 crazy-fan threads at priority 50
sched_football.c:154: TINFO: Starting referee thread
sched_football.c:157: TINFO: Starting the game (5 sec)
sched_football.c:184: TINFO: Final ball position: 0
sched_football.c:190: TPASS: Expect: final_ball == 0
sched_football.c:273: TINFO: Restoring RT throttling (sched_rt_runtime_us = -1)

Summary:
passed   30
failed   0
broken   0
skipped  0
warnings 0



[-- Attachment #4: Type: text/plain, Size: 60 bytes --]


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

^ permalink raw reply related	[flat|nested] 10+ messages in thread

* Re: [LTP] [PATCH] sched_football: fix false failures on many-CPU systems
  2026-04-12 13:05 [LTP] [PATCH] sched_football: fix false failures on many-CPU systems Soma Das
@ 2026-04-14 15:54 ` Jan Polensky
  2026-04-15  9:52   ` Li Wang
  2026-04-14 16:59 ` [LTP] " linuxtestproject.agent
  1 sibling, 1 reply; 10+ messages in thread
From: Jan Polensky @ 2026-04-14 15:54 UTC (permalink / raw)
  To: Soma Das, ltp

On Sun, Apr 12, 2026 at 06:35:42PM +0530, Soma Das wrote:
> Test logs attached — 40+ consecutive runs passing after fix on 80-CPU
> ppc64le LPAR. ---
> From 3fc17dd06907785f5b1b65aebfe150c8ac73d54a Mon Sep 17 00:00:00 2001
> From: Soma Das <somadas1@linux.ibm.com>
> Date: Sun, 12 Apr 2026 13:13:08 +0000
> Subject: [PATCH] sched_football: fix false failures on many-CPU systems
> On large SMP systems with CONFIG_RT_GROUP_SCHED=n, four independent
> issues cause false failures.
> 1. RT throttling freezes all SCHED_FIFO threads simultaneously. On
> release, the kernel does not always reschedule the highest-priority
> thread first on every CPU, so offense briefly runs and increments
> the_ball before defense is rescheduled. Fix by saving and disabling
> sched_rt_runtime_us in setup and restoring it in a new cleanup
> callback.
> 2. Offense and defense threads were unpinned, allowing the scheduler
> to migrate them freely. An offense thread could land on a CPU with
> no defense thread present and run unchecked. Fix by passing a CPU
> index as the thread arg and calling sched_setaffinity() at thread
> start. Pairs are distributed round-robin (i % ncpus) so each
> offense thread shares its CPU with a defense thread.
> 3. game_over was never reset between iterations, causing all threads
> to exit immediately on reruns (-i N), making the test a no-op.
> Fix by resetting both kickoff_flag and game_over at the top of
> do_test().
> 4. sched_setscheduler() failure for the referee was silently ignored.
> If the call fails the test produces meaningless results. Fix by
> checking the return value and calling tst_brk(TBROK) on failure.
> Signed-off-by: Soma Das <somadas1@linux.ibm.com>
> ---
[snip]
Hi Soma,

this patch makes the test much more deterministic by changing the
scheduling scenario: offense/defense were previously unpinned (so they
could migrate freely), but are now pinned via sched_setaffinity() with
explicit CPU pairing (round‑robin across CPUs).

That likely fixes the false failures you describe (offense briefly
running “unchecked” when it lands on a CPU without a local higher‑prio
defense), but it also means we’re no longer exercising
migration/load‑balancing behavior here.

We’re effectively testing local SCHED_FIFO priority ordering under
controlled placement. It would be great to call this out explicitly in
the test description / commit message so readers don’t assume the test
still covers migration fairness.

Tested-by: Jan Polensky <japo@linux.ibm.com>

Tested on z16:

    [************ ~]# lscpu
    Architecture:                s390x
      CPU op-mode(s):            32-bit, 64-bit
      Byte Order:                Big Endian
    CPU(s):                      256
      On-line CPU(s) list:       0-255
    Vendor ID:                   IBM/S390
      Model name:                -
        Machine type:            9175
        Thread(s) per core:      2
[snip]

Best regards
Jan


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [LTP] sched_football: fix false failures on many-CPU systems
  2026-04-12 13:05 [LTP] [PATCH] sched_football: fix false failures on many-CPU systems Soma Das
  2026-04-14 15:54 ` Jan Polensky
@ 2026-04-14 16:59 ` linuxtestproject.agent
  1 sibling, 0 replies; 10+ messages in thread
From: linuxtestproject.agent @ 2026-04-14 16:59 UTC (permalink / raw)
  To: Soma Das; +Cc: ltp

Hi Soma,

On Sun, 12 Apr 2026 13:13:08 +0000, Soma Das wrote:
> sched_football: fix false failures on many-CPU systems
>
> On large SMP systems with CONFIG_RT_GROUP_SCHED=n, four independent
> issues cause false failures.
>
> 1. RT throttling...
> 2. Offense and defense threads were unpinned...
> 3. game_over was never reset between iterations...
> 4. sched_setscheduler() failure for the referee was silently ignored.

The commit message itself describes these as four independent issues.
Please split into four separate commits so bisection and backporting
work correctly. At minimum, fixes 3 (game_over reset between -i
iterations) and 4 (sched_setscheduler error check) are fully orthogonal
to the RT-throttling and CPU-affinity changes and must be separate
patches.

[...]

> +	SAFE_FILE_SCANF("/proc/sys/kernel/sched_rt_runtime_us", "%ld",
> +			&saved_rt_runtime_us);
> ...
> +	SAFE_FILE_PRINTF("/proc/sys/kernel/sched_rt_runtime_us", "%ld", -1L);

Consider using .save_restore in struct tst_test instead of manual
save/restore in setup/cleanup — it is the idiomatic LTP approach for
/proc/sys knobs.

---
Note:

Our agent completed the review of the patch. The agent can sometimes
produce false positives although often its findings are genuine. If you
find issues with the review, please comment this email or ignore the
suggestions.

Regards,
LTP AI Reviewer

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [LTP] [PATCH] sched_football: fix false failures on many-CPU systems
  2026-04-14 15:54 ` Jan Polensky
@ 2026-04-15  9:52   ` Li Wang
  2026-04-15 15:20     ` Jan Polensky
  0 siblings, 1 reply; 10+ messages in thread
From: Li Wang @ 2026-04-15  9:52 UTC (permalink / raw)
  To: Jan Polensky, Soma Das; +Cc: jstultz, ltp

Hi Soma and Jan,

> > 1. RT throttling freezes all SCHED_FIFO threads simultaneously. On
> > release, the kernel does not always reschedule the highest-priority
> > thread first on every CPU, so offense briefly runs and increments
> > the_ball before defense is rescheduled. Fix by saving and disabling
> > sched_rt_runtime_us in setup and restoring it in a new cleanup
> > callback.

Make sense, and like the AI-reviewer points out LTP provides an option
to save_restore it automatically.

> > 2. Offense and defense threads were unpinned, allowing the scheduler
> > to migrate them freely. An offense thread could land on a CPU with
> > no defense thread present and run unchecked. Fix by passing a CPU
> > index as the thread arg and calling sched_setaffinity() at thread
> > start. Pairs are distributed round-robin (i % ncpus) so each
> > offense thread shares its CPU with a defense thread.

This is a good thought, as for SCHED_FIFO it manages the corresponding
runqueue for each CPU and simply picks the higher priority task to run.
So pinning the threads to each CPU makes sense, but maybe we could
only pin the defense because:

With N defense threads pinned one per CPU, every CPU has a defense
thread at priority 30 permanently runnable. The offense threads at priority
15, regardless of which CPU the scheduler places them on, will always find
a higher-priority defense thread on the same CPU's runqueue. Since
SCHED_FIFO strictly favors the higher-priority runnable task, offense can
never be picked.

Pinning offense as well would be redundant, it doesn't matter where offense
lands, because defense already covers every CPU. This also has the advantage
of letting the scheduler freely migrate offense threads without
affecting the test
outcome, which avoids interfering with the kernel's load balancing logic during
the test.

And, I'd suggest using tst_ncpus_available() instead of get_numcpus()
when distributing defense threads across CPUs, in case some CPUs are
offline. Pinning a defense thread to an offline CPU would leave that
CPU uncovered and allow offense to run unchecked. See:

Also, the short usleep() after setting kickoff_flag, which was originally
there to give the RT load balancer time to distribute threads across CPUs,
can now be removed, since defense is already pinned to every CPU and
coverage is guaranteed without any extra settling time.

-       if (tst_check_preempt_rt())
-               usleep(20000);
-       else
-               usleep(2000000);


> > 3. game_over was never reset between iterations, causing all threads
> > to exit immediately on reruns (-i N), making the test a no-op.
> > Fix by resetting both kickoff_flag and game_over at the top of
> > do_test().

Good catch.

> > 4. sched_setscheduler() failure for the referee was silently ignored.
> > If the call fails the test produces meaningless results. Fix by
> > checking the return value and calling tst_brk(TBROK) on failure.

+1

> Tested-by: Jan Polensky <japo@linux.ibm.com>

Thanks, can you re-test it based on what my above revision suggests?

--
Regards,
Li Wang

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [LTP] [PATCH] sched_football: fix false failures on many-CPU systems
  2026-04-15  9:52   ` Li Wang
@ 2026-04-15 15:20     ` Jan Polensky
  2026-04-15 20:21       ` John Stultz via ltp
  0 siblings, 1 reply; 10+ messages in thread
From: Jan Polensky @ 2026-04-15 15:20 UTC (permalink / raw)
  To: Li Wang, Soma Das; +Cc: jstultz, ltp

On Wed, Apr 15, 2026 at 05:52:11PM +0800, Li Wang wrote:
> Hi Soma and Jan,
>
> > > 1. RT throttling freezes all SCHED_FIFO threads simultaneously. On
> > > release, the kernel does not always reschedule the highest-priority
> > > thread first on every CPU, so offense briefly runs and increments
> > > the_ball before defense is rescheduled. Fix by saving and disabling
> > > sched_rt_runtime_us in setup and restoring it in a new cleanup
> > > callback.
>
> Make sense, and like the AI-reviewer points out LTP provides an option
> to save_restore it automatically.
>
> > > 2. Offense and defense threads were unpinned, allowing the scheduler
> > > to migrate them freely. An offense thread could land on a CPU with
> > > no defense thread present and run unchecked. Fix by passing a CPU
> > > index as the thread arg and calling sched_setaffinity() at thread
> > > start. Pairs are distributed round-robin (i % ncpus) so each
> > > offense thread shares its CPU with a defense thread.
>
> This is a good thought, as for SCHED_FIFO it manages the corresponding
> runqueue for each CPU and simply picks the higher priority task to run.
> So pinning the threads to each CPU makes sense, but maybe we could
> only pin the defense because:
>
> With N defense threads pinned one per CPU, every CPU has a defense
> thread at priority 30 permanently runnable. The offense threads at priority
> 15, regardless of which CPU the scheduler places them on, will always find
> a higher-priority defense thread on the same CPU's runqueue. Since
> SCHED_FIFO strictly favors the higher-priority runnable task, offense can
> never be picked.
>
> Pinning offense as well would be redundant, it doesn't matter where offense
> lands, because defense already covers every CPU. This also has the advantage
> of letting the scheduler freely migrate offense threads without
> affecting the test
> outcome, which avoids interfering with the kernel's load balancing logic during
> the test.
>
> And, I'd suggest using tst_ncpus_available() instead of get_numcpus()
> when distributing defense threads across CPUs, in case some CPUs are
> offline. Pinning a defense thread to an offline CPU would leave that
> CPU uncovered and allow offense to run unchecked. See:
>
> Also, the short usleep() after setting kickoff_flag, which was originally
> there to give the RT load balancer time to distribute threads across CPUs,
> can now be removed, since defense is already pinned to every CPU and
> coverage is guaranteed without any extra settling time.
>
> -       if (tst_check_preempt_rt())
> -               usleep(20000);
> -       else
> -               usleep(2000000);
>
>
> > > 3. game_over was never reset between iterations, causing all threads
> > > to exit immediately on reruns (-i N), making the test a no-op.
> > > Fix by resetting both kickoff_flag and game_over at the top of
> > > do_test().
>
> Good catch.
>
> > > 4. sched_setscheduler() failure for the referee was silently ignored.
> > > If the call fails the test produces meaningless results. Fix by
> > > checking the return value and calling tst_brk(TBROK) on failure.
>
> +1
>
> > Tested-by: Jan Polensky <japo@linux.ibm.com>
>
> Thanks, can you re-test it based on what my above revision suggests?
>
> --
> Regards,
> Li Wang

Hi Li, hi Soma,

@Li: I incorporated your suggested changes and re-tested. Works fine for
me on the same machine as before.

	./sched_football -i 10
    [snip]
    Summary:
    passed   10
    failed   0
    broken   0
    skipped  0
    warnings 0

Tested-by: Jan Polensky <japo@linux.ibm.com>

@Soma: Feel free to pick it up, the diff/patch is attached below.
Please note the additional join_threads() call, it is needed if you run the test like:

	./sched_football -i 10

It seems the threads do not terminate correctly without it.

diff --git a/testcases/realtime/func/sched_football/sched_football.c b/testcases/realtime/func/sched_football/sched_football.c
index 43bac9468693..be0334da812e 100644
--- a/testcases/realtime/func/sched_football/sched_football.c
+++ b/testcases/realtime/func/sched_football/sched_football.c
@@ -118,23 +118,17 @@ void *thread_defense(void *arg)
 }

 /* This is the offensive team. They're trying to move the ball */
-void *thread_offense(void *arg)
+void *thread_offense(void *arg LTP_ATTRIBUTE_UNUSED)
 {
-	struct thread *t = (struct thread *)arg;
-	int cpu = (int)(intptr_t)t->arg;
-	cpu_set_t cpuset;
-
 	prctl(PR_SET_NAME, "offense", 0, 0, 0);

 	/*
-	 * Pin to the same CPU as the paired defense thread so there is
-	 * always a higher-priority defense thread locally available to
-	 * preempt this one without requiring cross-CPU migration.
+	 * Offense threads are not pinned. With defense threads pinned one per
+	 * CPU at priority 30, every CPU has a higher-priority defense thread
+	 * runnable. Offense at priority 15 can never be picked by SCHED_FIFO
+	 * regardless of which CPU it lands on. Leaving offense unpinned avoids
+	 * interfering with the kernel's load balancing logic.
 	 */
-	CPU_ZERO(&cpuset);
-	CPU_SET(cpu, &cpuset);
-	if (sched_setaffinity(0, sizeof(cpuset), &cpuset) != 0)
-		tst_brk(TBROK | TERRNO, "sched_setaffinity failed for offense on CPU %d", cpu);

 	pthread_barrier_wait(&start_barrier);
 	while (!tst_atomic_load(&kickoff_flag))
@@ -169,10 +163,6 @@ void referee(int game_length)

 	tst_atomic_store(0, &the_ball);
 	tst_atomic_store(1, &kickoff_flag);
-	if (tst_check_preempt_rt())
-		usleep(20000);
-	else
-		usleep(2000000);

 	/* Watch the game */
 	while ((now.tv_sec - start.tv_sec) < game_length) {
@@ -199,10 +189,10 @@ static void do_test(void)
 	int i;

 	if (players_per_team == 0)
-		players_per_team = get_numcpus();
+		players_per_team = tst_ncpus_available();

 	/* actual CPU count used for affinity assignment, independent of players_per_team */
-	ncpus = get_numcpus();
+	ncpus = tst_ncpus_available();

 	tst_res(TINFO, "players_per_team: %d game_length: %d",
 	       players_per_team, game_length);
@@ -227,10 +217,8 @@ static void do_test(void)
 	priority = 15;
 	tst_res(TINFO, "Starting %d offense threads at priority %d",
 	       players_per_team, priority);
-	/* i % ncpus distributes threads round-robin across CPUs; the CPU index is
-	 * passed as the thread arg so offense and defense pairs share the same CPU */
 	for (i = 0; i < players_per_team; i++)
-		create_fifo_thread(thread_offense, (void *)(intptr_t)(i % ncpus), priority);
+		create_fifo_thread(thread_offense, NULL, priority);

 	/* Start the defense */
 	priority = 30;
@@ -248,6 +236,7 @@ static void do_test(void)

 	referee(game_length);

+	join_threads();
 	pthread_barrier_destroy(&start_barrier);
 }



-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

^ permalink raw reply related	[flat|nested] 10+ messages in thread

* Re: [LTP] [PATCH] sched_football: fix false failures on many-CPU systems
  2026-04-15 15:20     ` Jan Polensky
@ 2026-04-15 20:21       ` John Stultz via ltp
  2026-04-16  3:23         ` Li Wang
  0 siblings, 1 reply; 10+ messages in thread
From: John Stultz via ltp @ 2026-04-15 20:21 UTC (permalink / raw)
  To: Jan Polensky; +Cc: Soma Das, ltp

On Wed, Apr 15, 2026 at 8:20 AM Jan Polensky <japo@linux.ibm.com> wrote:
> On Wed, Apr 15, 2026 at 05:52:11PM +0800, Li Wang wrote:
> > Hi Soma and Jan,
> >
> > > > 1. RT throttling freezes all SCHED_FIFO threads simultaneously. On
> > > > release, the kernel does not always reschedule the highest-priority
> > > > thread first on every CPU, so offense briefly runs and increments
> > > > the_ball before defense is rescheduled. Fix by saving and disabling
> > > > sched_rt_runtime_us in setup and restoring it in a new cleanup
> > > > callback.
> >
> > Make sense, and like the AI-reviewer points out LTP provides an option
> > to save_restore it automatically.

Throttling shouldn't break the test. The fact that SCHED_NORMAL tasks
ran shouldn't change the ordering when we go back to running RT tasks.
This is likely a kernel bug.

> > > > 2. Offense and defense threads were unpinned, allowing the scheduler
> > > > to migrate them freely. An offense thread could land on a CPU with
> > > > no defense thread present and run unchecked. Fix by passing a CPU
> > > > index as the thread arg and calling sched_setaffinity() at thread
> > > > start. Pairs are distributed round-robin (i % ncpus) so each
> > > > offense thread shares its CPU with a defense thread.
> >
> > This is a good thought, as for SCHED_FIFO it manages the corresponding
> > runqueue for each CPU and simply picks the higher priority task to run.
> > So pinning the threads to each CPU makes sense, but maybe we could
> > only pin the defense because:
> >
> > With N defense threads pinned one per CPU, every CPU has a defense
> > thread at priority 30 permanently runnable. The offense threads at priority
> > 15, regardless of which CPU the scheduler places them on, will always find
> > a higher-priority defense thread on the same CPU's runqueue. Since
> > SCHED_FIFO strictly favors the higher-priority runnable task, offense can
> > never be picked.
> >
> > Pinning offense as well would be redundant, it doesn't matter where offense
> > lands, because defense already covers every CPU. This also has the advantage
> > of letting the scheduler freely migrate offense threads without
> > affecting the test
> > outcome, which avoids interfering with the kernel's load balancing logic during
> > the test.
> >
> > And, I'd suggest using tst_ncpus_available() instead of get_numcpus()
> > when distributing defense threads across CPUs, in case some CPUs are
> > offline. Pinning a defense thread to an offline CPU would leave that
> > CPU uncovered and allow offense to run unchecked. See:

I didn't see the orignal patch here, but the whole point of
sched_football is to ensure the top <num cpu> (unaffined) priority
tasks are always run and no lower priority rt tasks are run instead.

So none of the tasks should be pinned to any cpus. The scheduler is
supposed to ensure the RT invariant holds.
There are some known bugs at the moment that will cause sched_football
to fail (the RT_PUSH_IPI feature, for instance). That's a problem with
the kernel, not the test.

thanks
-john

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [LTP] [PATCH] sched_football: fix false failures on many-CPU systems
  2026-04-15 20:21       ` John Stultz via ltp
@ 2026-04-16  3:23         ` Li Wang
  2026-04-16  5:53           ` Li Wang
  0 siblings, 1 reply; 10+ messages in thread
From: Li Wang @ 2026-04-16  3:23 UTC (permalink / raw)
  To: John Stultz; +Cc: Soma Das, ltp

Hi John,

John Stultz <jstultz@google.com> wrote:

> > > > > 1. RT throttling freezes all SCHED_FIFO threads simultaneously. On
> > > > > release, the kernel does not always reschedule the highest-priority
> > > > > thread first on every CPU, so offense briefly runs and increments
> > > > > the_ball before defense is rescheduled. Fix by saving and disabling
> > > > > sched_rt_runtime_us in setup and restoring it in a new cleanup
> > > > > callback.
> > >
> > > Make sense, and like the AI-reviewer points out LTP provides an option
> > > to save_restore it automatically.
>
> Throttling shouldn't break the test. The fact that SCHED_NORMAL tasks
> ran shouldn't change the ordering when we go back to running RT tasks.
> This is likely a kernel bug.

Theoretically speaking, your point is correct. While instant global
priority ordering upon unthrottling is ideal, it ignores the physical realities
of SMP architecture.

If we look at do_sched_rt_period_timer(), CPUs are unthrottled sequentially
via a for_each_cpu loop. When an early CPU in the loop is unlocked, it
immediately schedules its local RT task 'offense'.
See:
  https://elixir.bootlin.com/linux/v7.0/source/kernel/sched/rt.c#L797

Meanwhile, subsequent CPUs in the loop (which may hold the higher-priority
'defense' task) are literally still throttled.

Expecting atomic, zero-latency global unthrottling is physically unrealistic for
multi-core systems.

That's why I tend to believe disabling throttling for this specific test is the
wise and practical approach.


> > > > > 2. Offense and defense threads were unpinned, allowing the scheduler
> > > > > to migrate them freely. An offense thread could land on a CPU with
> > > > > no defense thread present and run unchecked. Fix by passing a CPU
> > > > > index as the thread arg and calling sched_setaffinity() at thread
> > > > > start. Pairs are distributed round-robin (i % ncpus) so each
> > > > > offense thread shares its CPU with a defense thread.
> > >
> > > This is a good thought, as for SCHED_FIFO it manages the corresponding
> > > runqueue for each CPU and simply picks the higher priority task to run.
> > > So pinning the threads to each CPU makes sense, but maybe we could
> > > only pin the defense because:
> > >
> > > With N defense threads pinned one per CPU, every CPU has a defense
> > > thread at priority 30 permanently runnable. The offense threads at priority
> > > 15, regardless of which CPU the scheduler places them on, will always find
> > > a higher-priority defense thread on the same CPU's runqueue. Since
> > > SCHED_FIFO strictly favors the higher-priority runnable task, offense can
> > > never be picked.
> > >
> > > Pinning offense as well would be redundant, it doesn't matter where offense
> > > lands, because defense already covers every CPU. This also has the advantage
> > > of letting the scheduler freely migrate offense threads without
> > > affecting the test
> > > outcome, which avoids interfering with the kernel's load balancing logic during
> > > the test.
> > >
> > > And, I'd suggest using tst_ncpus_available() instead of get_numcpus()
> > > when distributing defense threads across CPUs, in case some CPUs are
> > > offline. Pinning a defense thread to an offline CPU would leave that
> > > CPU uncovered and allow offense to run unchecked. See:
>
> I didn't see the orignal patch here, but the whole point of
> sched_football is to ensure the top <num cpu> (unaffined) priority
> tasks are always run and no lower priority rt tasks are run instead.
>
> So none of the tasks should be pinned to any cpus. The scheduler is
> supposed to ensure the RT invariant holds.
> There are some known bugs at the moment that will cause sched_football
> to fail (the RT_PUSH_IPI feature, for instance). That's a problem with
> the kernel, not the test.

Apart from the known bug of RT_PUSH_IPI feature, it still does not
guarantee 100% success in real scenarios.

After a deep look into the rt scheduler principals, I found that, because
the RT_PUSH_IPI mechanism is designed as a "best-effort"
optimization rather than a guaranteed operation. As the kernel's
scheduling state is highly dynamic and asynchronous, a push attempt
will deliberately abort if the environment changes between the time the
IPI is sent and when it is actually processed.

It fails by design to prevent instability, primarily due to state expiration,
CPU affinity restrictions, sudden priority inversions, or the lack of an
eligible target CPU.

See push_rt_task() in kernel/sched/rt.c:
  https://elixir.bootlin.com/linux/v7.0/source/kernel/sched/rt.c#L1939

Hence, if we explicitly pin the defense thread to each CPU, it will join in
the corresponding runqueues, which completely match the reasonable
situation: the kernel's RT scheduler guarantees per-CPU priority ordering,
not global placement. The RT load balancer is asynchronous and doesn't
guarantee that all high-priority threads are placed before any low-priority
thread runs.

On the other side, if the test expects a global guarantee, it's testing
something the kernel doesn't claim to provide.

To the rest changes, the current test has several non-kernel issues
(RT throttling interference, uninitialized game_over on reruns, silent
sched_setscheduler failures) that produce false failures. These mask
the real kernel bugs you want to detect.


--
Regards,
Li Wang

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [LTP] [PATCH] sched_football: fix false failures on many-CPU systems
  2026-04-16  3:23         ` Li Wang
@ 2026-04-16  5:53           ` Li Wang
  2026-04-16  8:26             ` Soma Das
  0 siblings, 1 reply; 10+ messages in thread
From: Li Wang @ 2026-04-16  5:53 UTC (permalink / raw)
  To: John Stultz; +Cc: Soma Das, ltp

> That's why I tend to believe disabling throttling for this specific test is the
> wise and practical approach.

However, back to the original patch, disabling throttling was
indeed a bit of an overprotection based on the pined method
(I didn't realize that before).

Once we go with pin 'defense' threads to every CPU, while leaving
the offense thread unpinned, this throttling can be kept enabled.

Whichever CPU gets unthrottled first will instantly execute its local
defensetask, completely starving the lower-priority offense task.

It relies on strict local preemption to perfectly mask the SMP sequential
unthrottling latency, fixing the test without needing to disable
sched_rt_runtime_us in the kernel.

-- 
Regards,
Li Wang

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [LTP] [PATCH] sched_football: fix false failures on many-CPU systems
  2026-04-16  5:53           ` Li Wang
@ 2026-04-16  8:26             ` Soma Das
  2026-04-16  8:40               ` Li Wang
  0 siblings, 1 reply; 10+ messages in thread
From: Soma Das @ 2026-04-16  8:26 UTC (permalink / raw)
  To: Li Wang, John Stultz; +Cc: ltp

Hi Li, Jan, John,

Thank you all for the detailed review and discussion.

Based on the feedback, here is what I plan to incorporate in v2:

  *

    Pin only defense threads (one per CPU), leave offense unpinned

  *

    Replace |get_numcpus()| with |tst_ncpus_available()| to handle
    offline CPUs

  *

    Drop the RT throttle disabling entirely - unnecessary once defense
    is pinned per CPU

  *

    Remove the |usleep()| / |tst_check_preempt_rt()| block after kickoff

  *

    Add |join_threads()| before |pthread_barrier_destroy()| for clean
    |-i N| reruns (thanks Jan for catching this)

  *

    Split into separate patches - at minimum fixes #3 and #4 will be
    separate

  *

    Update commit message to clarify the test now verifies per-CPU
    SCHED_FIFO priority ordering

Will send v2 soon.

Thanks,
Soma


On 16/04/26 11:23 AM, Li Wang wrote:
>> That's why I tend to believe disabling throttling for this specific test is the
>> wise and practical approach.
> However, back to the original patch, disabling throttling was
> indeed a bit of an overprotection based on the pined method
> (I didn't realize that before).
>
> Once we go with pin 'defense' threads to every CPU, while leaving
> the offense thread unpinned, this throttling can be kept enabled.
>
> Whichever CPU gets unthrottled first will instantly execute its local
> defensetask, completely starving the lower-priority offense task.
>
> It relies on strict local preemption to perfectly mask the SMP sequential
> unthrottling latency, fixing the test without needing to disable
> sched_rt_runtime_us in the kernel.
>

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [LTP] [PATCH] sched_football: fix false failures on many-CPU systems
  2026-04-16  8:26             ` Soma Das
@ 2026-04-16  8:40               ` Li Wang
  0 siblings, 0 replies; 10+ messages in thread
From: Li Wang @ 2026-04-16  8:40 UTC (permalink / raw)
  To: Soma Das; +Cc: John Stultz, ltp

Soma Das <somadas1@linux.ibm.com> wrote:

> Based on the feedback, here is what I plan to incorporate in v2:
>
>   * Pin only defense threads (one per CPU), leave offense unpinned
>
>   * Replace |get_numcpus()| with |tst_ncpus_available()| to handle
>     offline CPUs
>
>   * Drop the RT throttle disabling entirely - unnecessary once defense
>     is pinned per CPU
>
>   * Remove the |usleep()| / |tst_check_preempt_rt()| block after kickoff
>
>   * Add |join_threads()| before |pthread_barrier_destroy()| for clean
>     |-i N| reruns (thanks Jan for catching this)
>
>   * Split into separate patches - at minimum fixes #3 and #4 will be
>     separate
>
>   * Update commit message to clarify the test now verifies per-CPU
>     SCHED_FIFO priority ordering

Generally that's my expected revision, but I would suggest you wait for
John's reply to see if he has other suggestions.
(John is an expert in schedulers :)

But you can test the v2 on your side and feedback here firstly.


-- 
Regards,
Li Wang

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2026-04-16  8:41 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-04-12 13:05 [LTP] [PATCH] sched_football: fix false failures on many-CPU systems Soma Das
2026-04-14 15:54 ` Jan Polensky
2026-04-15  9:52   ` Li Wang
2026-04-15 15:20     ` Jan Polensky
2026-04-15 20:21       ` John Stultz via ltp
2026-04-16  3:23         ` Li Wang
2026-04-16  5:53           ` Li Wang
2026-04-16  8:26             ` Soma Das
2026-04-16  8:40               ` Li Wang
2026-04-14 16:59 ` [LTP] " linuxtestproject.agent

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox