Date: Thu, 25 Jul 2019 09:14:21 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 239351] [panic] spin lock held too long under heavy load (net/wireguard affected) Message-ID: <bug-239351-7501-dsTY5FhJW6@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-239351-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-239351-7501@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 --- Comment #12 from Evilham <contact@evilham.com> --- Created attachment 206056 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D206056&action= =3Dedit panic_assertion_patch206036.tar.gz This panic occurred with 13.0-CURRENT r350275+d78b126a34dc(master) + patch206036 over night; the system was compiling some ports in poudriere f= or CURRENT. I was about to discard it as it being the same as the others, but noticed it has a different message, namely panic: Assertion error_ =3D=3D 0 failed at /freebsd/src/sys/vm/vm_map.c:553 Attached is the dump, backtrace, acttrace and I managed to identify tid and frame but p other_cpus returned "No symbol "other_cpus" in current context.= ", which is probably normal since this is a totally different thing, but I tho= ught I'd give it a try anyway. I hope this is useful. --=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-7501-dsTY5FhJW6>