Re: port-sparc/59825: futex_wake_op_op test hangs on qemu-sparc with TCX and -smp 2

["Martin Husemann via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR port-sparc/59825; it has been noted by GNATS.

From: Martin Husemann <martin%duskware.de@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: port-sparc/59825: futex_wake_op_op test hangs on qemu-sparc with
 TCX and -smp 2
Date: Tue, 9 Dec 2025 18:35:52 +0100

 Run on real hardware (dual cpu SS20) this test triggers several
 xcall timeouts:
 
 xcall(cpu1,0xf034b138) from 0xf034b308: couldn't ping cpus: cpu0
 xcall(cpu1,0xf034b138) from 0xf034b308: couldn't ping cpus: cpu0
 xcall(cpu1,0xf034b138) from 0xf034b308: couldn't ping cpus: cpu0
 xcall(cpu1,0xf034b138) from 0xf034b308: couldn't ping cpus: cpu0
 xcall(cpu1,0xf034b138) from 0xf034b308: couldn't ping cpus: cpu0
 xcall(cpu1,0xf034b138) from 0xf034b308: couldn't ping cpus: cpu0
 xcall(cpu1,0xf034b138) from 0xf034b308: couldn't ping cpus: cpu0
 xcall(cpu1,0xf034b138) from 0xf034b308: couldn't ping cpus: cpu0
 xcall(cpu1,0xf034b138) from 0xf034b308: couldn't ping cpus: cpu0
 xcall(cpu1,0xf034b138) from 0xf034b308: couldn't ping cpus: cpu0
 xcall(cpu1,0xf034b138) from 0xf034b308: couldn't ping cpus: cpu0
 xcall(cpu1,0xf034b138) from 0xf034b308: couldn't ping cpus: cpu0
 xcall(cpu1,0xf034b138) from 0xf034b308: couldn't ping cpus: cpu0
 xcall(cpu1,0xf034b138) from 0xf034b308: couldn't ping cpus: cpu0
 xcall(cpu1,0xf034b138) from 0xf034b308: couldn't ping cpus: cpu0
 xcall(cpu0,0xf034b138) from 0xf034b308: couldn't ping cpus: cpu1
 xcall(cpu0,0xf034b138) from 0xf034b308: couldn't ping cpus: cpu1
 xcall(cpu0,0xf034b138) from 0xf034b308: couldn't ping cpus: cpu1
 xcall(cpu0,0xf034b138) from 0xf034b308: couldn't ping cpus: cpu1
 xcall(cpu0,0xf034b138) from 0xf034b308: couldn't ping cpus: cpu1
 xcall(cpu0,0xf034b138) from 0xf034b308: couldn't ping cpus: cpu1
 xcall(cpu0,0xf034b138) from 0xf034b308: couldn't ping cpus: cpu1
 xcall(cpu0,0xf034b138) from 0xf034b308: couldn't ping cpus: cpu1
 
 but finishes (and all CPUs are responsive again) often.
 
 Sometimes, however, it hangs hard (can't even break into ddb).
 
 Martin