Re: Solaris ASM problem - Mailing list pgsql-hackers

From Theo Schlossnagle
Subject Re: Solaris ASM problem
Date
Msg-id 44528E32.8090308@omniti.com
Whole thread Raw
In response to Re: Solaris ASM problem  (Kris Jurka <books@ejurka.com>)
List pgsql-hackers
Kris Jurka wrote:

>
>
> On Fri, 28 Apr 2006, Theo Schlossnagle wrote:
>
>> Kris Jurka wrote:
>>
>>> Anyway the test exits with
>>> Stuck spinlock (80618e9) detected at ./s_lock.c:355.
>>>
>>> on a linux gcc build this exits with
>>> Stuck spinlock (0x5013ad) detected at ./s_lock.c:402.
>>
>>
>> This seems like a different problem, no?  The patch I sent in didn't 
>> touch any of the linux assembly bits.  The linux test should pass to 
>> the end without an issue right?
>>
>
> No, that's the desired ending.  It prints:
>
> S_LOCK_TEST: this will print 1000 stars and then
>              exit with a 'stuck spinlock' message
>              if S_LOCK() and TAS() are working.
>
> The solaris version is just getting stuck before at another point before
> the expected stuck point.

My workstation is running 32bit solaris.. I can build and debug it 
here...  I'll give that a spin (hehe).

-- 
// Theo Schlossnagle
// Principal Engineer -- http://www.omniti.com/~jesus/
// Ecelerity: Run with it. -- http://www.omniti.com/



pgsql-hackers by date:

Previous
From: Theo Schlossnagle
Date:
Subject: Re: Solaris ASM problem
Next
From: Theo Schlossnagle
Date:
Subject: Re: Solaris ASM problem