From owner-freebsd-net@freebsd.org Fri Aug 4 17:33:21 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 A02A9DBFFE6 for ; Fri, 4 Aug 2017 17:33:21 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6951270AD6; Fri, 4 Aug 2017 17:33:21 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id AD0EC26080B; Fri, 4 Aug 2017 19:33:19 +0200 (CEST) Subject: Re: mlx4en, timer irq @100%... To: Ben RUBSON , FreeBSD Net , Gleb Smirnoff References: <72b9de84-5572-3737-b274-34d2c5cdf634@selasky.org> <91DCB96E-4C08-44C5-94E7-E7C686DEFE5F@gmail.com> From: Hans Petter Selasky Message-ID: Date: Fri, 4 Aug 2017 19:31:07 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: <91DCB96E-4C08-44C5-94E7-E7C686DEFE5F@gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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: Fri, 04 Aug 2017 17:33:21 -0000 On 08/04/17 19:13, Ben RUBSON wrote: > 12 100029 intr swi4: clock (0) tcp_tw_2msl_scan pfslowtimo softclock_call_cc softclock intr_event_execute_handlers ithread_loop fork_exit fork_trampoline Hi, Can you "procstat -ak" a few times and grep for swi4. If the entry above does not disappear this is the culpit. Either the callout list is corrupted or there is an issue inside tcp_tw_2msl_scan(). I'm CC'ing Glebius hence he's been involved with timer issues in the kernel earlier. --HPS