aboutsummaryrefslogtreecommitdiff
path: root/sys/contrib/alpine-hal/ssh:/anongit@git.FreeBSD.org/(developers-only)
diff options
context:
space:
mode:
authorAdrian Chadd <adrian@FreeBSD.org>2026-01-03 22:52:14 +0000
committerAdrian Chadd <adrian@FreeBSD.org>2026-01-04 02:27:48 +0000
commit8df2e542146801fd01675e56724eaa567d04c209 (patch)
tree5a535dc16eeb97615b2e48924b6018894afaf94e /sys/contrib/alpine-hal/ssh:/anongit@git.FreeBSD.org/(developers-only)
parent17355cf50fcbd0d8ddb638e1f2fd5861b526edbe (diff)
powerpc: put the isync inside the TD_LOCK() checking loopHEADmain
Fix a narrow window where the lock is unlocked but the checking CPU hasn't flushed things appropriately. Inside this window the CPU inside cpu_switch() will loop forever thinking the destination thread is still blocked/locked even though it is not. This manifests as the system hanging after starting all APs. I've seen this reliably trigger in qemu-system-ppc64 running power9 pseries guests; the more CPUs the more likely it triggers at boot. PR: kern/292167 Differential Revision: https://reviews.freebsd.org/D54478 Reviewed by: jhibbits MFC after: 1 week Relnotes: yes
Diffstat (limited to 'sys/contrib/alpine-hal/ssh:/anongit@git.FreeBSD.org/(developers-only)')
0 files changed, 0 insertions, 0 deletions