Date: Thu, 25 Jul 2019 21:44:47 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 239351] [panic] spin lock held too long under heavy load (net/wireguard affected) Message-ID: <bug-239351-227-YelJaE2Si4@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-239351-227@https.bugs.freebsd.org/bugzilla/> References: <bug-239351-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=3D239351 Mark Millard <marklmi26-fbsd@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marklmi26-fbsd@yahoo.com --- Comment #20 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Mark Johnston from comment #13) Just in case the extra information might prove to be of use: I had a one-time 'spin lock held too long' back on 2019-Jul-06 that I reported in: https://lists.freebsd.org/pipermail/freebsd-current/2019-July/073779.html It was under Hyper-V and had nothing to do with wireguard or anything like that: buildworld buildkernel under a -r349794 based build. This was on a 1950X Threadripper. But it did not repeat in my activity after that, despite trying a bunch of (re)builds. I've since updated beyond that point). The message submittal had a backtrace. --=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-239351-227-YelJaE2Si4>