Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 4 Aug 2017 19:53:07 +0200
From:      Ben RUBSON <ben.rubson@gmail.com>
To:        FreeBSD Net <freebsd-net@freebsd.org>
Subject:   Re: mlx4en, timer irq @100%...
Message-ID:  <468D8DC1-2685-4C04-A830-03F8BEFA3408@gmail.com>
In-Reply-To: <473e881e-4b36-1538-2d92-7db37fa6f6a5@selasky.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> <473e881e-4b36-1538-2d92-7db37fa6f6a5@selasky.org>

next in thread | previous in thread | raw e-mail | index | archive | help

> On 04 Aug 2017, at 19:45, Hans Petter Selasky <hps@selasky.org> wrote:
>=20
> On 08/04/17 19:42, Ben RUBSON wrote:
>>> On 04 Aug 2017, at 19:31, Hans Petter Selasky <hps@selasky.org> =
wrote:
>>>=20
>>> 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
>>>=20
>>> Hi,
>>>=20
>>> 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().
>> Still here since my log catch 30 minutes ago, and sounds like it does =
not want to disappear.
>>> I'm CC'ing Glebius hence he's been involved with timer issues in the =
kernel earlier.
>> 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.
>=20
> Hi,
>=20
> I guess we need to involve kgdb to get the full backtrace. Let's wait =
and see if anyone here knows how to do it right so the machine doesn't =
crash and the state is lost.

I used to test kernel dump with "sysctl debug.kdb.panic=3D1" and it =
worked correctly.
However I'm not sure about debug.minidump, if we can have it enabled or =
if it should be set to 0 in our case.
Let's wait for others to be sure yes.

Ben=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?468D8DC1-2685-4C04-A830-03F8BEFA3408>