Subject: Re: Upgrade 10.5->10.6 : db crash BUS ERROR (sig 10), reproducible
To: pgsql-admin@lists.postgresql.org
References: <20190307140421.GA8362@gate.oper.dinoex.org>
 <874l8ed31p.fsf@news-spur.riddles.org.uk>
 <E4B6F953-A971-4791-8355-BC74A167A52A@FreeBSD.org>
 <87tvgeb796.fsf@news-spur.riddles.org.uk>
From: Ron <ronljohnsonjr@gmail.com>
Message-ID: <48e7067e-d7d6-2a6b-8368-34d529bbd1ed@gmail.com>
Date: Thu, 7 Mar 2019 18:02:55 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <87tvgeb796.fsf@news-spur.riddles.org.uk>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Precedence: bulk

On 3/7/19 5:30 PM, Andrew Gierth wrote:
>>>>>> "Palle" == Palle Girgensohn <girgen@FreeBSD.org> writes:
>   >> Clang's __builtin_isinf(x) function, which is supposed to test if x is
>   >> infinite, does not work reliably on i386 when the x87 registers are used
>   >> for floating point. It does work if the SSE2 registers are used instead,
>   >> which clang will do if the -msse2 option is used. The downside of course
>   >> is that the code will no longer run on CPUs that are old enough to vote.
>
>   Palle> For this reason, we build i386 with gcc starting with version
>   Palle> 10.6. the CFLAGS+=--msse2 was not realiable for all CPU:s since
>   Palle> not all i386 CPU:s support SSE2.
>
>   Palle> We had one report of a user who had SSE2 flag still on (int
>   Palle> /etc/make.conf) when building, and got the same problem.
>   Palle> [https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236025
>   Palle> <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236025>]
>
> The user in that bug report was using a Pentium 4, which supports SSE2,
> so it's not the lack of SSE2 that caused the problem.

But if it's compiled for i386 instead of i686?

> Furthermore, the crash was in XLogReadRecord, which does not use floats.
>
> So I'm going to guess that your bug 236025 is actually an alignment
> problem, with the compiler making some assumption about alignment that
> we're violating. I'll investigate and see what I can find.


-- 
Angular momentum makes the world go 'round.