Skip site navigation (1) Skip section navigation (2)

Re: Solaris ASM problem

From: Theo Schlossnagle <jesus(at)omniti(dot)com>
To: Kris Jurka <books(at)ejurka(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:30:59
Message-ID: 44528993.2040508@omniti.com (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackerspgsql-patches
Kris Jurka wrote:

>
>
> On Fri, 28 Apr 2006, Theo Schlossnagle wrote:
>
>> The file that uses the spinlocks:
>> /src/backend/storage/lmgr/s_lock.c
>>
>> can be compiled standalone with -DS_LOCK_TEST
>>
>
> To get the test to compile I had to link in tas.o as the attached 
> patch shows.  Unfortunately this doesn't work for platforms that don't 
> have a tas.o, bailing out with file not found.  Perhaps it's not 
> important to fix this test, but I thought I'd mention it.
>
> 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?

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


In response to

Responses

pgsql-hackers by date

Next:From: Kris JurkaDate: 2006-04-28 21:38:39
Subject: Re: Solaris ASM problem
Previous:From: Kris JurkaDate: 2006-04-28 21:18:49
Subject: Re: Solaris ASM problem

pgsql-committers by date

Next:From: Kris JurkaDate: 2006-04-28 21:38:39
Subject: Re: Solaris ASM problem
Previous:From: Kris JurkaDate: 2006-04-28 21:18:49
Subject: Re: Solaris ASM problem

pgsql-patches by date

Next:From: Kris JurkaDate: 2006-04-28 21:38:39
Subject: Re: Solaris ASM problem
Previous:From: Kris JurkaDate: 2006-04-28 21:18:49
Subject: Re: Solaris ASM problem

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group