Date: Thu, 16 Jul 2015 22:33:39 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 201245] panic: spin lock held too long on sparc64 Message-ID: <bug-201245-8-36xVPEyB4L@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-201245-8@https.bugs.freebsd.org/bugzilla/> References: <bug-201245-8@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=201245 --- Comment #8 from Marius Strobl <marius@FreeBSD.org> --- You may give the following patch a try: https://people.freebsd.org/~marius/sparc64_ipi_mtx.diff Note that the issue at hand here is that the hardware architectures of v210, v240 and v440 are flawed in that they don't include a globally accessible time counter, just per-cores ones which aren't synchronized and therefore drift. Given how time keeping in FreeBSD works and although a few ways for working around that situation exist, all of these approaches come with some not really desirable side-effects and most are insane implementation-wise. Some changes in MI code over time also revealed some bugs in the current path taken in that they made race-conditions more likely to be hit when running on one of these models. That's also why subtle changes e. g. in network settings, differences of the generated code caused by commits in unrelated kernel parts etc. may avoid running into the panic encountered, but in fact these are red herrings. -- 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-201245-8-36xVPEyB4L>