Date: Wed, 14 Jun 2023 15:15:50 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 271983] mi_switch hang in KVM on Sapphire Rapids running NET_EPOCH_DRAIN_CALLBACKS Message-ID: <bug-271983-227-inq5IfrrFM@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-271983-227@https.bugs.freebsd.org/bugzilla/> References: <bug-271983-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D271983 --- Comment #10 from R. Christian McDonald <rcm@rcm.sh> --- I discovered today that it is possible to reproduce this bug on non-Sapphire Rapids systems. The difference being the use of the legacy vs modern virtio-rng.=20 The legacy virtio-rng doesn't exhibit this problem, it's the modern virtio-= rng that does. I tested on a non-Sapphire Rapids PVE host this morning and forced the virtio-rng to explicitly use the modern device (virtio-rng-pci-non-transitional) instead of the legacy (transitional) devi= ce (which is what PVE sets up by default) and the problem manifests there as w= ell. Conversely, if I explicitly use the legacy device on the Sapphire Rapids bo= x, the problem goes away there too. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-271983-227-inq5IfrrFM>