Fwd: [GENERAL] stuck spinlock detected at dynahash.c

2010-10-07 Thread Timon
-- Forwarded message -- From: Timon Date: 2010/10/8 Subject: Re: [GENERAL] stuck spinlock detected at dynahash.c To: Tom Lane I have this (thanks abrtd): --- Crash ID:           26:a6235a787c4e9c6c5ab4f6eadd2168371b4e0fe3 Last crash:         Wed 06

Re: [GENERAL] stuck spinlock detected at dynahash.c

2010-10-07 Thread Tom Lane
Timon writes: > 2010/10/6 Alvaro Herrera : >>> WARNING:  pgstat wait timeout >>> WARNING:  pgstat wait timeout >>> PANIC:  stuck spinlock (0x7fd877761af8) detected at dynahash.c:981 >>> PANIC:  stuck spinlock (0x7fd877761af8) detected at dynahash.c:981 >> >> What platform is this?  Are you runnin

Re: [GENERAL] stuck spinlock detected at dynahash.c

2010-10-06 Thread Timon
no, simple dedicated server with Linux Fedora 13 x86_64 kernel-2.6.33.6-147.2.4.fc13.x86_64 2010/10/6 Alvaro Herrera : > Excerpts from Timon's message of mié oct 06 07:35:44 -0400 2010: >> today I found in logs: >> >> WARNING:  pgstat wait timeout >> WARNING:  pgstat wait timeout >> PANIC:  stuck

Re: [GENERAL] stuck spinlock detected at dynahash.c

2010-10-06 Thread Alvaro Herrera
Excerpts from Timon's message of mié oct 06 07:35:44 -0400 2010: > today I found in logs: > > WARNING: pgstat wait timeout > WARNING: pgstat wait timeout > PANIC: stuck spinlock (0x7fd877761af8) detected at dynahash.c:981 > PANIC: stuck spinlock (0x7fd877761af8) detected at dynahash.c:981 Wha

[GENERAL] stuck spinlock detected at dynahash.c

2010-10-06 Thread Timon
today I found in logs: WARNING: pgstat wait timeout WARNING: pgstat wait timeout PANIC: stuck spinlock (0x7fd877761af8) detected at dynahash.c:981 PANIC: stuck spinlock (0x7fd877761af8) detected at dynahash.c:981 ... LOG: server process (PID 8078) was terminated by signal 6: Aborted LOG: ter