Date: Thu, 25 Jul 2019 23:17:30 +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-wDM3jyGYv3@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 --- Comment #22 from Evilham <contact@evilham.com> --- (In reply to Konstantin Belousov from comment #21) > Make sure that you run absolutely latest BIOS. Oh, wth.... That didn't cross my mind. I had 1.16, which was latest last ti= me I checked (end of June), now there is 1.22 and 1.24. Upgraded to 1.24, suddenly there are issues with drm-kmod, booted single-us= er, disabled it, system boots fine, ran my "WireGuard" panic-maker and... it's = not working anymore (aka no panic). These are the release notes, does any of that sound like it could have fixed the issue? https://download.lenovo.com/pccbbs/mobiles/r0wuj56w.txt This sounds super suspicious to me but I can't really parse the meaning out= of this English: - [Important] Modify WMI AmdVt item can't modify and remove unuse item I'll reactivate WireGuard on my day-to-day and keep an eye on things, if in= a few days the panic doesn't happen again, I'll close this bug. --=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-wDM3jyGYv3>