From owner-freebsd-current@freebsd.org Sat Apr 29 19:24:59 2017 Return-Path: Delivered-To: freebsd-current@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 E9B47D54982 for ; Sat, 29 Apr 2017 19:24:59 +0000 (UTC) (envelope-from tom@uffner.com) Received: from eris.uffner.com (eris.uffner.com [71.162.143.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "eris.uffner.com", Issuer "Uffner.com CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AC3491B36 for ; Sat, 29 Apr 2017 19:24:58 +0000 (UTC) (envelope-from tom@uffner.com) Received: from discordia.uffner.com (discordia.uffner.com [10.69.69.61]) (authenticated bits=0) by eris.uffner.com (8.14.9/8.14.9) with ESMTP id v3TJOU5G033249 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=FAIL); Sat, 29 Apr 2017 15:24:40 -0400 (EDT) (envelope-from tom@uffner.com) Subject: Re: panics in network stack in 12-current To: Hamza Sheikh , freebsd-current References: <92a10822-3fde-f839-1836-92e8d936f2b6@yandex.ru> <841f1d22-b563-862c-a367-a475356781ef@uffner.com> <9c1f65f4-162b-a83d-1246-31d9e0525e4a@uffner.com> <0dda5011-e74c-50d1-e8fa-088f123e30d2@uffner.com> From: Tom Uffner Message-ID: <5f0edb37-3862-4708-2134-2406b8c36419@uffner.com> Date: Sat, 29 Apr 2017 15:24:30 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Apr 2017 19:25:00 -0000 Hamza Sheikh wrote: > I may have encountered something similar on an EdgeRouter Lite running > r317256. It's serving as network gateway at home. After some time the > WAN connection goes dead. It starts working with either (a) > reconnecting the network cable or (b) pinging any IP on the internet > from that box. On rare occasions I had to reboot to get it to work. it doesn't sound much like my problem. i had no network issues until the system would suddenly panic and reboot. removing FLOWTABLE from my kernel might have fixed it, but it is too early to tell as I have yet to discover a reproducible way to trigger the bug. > I'm still new to FreeBSD and don't know how to collect relevant > information or whether to even determine if my issue is related to > Andrey's. Any help is really appreciated. My setup is documented in > detail in a blog post[0] if it helps. You probably don't want to hear this, but if you are new to FreeBSD, maybe you shouldn't be running current. I probably shouldn't running current and I have 35 years of BSD experience. I do it as a way of contributing to the project by alpha-testing new code when I have time. Brendan Gregg has some very good material on his site that might help you learn to collect useful info about what is going on inside your systems. http://www.brendangregg.com/Perf/freebsd_observability_tools.png http://www.brendangregg.com/