From owner-freebsd-net@freebsd.org  Mon Aug  7 16:14:12 2017
Return-Path: <owner-freebsd-net@freebsd.org>
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 1F39DDB3949
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Mon,  7 Aug 2017 16:14:12 +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 DA98F72750
 for <freebsd-net@freebsd.org>; Mon,  7 Aug 2017 16:14:11 +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 4A20226080B;
 Mon,  7 Aug 2017 18:14:09 +0200 (CEST)
Subject: Re: mlx4en, timer irq @100%...
To: Ben RUBSON <ben.rubson@gmail.com>, FreeBSD Net <freebsd-net@freebsd.org>
References: <BF3A3E47-A726-49FB-B83F-666EFC5C0FF1@gmail.com>
 <72b9de84-5572-3737-b274-34d2c5cdf634@selasky.org>
 <91DCB96E-4C08-44C5-94E7-E7C686DEFE5F@gmail.com>
 <c3fdf0bb-833d-915f-c246-9459819cd825@selasky.org>
 <4DF74CB8-23D2-4CCF-B699-5B86DAEA65E5@gmail.com>
 <40602CEA-D417-4E5B-8C68-916958D49A0B@gmail.com>
From: Hans Petter Selasky <hps@selasky.org>
Message-ID: <9c306f10-7c05-d28d-e551-a930603aaafa@selasky.org>
Date: Mon, 7 Aug 2017 18:11:55 +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: <40602CEA-D417-4E5B-8C68-916958D49A0B@gmail.com>
Content-Type: text/plain; charset=utf-8; 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 <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Aug 2017 16:14:12 -0000

On 08/04/17 21:09, Ben RUBSON wrote:
>> On 04 Aug 2017, at 19:42, Ben RUBSON <ben.rubson@gmail.com> wrote:
>>
>> Feel free to ask me whatever you need to investigate on this !
>> I let this (production :/) server in this state to have a chance to get interesting traces.
> 
> Server no more in production, I moved service to the standby node.
> So we can do everything :)
> swi4 still burning !
> 
> What is strange is that according to my monitoring, it began exactly at 15:00:00 UTC.
> Certainly a coincidence, as I can't find anything related.
> 

Hi,

Try to enter "kgdb" and run:

thread apply all bt

Look for the callout function in question.

--HPS