From owner-freebsd-net@freebsd.org Mon Nov 28 22:15:44 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CC9E5C5A01E for ; Mon, 28 Nov 2016 22:15:44 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from mail.strugglingcoder.info (strugglingcoder.info [104.236.146.68]) by mx1.freebsd.org (Postfix) with ESMTP id BEC8C12EE; Mon, 28 Nov 2016 22:15:44 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from localhost (unknown [10.1.1.3]) (Authenticated sender: hiren@strugglingcoder.info) by mail.strugglingcoder.info (Postfix) with ESMTPA id 2ECFF17EC7; Mon, 28 Nov 2016 14:10:33 -0800 (PST) Date: Mon, 28 Nov 2016 14:10:33 -0800 From: hiren panchasara To: Jakub Palider Cc: freebsd-net@freebsd.org, karels@FreeBSD.org, glebius@FreeBSD.org Subject: Re: FLOWTABLE aka TCP route caching panic Message-ID: <20161128221033.GM55731@strugglingcoder.info> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="oiL9LJXJsdjS5rzq" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Nov 2016 22:15:44 -0000 --oiL9LJXJsdjS5rzq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable + Mike and Gleb who may provide some help/pointers. On 11/25/16 at 04:33P, Jakub Palider wrote: > Hi, > I have found that last month (19 Oct) the problem appeared on this list, > and to my experience it persists, both on VM and bare metal installation > (HEAD from yesterday). I looks that enabling FLOWTABLE option is the only > source of this fault happening. It appears on our setup in 80% cases with= in > one hour from boot up. > From our debugging, it is caused by lock on DESTROYED lock. Did you find a > solution to this problem? >=20 > Regards, > Jakub > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" --oiL9LJXJsdjS5rzq Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAABCgBmBQJYPKtRXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNEUyMEZBMUQ4Nzg4RjNGMTdFNjZGMDI4 QjkyNTBFMTU2M0VERkU1AAoJEIuSUOFWPt/lRbgIAJnIakyPSi6Q79giminTp8JI MQWKyLVaYYH1ytXcMYpFslba/KMnG0pixqCiHdUj/t9uTNwcCp+0K1sBblXn5P8V NX6W+8xoWoXo3cAlIvdElNhmUXWdBn72z3ssAPZViGVxUmPKfWXq/U1BNSSIdFhA z9/o9tbgDmRgOSyXp+AemjGT8n2l0Qo4EhXhgwVUzrTzJYHI4KaBUHo0HuPRzCpT 1PmhzJ1ApJOb9LhyGVtbQcJj+llYSdER8V84QSGHhcdYXhayao0DogMmZx98VMI3 6diH8wxeoyYNj45GPNmo3TuLf47Zw4SDTpo7f13/87zeH2WYs6QPCp5Ioof5Rlo= =J73A -----END PGP SIGNATURE----- --oiL9LJXJsdjS5rzq--