Re: Solaris ASM problem

From: Kris Jurka <books(at)ejurka(dot)com>
To: Theo Schlossnagle <jesus(at)omniti(dot)com>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Solaris ASM problem
Date: 2006-04-28 21:38:39
Message-ID: Pine.BSO.4.63.0604281637310.11941@leary2.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers pgsql-patches

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.

Kris Jurka

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Theo Schlossnagle 2006-04-28 21:50:42 Re: Solaris ASM problem
Previous Message Theo Schlossnagle 2006-04-28 21:30:59 Re: Solaris ASM problem

Browse pgsql-hackers by date

  From Date Subject
Next Message Theo Schlossnagle 2006-04-28 21:50:42 Re: Solaris ASM problem
Previous Message Theo Schlossnagle 2006-04-28 21:30:59 Re: Solaris ASM problem

Browse pgsql-patches by date

  From Date Subject
Next Message Theo Schlossnagle 2006-04-28 21:50:42 Re: Solaris ASM problem
Previous Message Theo Schlossnagle 2006-04-28 21:30:59 Re: Solaris ASM problem