From owner-freebsd-bugs@FreeBSD.ORG  Mon Nov 24 17:40:35 2014
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 92218EC8
 for <freebsd-bugs@FreeBSD.org>; Mon, 24 Nov 2014 17:40:35 +0000 (UTC)
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 7911560B
 for <freebsd-bugs@FreeBSD.org>; Mon, 24 Nov 2014 17:40:35 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sAOHeZTm061180
 for <freebsd-bugs@FreeBSD.org>; Mon, 24 Nov 2014 17:40:35 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 195262] [lor] Possibly two LORs: entropy harvest mutex and
 scrlock, and entropy harvest mutex and sleepq chain
Date: Mon, 24 Nov 2014 17:40:35 +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: 10.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: ellisw@panasas.com
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-195262-8-uL4zPCDIYb@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-195262-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-195262-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.18-1
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: Mon, 24 Nov 2014 17:40:35 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195262

--- Comment #4 from Ellis H. Wilson III <ellisw@panasas.com> ---
Many thanks to Xin Li for the rapid patch and excellent explanation!  I can
confirm with the attached patch applied to my 10.1 release bits, and the kernel
recompiled and reinstalled, we boot without panic.  Tested via ten reboots of
my VM instance of 10.1 with the patch, with both clean and unclean reboots.

I'm not sure what protocol is for declaring this fixed or not as this is my
first bug report for FreeBSD.  So I apologize if I should be marking this
closed or what.  Please advise.

Last, it would be ideal in my (perhaps naive) mind if we could return to a
default kernel configuration without WITNESS_SKIPSPIN so these bugs are given
attention naturally, rather than people having to run a non-standard
configuration in order to expose them.  Thoughts?

-- 
You are receiving this mail because:
You are the assignee for the bug.