Date: Thu, 25 Mar 2010 20:40:02 GMT From: Ben Cadieux <ben.cadieux@gmail.com> To: freebsd-amd64@FreeBSD.org Subject: Re: amd64/145039: spin lock held too long amd64 mp_machdep.c Message-ID: <201003252040.o2PKe256028341@freefall.freebsd.org>
index | next in thread | raw e-mail
The following reply was made to PR amd64/145039; it has been noted by GNATS. 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 On Thu, Mar 25, 2010 at 12:44 PM, Howard Feldman <hfeldman@earthlink.net> w= rote: > Hi, > > I've had the same issue with the AMD64 version of Release 8.0. =A0However= , I'm not running jails but the issue seems to occur when running two Virtu= alBox sessions-one running FreeBSD version 8.0 and the other running Window= s XP. =A0I'm running under KDE. =A0I 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 <ben.cadieux@gmail.com> >>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: =A0 =A0 =A0 =A0 145039 >>>Category: =A0 =A0 =A0 amd64 >>>Synopsis: =A0 =A0 =A0 spin lock held too long amd64 mp_machdep.c >>>Confidential: =A0 no >>>Severity: =A0 =A0 =A0 critical >>>Priority: =A0 =A0 =A0 high >>>Responsible: =A0 =A0freebsd-amd64 >>>State: =A0 =A0 =A0 =A0 =A0open >>>Quarter: >>>Keywords: >>>Date-Required: >>>Class: =A0 =A0 =A0 =A0 =A0sw-bug >>>Submitter-Id: =A0 current-users >>>Arrival-Date: =A0 Thu Mar 25 18:20:02 UTC 2010 >>>Closed-Date: >>>Last-Modified: >>>Originator: =A0 =A0 Ben Cadieux >>>Release: =A0 =A0 =A0 =A0FreeBSD 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 =A0 =A0sol@underworld.example.org:/usr/obj/usr/src/sys= /UNDERWORLD =A0amd64 >>>Description: >>I'm running 2 jails, and 2 VirtualBox sessions (with Win2k3 Server & WinX= P). =A0If 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. =A0Sometimes the server is stable for a week, other tim= es minutes or hours. >> >>spin lock 0xffffffff80752f80 (smp rendezvous) held by 0xffffff0001879740 = (tid 100022) too long >>exclusive spin mutex smp rendezvous (smp rendezvous) r =3D 0 (0xffffffff8= 0752f80) >>locked @ /usr/src/sys/amd64/amd64/mp_machdep.c:992 >>panic: spin lock held too long >>cpuid =3D 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" > >home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201003252040.o2PKe256028341>