From owner-freebsd-current@freebsd.org Thu Apr 27 17:03:08 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 6E8AAD532C4 for ; Thu, 27 Apr 2017 17:03:08 +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 33048890 for ; Thu, 27 Apr 2017 17:03:07 +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 v3RH2vIX052102 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=FAIL); Thu, 27 Apr 2017 13:03:05 -0400 (EDT) (envelope-from tom@uffner.com) Subject: Re: panics in network stack in 12-current To: "Andrey V. Elsukov" , freebsd-current References: <92a10822-3fde-f839-1836-92e8d936f2b6@yandex.ru> <841f1d22-b563-862c-a367-a475356781ef@uffner.com> <9c1f65f4-162b-a83d-1246-31d9e0525e4a@uffner.com> From: Tom Uffner Message-ID: <0dda5011-e74c-50d1-e8fa-088f123e30d2@uffner.com> Date: Thu, 27 Apr 2017 13:02:57 -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: Thu, 27 Apr 2017 17:03:08 -0000 Andrey V. Elsukov wrote: > On 27.04.2017 08:42, Tom Uffner wrote: >> r315956 panicked about 22 min after boot. failed to dump a core. > > Why not update to the latest revision? I did several times a while ago, but didn't get a panic free system. I was hoping to bisect the point the point where the problem actually occurred and maybe send a patch instead of just begging for help. trouble was, I got down to a small number of revisions and none of them had any changes that looked even remotely related to my problem. I'll give today's HEAD a try. > Probably this is flowtable related, don't think it is usable. > Anyway we need the trace to determine the cause. Also it seems you have > VIMAGE enabled. This also have some known panics. OK, I will also try disabling flowtable. Not sure about VIMAGE. I don't have it specifically enabled, but I don't have it specifically disabled either if it defaults to on. I don't know much about it. I have also tried using the GENERIC kernel instead of my custom one, but it was even less stable on my hardware and bricked the system instead of panicking and producing a core dump.