On Monday 29 March 2010 20:26:08 Alex Hunsaker wrote: > > Test are para-virt VMs with "regular" kernels, production are real > > machines with hardened kernels (grsec+pax). > > Ive seen this error on a few boxes around here, using a non grsec > kernel fixes it. I never bothered to report it because I cant > reproduce it and it goes away without grsec. (2.6.30-32 IIRC, have > not tired the latest 33). Interestingly I have the *exact* same > hardware and setup (kernel/userspace/postgres etc) on a test machine > that I've never been able to trigger it on.
Thanks Alex, good to know I've not screwed up the kernel somehow. I've been using 2.6.32 with grsecurity-2.1.14-2.6.32.9-201002231820 applied. -- Mike Williams -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
