Date: Wed, 24 Jul 2019 10:12:00 +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-9irHH77Yr7@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 #3 from Evilham <contact@evilham.com> --- Created attachment 206031 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D206031&action= =3Dedit coredump_nowg_onboot_net_up Actually, I meant to update this bug report yesterday but didn't manage to. I have seen this kernel panic again without WireGuard, though it does happen way more often with it and I can produce the panic with it but can't reliab= ly (ehem) panic the system without it. It actually happened once while booting, but after network was initialised,= so network could still be at fault. Now I'm quite inclined to believe that this is related to #231760 and booti= ng with hw.pci.mcfg=3D0 (the only way to boot atm); but my knowledge of FreeBS= D's inners is not up to the task to fully pin-point it. I have two more dumps, please note that even if drm-kmod is present and somewhat verbose, it was not present on the system at the time of the first dump; so it'd be misleading to think it's caused by it. --=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-9irHH77Yr7>