Date: Thu, 25 Mar 2010 18:16:33 GMT From: Ben Cadieux <ben.cadieux@gmail.com> To: freebsd-gnats-submit@FreeBSD.org Subject: amd64/145039: spin lock held too long amd64 mp_machdep.c Message-ID: <201003251816.o2PIGX3D029023@www.freebsd.org> Resent-Message-ID: <201003251820.o2PIK2l5008307@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>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:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201003251816.o2PIGX3D029023>