Date: Thu, 25 Jul 2019 01:08:05 +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-sXhbN6v69j@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 #9 from Mark Johnston <markj@FreeBSD.org> --- Created attachment 206046 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D206046&action= =3Dedit kgdb script Thanks. Now, please try downloading the attached file, and run: # printf "source /path/to/acttace.py\nacttrace\n" | kgdb83 /boot/kernel/ker= nel /var/crash/vmcore.2 Then save the output here. The kernel panicked because one of the cores fa= iled to respond to an interrupt, and it's not clear to me what that core was doi= ng at the time. It would also be helpful to see output from: # kgdb /boot/kernel/kernel /var/crash/vmcore.2 (kgdb) tid 100168 (kgdb) frame 4 (kgdb) p other_cpus --=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-sXhbN6v69j>