From nobody@FreeBSD.org  Thu Mar 25 18:16:34 2010
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 1DD2C106566B
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 25 Mar 2010 18:16:34 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21])
	by mx1.freebsd.org (Postfix) with ESMTP id 0D18E8FC22
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 25 Mar 2010 18:16:34 +0000 (UTC)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.14.3/8.14.3) with ESMTP id o2PIGXJf029024
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 25 Mar 2010 18:16:33 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.14.3/8.14.3/Submit) id o2PIGX3D029023;
	Thu, 25 Mar 2010 18:16:33 GMT
	(envelope-from nobody)
Message-Id: <201003251816.o2PIGX3D029023@www.freebsd.org>
Date: Thu, 25 Mar 2010 18:16:33 GMT
From: Ben Cadieux <ben.cadieux@gmail.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: spin lock held too long amd64 mp_machdep.c
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         145039
>Category:       kern
>Synopsis:       [emulation] spin lock held too long amd64 mp_machdep.c
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    vbox
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Mar 25 18:20:02 UTC 2010
>Closed-Date:    Mon Nov 29 22:29:07 UTC 2010
>Last-Modified:  Mon Nov 29 22:29:07 UTC 2010
>Originator:     Ben Cadieux
>Release:        FreeBSD 8.0-RELEASE & 8.0-STABLE
>Organization:
>Environment:
FreeBSD underworld.example.org 8.0-STABLE FreeBSD 8.0-STABLE #0: Wed Mar 24 09:54:03 PDT 2010    sol@underworld.example.org:/usr/obj/usr/src/sys/UNDERWORLD  amd64
>Description:
I'm running 2 jails, and 2 VirtualBox sessions (with Win2k3 Server &
WinXP).  If I only run 1 VirtualBox session, the problem seems to be rarer.

There doesn't seem to be too much of a pattern other than increased load
increases the risk.  Sometimes the server is stable for a week, other
times minutes or hours.

spin lock 0xffffffff80752f80 (smp rendezvous) held by 0xffffff0001879740 (tid 100022) too long
exclusive spin mutex smp rendezvous (smp rendezvous) r = 0 (0xffffffff80752f80)
locked @ /usr/src/sys/amd64/amd64/mp_machdep.c:992
panic: spin lock held too long
cpuid = 4
Uptime: 8m30s

>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:

From: Howard Feldman <hfeldman@earthlink.net>
To: Ben Cadieux <ben.cadieux@gmail.com>, freebsd-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: amd64/145039: spin lock held too long amd64 mp_machdep.c
Date: Thu, 25 Mar 2010 15:44:07 -0400 (EDT)

 Hi,
 
 I've had the same issue with the AMD64 version of Release 8.0.  However,
 I'm not running jails but the issue seems to occur when running two
 VirtualBox sessions-one running FreeBSD version 8.0 and the other
 running Windows XP.  I'm running under KDE.  I have 12 GB main memory.
 
 I've tried to run Windows XP under load but could not repeat the panic.
 
 It seems that the common factor here is running VirtualBox and Windows XP.
 
 ...howard
 
From: Ben Cadieux <ben.cadieux@gmail.com>
To: Howard Feldman <hfeldman@earthlink.net>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: amd64/145039: spin lock held too long amd64 mp_machdep.c
Date: Thu, 25 Mar 2010 13:12:14 -0700

 Hello,
 
 Thanks for the input, Howard!
 
 I had the spinlock problem (without WITNESS enabled) while only
 running Win2k3 in VirtualBox.  I can only assume it's the same
 error... it just happens less often.
 
 I should've included more details in case hardware or something else
 is related.  I'm using a SuperMicro board (X8SIL-F-O) with 8GB of ram
 and an Intel Xeon X3440.    Two 'em' NICs, only using one at the
 moment.
 
 Best Regards,
 Ben Cadieux

From: Martin Matuska <mm@FreeBSD.org>
To: bug-followup@FreeBSD.org, ben.cadieux@gmail.com
Cc:  
Subject: Re: amd64/145039: spin lock held too long amd64 mp_machdep.c
Date: Thu, 13 May 2010 15:00:53 +0200

 This is a problem of the VirtualBox kernel module and/or interaction of
 it with VirtualBox.
 I experienced the same problem.
 
 Also this user here:
 http://lists.freebsd.org/pipermail/freebsd-emulation/2010-January/007359.html
 
 You should compile your kernel with INVARIANT_SUPPORT, INVARIANTS and DEBUG
 and report more information about the panics.
 
 
Responsible-Changed-From-To: freebsd-amd64->freebsd-vbox 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Wed Aug 4 03:39:40 UTC 2010 
Responsible-Changed-Why:  
Apparently a problem with interaction with virtualbox. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=145039 
Responsible-Changed-From-To: freebsd-vbox->vbox 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Wed Aug 4 03:53:27 UTC 2010 
Responsible-Changed-Why:  
fix brain-o in assignment. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=145039 

From: Ben Cadieux <ben.cadieux@gmail.com>
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: kern/145039: [emulation] spin lock held too long amd64 mp_machdep.c
Date: Mon, 29 Nov 2010 14:01:09 -0800

 This is fixed.
State-Changed-From-To: open->closed 
State-Changed-By: beat 
State-Changed-When: Mon Nov 29 22:29:06 UTC 2010 
State-Changed-Why:  
Closed on submitters request. Thanks for the feedback! 

http://www.freebsd.org/cgi/query-pr.cgi?pr=145039 
>Unformatted:
