Date: Fri, 2 Apr 2010 17:53:18 +0300 From: Oleg Lomaka <oleg.lomaka@gmail.com> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: freebsd-stable@freebsd.org Subject: Re: panic during work with jailed postgresql8.4 Message-ID: <B5326E21-6CA2-4EFE-8701-C6E67B0AA8E3@gmail.com> In-Reply-To: <20100402131114.T40281@maildrop.int.zabbadoz.net> References: <44FD9C14-7114-4270-A7B6-F029995BA282@gmail.com> <20100402120137.E40281@maildrop.int.zabbadoz.net> <363ECEF2-62D3-4F97-A21D-9E10358A1065@gmail.com> <20100402131114.T40281@maildrop.int.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 2, 2010, at 4:12 PM, Bjoern A. Zeeb wrote: > On Fri, 2 Apr 2010, Oleg Lomaka wrote: >=20 >>>> uname -a >>>> FreeBSD cerberus.regredi.com 8.0-STABLE FreeBSD 8.0-STABLE #7 = r206031: Thu Apr 1 13:43:57 EEST 2010 = root@cerberus.regredi.com:/usr/obj/usr/src/sys/GENERIC amd64 >>>>=20 >>>> Link to dmesg.boot: >>>> = http://docs.google.com/leaf?id=3D0B-irbkAqk9i7OGY2ZWJiODgtOWJmMy00NDQ1LTli= ZDctZjU3N2YwNmMxNjZl&hl=3Den >>>>=20 >>>> Link to kernel core backtrace: >>>> = http://docs.google.com/Doc?docid=3D0AeirbkAqk9i7ZGc5Yzc2ZndfM2M4NzYydmRw&h= l=3Den >>>>=20 >>>> Can I help to spot this trouble by providing additional info? >>>=20 >>> Looking at the info I doubt it's related to jails or Pg in first >>> place. Have you been running that same setup already before your = Apr >>> 1st, r206031, kernel? If so, from when was your last kernel? >>=20 >> Yes, this configuration works on another server fine (8.0-STABLE = FreeBSD 8.0-STABLE #3 r205202) >>=20 >> Made few more tests. All tests I make using psql command (as it is = 100% reproducible, may be now try spot it using telnet/netcat, without = involving pg). psql accomplish login operation fine, panic appears after = i run any command like \d, so I think it depends on packet size. >>=20 >> Current picture is: >> 1. When connect from host machine - works fine. >> 2. When I connect from other server - works fine. >> 3. When connect from another jail on the same box as db's jail (tried = from few jails) - kernel fault. >>=20 >> Also tried security.jail.allow_raw_sockets on/off - nothing changes. >=20 > In addition to the private mail I have just sent you, the first thing > you might try it to updat again; I hadn't realized before that your > r206031 seems to be in the middle of a multi-commit merge from two > people. >=20 > It would be worth to update to the latest stable/8 and try again > first. That's it. r206088 works fine. Thank you for help.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B5326E21-6CA2-4EFE-8701-C6E67B0AA8E3>