From owner-freebsd-net@freebsd.org Wed Jan 11 09:43:18 2017 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 B9676CAAF1B for ; Wed, 11 Jan 2017 09:43:18 +0000 (UTC) (envelope-from jpa@semihalf.com) Received: from mail-vk0-x22f.google.com (mail-vk0-x22f.google.com [IPv6:2607:f8b0:400c:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 81E1D16DD for ; Wed, 11 Jan 2017 09:43:18 +0000 (UTC) (envelope-from jpa@semihalf.com) Received: by mail-vk0-x22f.google.com with SMTP id 137so376661419vkl.0 for ; Wed, 11 Jan 2017 01:43:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semihalf-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=3dEYdjvlSIL0IyVYGffTD2Zx20SuxV2WnHKdPRyg95Y=; b=YrN0yV5cqEB/8Tf4EqXCbCvNoBZLlfq5vPledTgmysztgGNaPg/qfosB3Hz6etRaZt Sr9n4RVJRNs0TbUJAFaWcXc77Ic+aZOhgk4CzS23nzJuD/mgZsgfkArJqv+zySA1Wqnm H4NKRKIxUd1KX647iORVHd3HJN6tUUzC6HRR359aEv43G8CrXz86mwXOdre+szUUSKvK 9xC3N+96YaXXE+wx9/9GPQ/MIHDEOZej8nlJt7upDoMqHVA3ZWjrjb4uKmpTmA8iZGMF iexl5EdEmd5Srh+2RBATQlDGR5lUllucqeYDEGNb190vf1BX9Tg84+2FqENEyawmvDSY kesQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=3dEYdjvlSIL0IyVYGffTD2Zx20SuxV2WnHKdPRyg95Y=; b=lQTfLpbljr9Mzv2I88jFIHtcd4EyamjBEvlo83i/PU6AiBBwjYsVeiBF005ySanLU3 ksFnD6Oy6fxoxnPzrGVIi8gFgwhe/e+CVHe42tEbQkWkDI7KO2iQVircwOEgLhpBWRwn deD+8wkZSdq8zyM7D2n2A/v7O/R11/gzjD4gpmnY4fERNjgM6zjm6SF+4YjUPq6kVaTV jmDxDEuqBVeM/G0BfdOX2vtlY3nDpgPc2eyWv/DJdKM2E6W0qfBIudK6YyOKF5M/WE9e iypM5Lr4gs04zj2hDHlSSd29AYSETIgvYFkrxpt5v5/a9Eu8UoId8dJ1GpYpCI3A3cBX mN3A== X-Gm-Message-State: AIkVDXJ4WCSLktc91nKLActm2TwbqXjeYTBjZZWqyiL6dtySP8cRK+GcnsOiP7NxSkSYVuem/0xbT1hMHRPomg== X-Received: by 10.31.87.6 with SMTP id l6mr3056312vkb.116.1484127797554; Wed, 11 Jan 2017 01:43:17 -0800 (PST) MIME-Version: 1.0 Received: by 10.31.46.18 with HTTP; Wed, 11 Jan 2017 01:42:47 -0800 (PST) In-Reply-To: <20161129190509.GO27748@FreeBSD.org> References: <20161128221033.GM55731@strugglingcoder.info> <20161129190509.GO27748@FreeBSD.org> From: Jakub Palider Date: Wed, 11 Jan 2017 10:42:47 +0100 Message-ID: Subject: Re: FLOWTABLE aka TCP route caching panic To: Gleb Smirnoff Cc: hiren panchasara , freebsd-net@freebsd.org, karels@freebsd.org Content-Type: text/plain; charset=UTF-8 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: Wed, 11 Jan 2017 09:43:18 -0000 On Tue, 29 Nov 2016 11:05:09 -0800 Gleb Smirnoff wrote: > On Mon, Nov 28, 2016 at 02:10:33PM -0800, hiren panchasara wrote: > h> > Hi, > h> > I have found that last month (19 Oct) the problem appeared on this list, > h> > and to my experience it persists, both on VM and bare metal installation > h> > (HEAD from yesterday). I looks that enabling FLOWTABLE option is the only > h> > source of this fault happening. It appears on our setup in 80% cases within > h> > one hour from boot up. > h> > From our debugging, it is caused by lock on DESTROYED lock. Did you find a > h> > solution to this problem? > > Not yet. > > I'm pretty sure that reverting my r307234 will fix your crashes. However, I still > believe that r307234 is a proper way of fixing things, not r300854 which just > plugged the problem in the nearest place to the crash. But as we all see r307234 > is definitely missing some code path, which still allows for stale route to be > referenced. > > -- > Totus tuus, Glebius. Thank you for your pointer, in helped at some point. The problem however returned, especially when under heavy, continuous load. We are running 4 iperf3 processes, each having 4 threads, and the machine dies after 30-60 minutes of TCP traffic. I am running rS30911112 from Nov 24. On FreeBSD 11.0-RELEASE this problem (1 full day of testing) was not noticed. Could you point to related commits that might also influence this behaviour? Thanks, Jakub