From owner-freebsd-net@freebsd.org Fri Aug 4 17:53:10 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 BE83EDC0D73 for ; Fri, 4 Aug 2017 17:53:10 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FD9671715 for ; Fri, 4 Aug 2017 17:53:10 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wm0-x241.google.com with SMTP id y206so6453428wmd.5 for ; Fri, 04 Aug 2017 10:53:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=8Zc5tVKdKhUHHB3/3zdqpcWWkatr0ZBDjXVSjZ/rKu0=; b=UWFt6Rymh1g4xU61uPKtQRjMTYvUQPML72ICm+J9rJXUzuWIQthsSA2zTfZbpdFuwA YRWbeAOni52MWYWBqiJyCcZbOtUvsebczudyeQCE9weH2/YQVGd9Wd+MBm4d6HL9UaRS Z1byRUb/Ay1kqKkT6fqDG646KgnRjbFy5GrKMz0/wfmSacwJIGfWgm5tSBm2PrCDrU86 Q9XjOcuDFvttNI8G9zPc3fIedw+n3Yl74+z8nrYcHByBEv6JuCfB5G36iID++t41CsSG t1vxG7l4w0oJIRfivtsL83pG+omhLutI+S3kjFfn/ErIRw0slVJ0px94eqnHAiB6TDHo sZOg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=8Zc5tVKdKhUHHB3/3zdqpcWWkatr0ZBDjXVSjZ/rKu0=; b=LP0qUy0m9egJKF1nlbaKORBtMU1SuX1mJhHUxEUANkQOywrzlRjnC61KI94LU3KSQs FKECUrLFkoTHKC4lFuyKJuFnAYRbyHYuPFKfgevEZZiZAzxH6em6jAEcyhA932UUiEta T84DcZBnLjDFEWdzUjGLpGP9wnH91Dx1kPtAZDNBJkkaJNHjsomCpTLT7YdmCE1UwIXA vrqi+pGd6j+1l0oZj+ZD+9rr9rb67ZqfN8FP6ex4xAfOMXa1g+eCNB2tl9lgsKq4vKzp 2iTGmrZbHZKsgPIHqpHuOt2srxXV75wt/N4r/SA2RwXfTBgpoACBRUU7EyqtkRDG6L0n y56w== X-Gm-Message-State: AHYfb5jmJRn2zjgbJmCugipkP+h1/FF1qSox5adylMpB85mbK4HTMMlg huPTPaMhJg3bTopAWfs= X-Received: by 10.28.2.8 with SMTP id 8mr1871483wmc.4.1501869188629; Fri, 04 Aug 2017 10:53:08 -0700 (PDT) Received: from ben.home (LFbn-1-6951-179.w90-116.abo.wanadoo.fr. [90.116.132.179]) by smtp.gmail.com with ESMTPSA id 53sm5871419wry.31.2017.08.04.10.53.07 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 04 Aug 2017 10:53:08 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: mlx4en, timer irq @100%... From: Ben RUBSON In-Reply-To: <473e881e-4b36-1538-2d92-7db37fa6f6a5@selasky.org> Date: Fri, 4 Aug 2017 19:53:07 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <468D8DC1-2685-4C04-A830-03F8BEFA3408@gmail.com> References: <72b9de84-5572-3737-b274-34d2c5cdf634@selasky.org> <91DCB96E-4C08-44C5-94E7-E7C686DEFE5F@gmail.com> <4DF74CB8-23D2-4CCF-B699-5B86DAEA65E5@gmail.com> <473e881e-4b36-1538-2d92-7db37fa6f6a5@selasky.org> To: FreeBSD Net X-Mailer: Apple Mail (2.3124) 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:53:10 -0000 > On 04 Aug 2017, at 19:45, Hans Petter Selasky wrote: >=20 > On 08/04/17 19:42, Ben RUBSON wrote: >>> On 04 Aug 2017, at 19:31, Hans Petter Selasky = 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=