freebsd-amd64 Digest, Vol 353, Issue 4
freebsd-am...@freebsd.org
freebs...@freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
or, via email, send a message with subject or body 'help' to
freebsd-am...@freebsd.org
You can reach the person managing the list at
freebsd-a...@freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-amd64 digest..."
Today's Topics:
1. Re: amd64/112222: [libc] 32-bit libc incorrectly converts
some FP numbers (Alexander Best)
2. Re: amd64/112222: [libc] 32-bit libc incorrectly converts
some FP numbers (re...@FreeBSD.org)
3. amd64/145039: spin lock held too long amd64 mp_machdep.c
(Ben Cadieux)
4. Re: amd64/145039: spin lock held too long amd64 mp_machdep.c
(Howard Feldman)
5. Re: amd64/145039: spin lock held too long amd64 mp_machdep.c
(Ben Cadieux)
----------------------------------------------------------------------
Message: 1
Date: Thu, 25 Mar 2010 17:30:09 GMT
From: Alexander Best <alexb...@wwu.de>
Subject: Re: amd64/112222: [libc] 32-bit libc incorrectly converts
some FP numbers
To: freebs...@FreeBSD.org
Message-ID: <201003251730....@freefall.freebsd.org>
The following reply was made to PR amd64/112222; it has been noted by GNATS.
From: Alexander Best <alexb...@wwu.de>
To: <bug-fo...@FreeBSD.org>
Cc: Bruce Cran <br...@cran.org.uk>
Subject: Re: amd64/112222: [libc] 32-bit libc incorrectly converts some FP
numbers
Date: Thu, 25 Mar 2010 18:29:02 +0100 (CET)
if this issue has indeed been fixed by gcc commit r117331
(http://gcc.gnu.org/viewcvs?view=revision&revision=117331) the only branch it
still applies to is stable/6.
since it is very unlikely that a committer will backport these changes to gcc
3.4.6 the pr should be closed.
--
Alexander Best
------------------------------
Message: 2
Date: Thu, 25 Mar 2010 18:06:15 GMT
From: re...@FreeBSD.org
Subject: Re: amd64/112222: [libc] 32-bit libc incorrectly converts
some FP numbers
To: peter...@optushome.com.au, re...@FreeBSD.org,
freebs...@FreeBSD.org
Message-ID: <201003251806....@freefall.freebsd.org>
Synopsis: [libc] 32-bit libc incorrectly converts some FP numbers
State-Changed-From-To: open->closed
State-Changed-By: remko
State-Changed-When: Thu Mar 25 18:06:15 UTC 2010
State-Changed-Why:
This had been resolved in all branches (head/8/7) and can no longer be
reproduced.
http://www.freebsd.org/cgi/query-pr.cgi?pr=112222
------------------------------
Message: 3
Date: Thu, 25 Mar 2010 18:16:33 GMT
From: Ben Cadieux <ben.c...@gmail.com>
Subject: amd64/145039: spin lock held too long amd64 mp_machdep.c
To: freebsd-gn...@FreeBSD.org
Message-ID: <201003251816....@www.freebsd.org>
>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 s...@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:
------------------------------
Message: 4
Date: Thu, 25 Mar 2010 20:10:07 GMT
From: Howard Feldman <hfel...@earthlink.net>
Subject: Re: amd64/145039: spin lock held too long amd64 mp_machdep.c
To: freebs...@FreeBSD.org
Message-ID: <201003252010....@freefall.freebsd.org>
The following reply was made to PR amd64/145039; it has been noted by GNATS.
From: Howard Feldman <hfel...@earthlink.net>
To: Ben Cadieux <ben.c...@gmail.com>, freebsd-gn...@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 <ben.c...@gmail.com>
>Sent: Mar 25, 2010 2:16 PM
>To: freebsd-gn...@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 s...@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:
>_______________________________________________
>freebs...@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
>To unsubscribe, send any mail to "freebsd-amd6...@freebsd.org"
------------------------------
Message: 5
Date: Thu, 25 Mar 2010 20:40:02 GMT
From: Ben Cadieux <ben.c...@gmail.com>
Subject: Re: amd64/145039: spin lock held too long amd64 mp_machdep.c
To: freebs...@FreeBSD.org
Message-ID: <201003252040....@freefall.freebsd.org>
The following reply was made to PR amd64/145039; it has been noted by GNATS.
From: Ben Cadieux <ben.c...@gmail.com>
To: Howard Feldman <hfel...@earthlink.net>
Cc: freebsd-gn...@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 <hfel...@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.c...@gmail.com>
>>Sent: Mar 25, 2010 2:16 PM
>>To: freebsd-gn...@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 =A0...@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:
>>_______________________________________________
>>freebs...@freebsd.org mailing list
>>http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
>>To unsubscribe, send any mail to "freebsd-amd6...@freebsd.org"
>
>
------------------------------
End of freebsd-amd64 Digest, Vol 353, Issue 4
*********************************************