From owner-freebsd-bugs@freebsd.org  Wed Jul  1 15:31:32 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 C0516991765
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed,  1 Jul 2015 15:31:32 +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 ADE152791
 for <freebsd-bugs@FreeBSD.org>; Wed,  1 Jul 2015 15:31:32 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t61FVWnA099629
 for <freebsd-bugs@FreeBSD.org>; Wed, 1 Jul 2015 15:31:32 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: Wed, 01 Jul 2015 15:31:32 +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: lidl@pix.net
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-9apnJzhnDI@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: Wed, 01 Jul 2015 15:31:32 -0000

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

--- Comment #1 from lidl@pix.net ---
Well, here's an interesting tidbit of information:

If I comment out all the references to the bge0
interface in /etc/rc.conf (that was the only interface
being configured, via DHCP), such that no bge
devices are configured, the machine will boot.

I just did "reboot" three times in a row, and all
worked, now that bge0 isn't being configured in /etc/rc.conf.

I think this is an important bit of information to know
in tracking down this problem.

In the failure case, I had the following in my /etc/rc.conf:
ifconfig_bge0="DHCP"
ifconfig_bge0_ipv6="inet6 accept_rtadv"

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