From owner-freebsd-bugs@freebsd.org  Thu Jul 16 22:33:39 2015
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 43EBC9A4622
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Thu, 16 Jul 2015 22:33:39 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 303C91E4B
 for <freebsd-bugs@FreeBSD.org>; Thu, 16 Jul 2015 22:33:39 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t6GMXdTA015180
 for <freebsd-bugs@FreeBSD.org>; Thu, 16 Jul 2015 22:33:39 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 201245] panic: spin lock held too long on sparc64
Date: Thu, 16 Jul 2015 22:33:39 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: marius@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
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/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jul 2015 22:33:39 -0000

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.