From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 25 20:10:07 2010 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D1402106566B for ; Thu, 25 Mar 2010 20:10:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A4D128FC16 for ; Thu, 25 Mar 2010 20:10:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o2PKA79E001341 for ; Thu, 25 Mar 2010 20:10:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o2PKA7SS001340; Thu, 25 Mar 2010 20:10:07 GMT (envelope-from gnats) Date: Thu, 25 Mar 2010 20:10:07 GMT Message-Id: <201003252010.o2PKA7SS001340@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Howard Feldman Cc: Subject: Re: amd64/145039: spin lock held too long amd64 mp_machdep.c X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Howard Feldman List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Mar 2010 20:10:07 -0000 The following reply was made to PR amd64/145039; it has been noted by GNATS. From: Howard Feldman To: Ben Cadieux , 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 -----Original Message----- >From: Ben Cadieux >Sent: Mar 25, 2010 2:16 PM >To: freebsd-gnats-submit@FreeBSD.org >Subject: amd64/145039: spin lock held too long amd64 mp_machdep.c > > >>Number: 145039 >>Category: amd64 >>Synopsis: spin lock held too long amd64 mp_machdep.c >>Confidential: no >>Severity: critical >>Priority: high >>Responsible: freebsd-amd64 >>State: open >>Quarter: >>Keywords: >>Date-Required: >>Class: sw-bug >>Submitter-Id: current-users >>Arrival-Date: Thu Mar 25 18:20:02 UTC 2010 >>Closed-Date: >>Last-Modified: >>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: >>Unformatted: >_______________________________________________ >freebsd-amd64@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 >To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org"