Date: Thu, 23 Jan 2020 14:11:35 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 243534] Kernel panics with "panic: invalid count 2" early during boot Message-ID: <bug-243534-227-b8EM0sd1j4@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-243534-227@https.bugs.freebsd.org/bugzilla/> References: <bug-243534-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=3D243534 --- Comment #2 from commit-hook@freebsd.org --- A commit references this bug: Author: emaste Date: Thu Jan 23 14:11:03 UTC 2020 New revision: 357045 URL: https://svnweb.freebsd.org/changeset/base/357045 Log: Apply r355819 to sparc64 - fix assertion failure after r355784 From r355819: Repeat the spinlock_enter/exit pattern from amd64 on other architectures to fix an assert violation introduced in r355784. Without this spinlock_exit() may see owepreempt and switch before reducing the spinlock count. amd64 had been optimized to do a single critical enter/exit regardless of the number of spinlocks which avoided the problem and this optimization had not been applied elsewhere. This is completely untested - I have no obsolete Sparc hardware - but someone did try testing recent changes on sparc64 (PR 243534). PR: 243534 Changes: head/sys/sparc64/sparc64/machdep.c --=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-243534-227-b8EM0sd1j4>