From owner-freebsd-stable@FreeBSD.ORG Fri Apr 2 14:53:23 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0CE201065670 for ; Fri, 2 Apr 2010 14:53:23 +0000 (UTC) (envelope-from oleg.lomaka@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.152]) by mx1.freebsd.org (Postfix) with ESMTP id 8D2948FC12 for ; Fri, 2 Apr 2010 14:53:22 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id l26so100068fgb.13 for ; Fri, 02 Apr 2010 07:53:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=HX5CZUGv+ShbPvwF72zBRKtuCCwOjZpYusAodAM86dE=; b=tF9aOZ7gVloH5HRelSdcLIlgzGLbVUYgiTD9wLdQ8NQJVD8jsyiLSwa0akj5Fn/q0i lpyx9PUuakFn+hC6f7CGf6pN4/2aQY0u7fl0hqKQC1ipwJOjVf6xXpvsTclQmoDqCE1N aqFjkUklIYGxtjQ+dgvjA0th/BsYohI3883J4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=BQOmevsdmL4CLZBzKfbpPDtbt15Sa41nzTkiK28Q13DVlpNS7iZD9YU7suiGRpkYIS gDorOykFyLugBu0sRYlG2QsJly5W7cK6DwrICA43jHfcKeBWBgeceen/+6JC7i+1n/Do gNhCk6Vl0dty56qE5jwEHz8623GZ/R3QUI/nc= Received: by 10.87.47.3 with SMTP id z3mr893165fgj.74.1270220000716; Fri, 02 Apr 2010 07:53:20 -0700 (PDT) Received: from [172.16.224.129] ([92.249.104.41]) by mx.google.com with ESMTPS id e3sm8183666fga.9.2010.04.02.07.53.19 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 02 Apr 2010 07:53:20 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii From: Oleg Lomaka In-Reply-To: <20100402131114.T40281@maildrop.int.zabbadoz.net> Date: Fri, 2 Apr 2010 17:53:18 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: 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> To: "Bjoern A. Zeeb" X-Mailer: Apple Mail (2.1078) Cc: freebsd-stable@freebsd.org Subject: Re: panic during work with jailed postgresql8.4 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Apr 2010 14:53:23 -0000 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.