Hmm, are you on a i386 box or an alpha box? IIRC there are some
strange spinlock problems on the alpha that may have required
patching after untarring the source. If that's it, check out the
archives on -general or -hackers.
Stephan Szabo
sszabo@bigpanda.com
On Wed, 16 Aug 2000, Darrin Ladd wrote:
> Howdy Folks,
>
> I sent this inquiry out yesterday and have not seen any responses. Does
> anyone have a suggestion on a different list or a site that I can go to that
> may be able to assist me? I would really appreciate any guidance that you
> could give me.
>
> Thanks!
> Darrin
>
>
> >From: "Darrin Ladd" <darrin_ladd@hotmail.com>
> >To: pgsql-general@postgresql.org
> >Subject: [GENERAL]regression test failure on initdb
> >Date: Tue, 15 Aug 2000 17:54:10 EDT
> >
> >Hi,
> >
> >I am having a little trouble with the runcheck regression testing of the
> >compilation that I just performed. I am running on a Linux Red-Hat 6.2 OS
> >and currently have Postgres 6.5.3 running in non-default directories and on
> >a non-default port. I wanted to install Postgres 7.0.2 in the default
> >areas
> >and convert over. I configured the default area and compiled the new
> >version. Then I go to perform the runcheck regression test and it fails on
> >the initdb step. In the initdb.log the error that is provided is:
> >
> >FATAL: s_lock(20306f80) at spinc:116, stuck spinlock. Aborting
> >
> >This seems serious, but I have no idea where to start to fix this. Please
> >point me in the right direction if you can.
> >
> >Thanks!
> >Darrin
> >________________________________________________________________________
> >Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
> >
>
> ________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
>