ports/117625: PostgreSQL 8.2.5 coredumps on FreeBSD 7

Michael michael at gameservice.ru
Mon Oct 29 11:50:03 UTC 2007


>Number:         117625
>Category:       ports
>Synopsis:       PostgreSQL 8.2.5 coredumps on FreeBSD 7
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Oct 29 11:50:01 UTC 2007
>Closed-Date:
>Last-Modified:
>Originator:     Michael
>Release:        RELENG_7
>Organization:
>Environment:
FreeBSD s4.picred.com 7.0-BETA1 FreeBSD 7.0-BETA1 #6: Fri Oct 26 18:36:43 MSD 2007     spc at s4.picred.com:/usr/obj/usr/src/sys/PR  i386
>Description:
PostgreSQL 8.2.5 compiled from ports core dumps on FreeBSD 7
(RELENG_7), it works without problem on FreeBSD 6-STABLE (RELENG_6).

I've asked pgsql-bugs about this issue, and they answered,
that probably FreeBSD 7 have problems with spinlocks:
http://www.nabble.com/PostgreSQL-crash-on-Freebsd-7-t4693969.html

Some info:

(gdb) bt
#0  0x485dc277 in kill () from /lib/libc.so.7
#1  0x485dc1d6 in raise () from /lib/libc.so.7
#2  0x485dadda in abort () from /lib/libc.so.7
#3  0x0824c075 in errfinish ()
#4  0x0824c8b1 in elog_finish ()
#5  0x081c9184 in s_lock ()
#6  0x081c8d48 in LWLockAcquire ()
#7  0x081c61ec in LockAcquire ()
#8  0x081c4289 in LockRelationOid ()
#9  0x080938fc in relation_open ()
#10 0x08096d5a in index_open ()
#11 0x08096139 in systable_beginscan ()
#12 0x08134f10 in RelationBuildTriggers ()
#13 0x08245d4d in RelationCacheInitializePhase2 ()
#14 0x08256af0 in InitPostgres ()
#15 0x081cfd13 in PostgresMain ()
#16 0x081a90ec in ClosePostmasterPorts ()
#17 0x081a9ea7 in PostmasterMain ()
#18 0x0816912f in main ()

Extract from dmesg:
pid 30622 (postgres), uid 70: exited on signal 6 (core dumped)

Extract from postmaster log:
2007-10-25 23:37:12 MSD (u=picred,db=picred)PANIC:  stuck spinlock (0x4880c3b0) detected at lwlock.c:379 
>How-To-Repeat:
I can't find what triggers coredump, it happens 2-4 times per day under high load
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the freebsd-ports-bugs mailing list