From owner-freebsd-bugs@freebsd.org  Wed Jul  1 12:13:11 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 9FD7D98F7EE
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed,  1 Jul 2015 12:13:11 +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 7317719B7
 for <freebsd-bugs@FreeBSD.org>; Wed,  1 Jul 2015 12:13:11 +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 t61CDBl7089438
 for <freebsd-bugs@FreeBSD.org>; Wed, 1 Jul 2015 12:13:11 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
Date: Wed, 01 Jul 2015 12:13:11 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
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: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter
 attachments.created
Message-ID: <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 12:13:11 -0000

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

            Bug ID: 201245
           Summary: panic: spin lock held too long
           Product: Base System
           Version: 11.0-CURRENT
          Hardware: sparc64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: lidl@pix.net

Created attachment 158219
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=158219&action=edit
core.txt.0 from panic

Noticed during testing of the 10.2-PRERELEASE iso image on a
dual-processor V240 UltraSparc:

Setting hostname: spork.pix.net.
bge0: link state changed to DOWN
spin lock 0xc0cb9e38 (smp rendezvous) held by 0xfffff80003e93240 (tid 100340)
too long
timeout stopping cpus
panic: spin lock held too long
cpuid = 1
KDB: stack backtrace:
#0 0xc0575380 at panic+0x20
#1 0xc0558e10 at _mtx_lock_spin_failed+0x50
#2 0xc0558ed8 at _mtx_lock_spin_cookie+0xb8
#3 0xc08d7b9c at tick_get_timecount_mp+0xdc
#4 0xc0583c88 at binuptime+0x48
#5 0xc08a3b8c at timercb+0x6c
#6 0xc08d7f00 at tick_intr+0x220
Uptime: 29s
Dumping 8192 MB (4 chunks)
  chunk at 0: 2147483648 bytes ... ok
  chunk at 0x100000000: 2147483648 bytes ... ok
  chunk at 0x1000000000: 2147483648 bytes ... ok
  chunk at 0x1100000000: 2147483648 bytes ... ok

Dump complete

This bug has been ongoing for quite a while.  Chris Ross dug up some
references to it, as explained here:

https://lists.freebsd.org/pipermail/freebsd-stable/2015-July/082635.html

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