From owner-freebsd-net@FreeBSD.ORG Wed Apr 22 06:58:42 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C0319614 for ; Wed, 22 Apr 2015 06:58:42 +0000 (UTC) Received: from goliath.siemens.de (goliath.siemens.de [192.35.17.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "goliath.siemens.de", Issuer "savelogs.saacon.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5A1331751 for ; Wed, 22 Apr 2015 06:58:41 +0000 (UTC) Received: from mail1.siemens.de (localhost [127.0.0.1]) by goliath.siemens.de (8.14.3/8.14.3) with ESMTP id t3M6wXEa012504; Wed, 22 Apr 2015 08:58:34 +0200 Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.40.130]) by mail1.siemens.de (8.14.3/8.14.3) with ESMTP id t3M6wX6I021865; Wed, 22 Apr 2015 08:58:33 +0200 Received: (from user@localhost) by curry.mchp.siemens.de (8.14.9/8.14.9) id t3M6wXQk081898; Date: Wed, 22 Apr 2015 08:58:33 +0200 From: Andre Albsmeier To: Mike Tancsa Cc: Andre Albsmeier , freebsd-net@freebsd.org Subject: Re: Intel em (82574L and 82573L) problems: stopping on high network and cpu load (Watchdog timeout) Message-ID: <20150422065833.GA66880@bali> References: <20150413101626.GA47411@bali> <552BBF48.4090808@sentex.net> <20150414055445.GA54779@bali> <552D1DAC.9040104@sentex.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <552D1DAC.9040104@sentex.net> X-Echelon: X-Advice: Drop that crappy M$-Outlook, I'm tired of your viruses! User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Apr 2015 06:58:42 -0000 On Tue, 14-Apr-2015 at 10:01:16 -0400, Mike Tancsa wrote: > On 4/14/2015 1:54 AM, Andre Albsmeier wrote: > > > > Is this an em specific issue or should one avoid TSO generally > > at the moment? That is, should I disable it on machines with > > msk (and maybe other) interfaces as well? > > em specific I think. This thread has some info on what might be going on > > https://lists.freebsd.org/pipermail/freebsd-stable/2014-September/080081.html For the records: I can definitely say that the problem did not appear again since I disabled TSO on the em adapters. I've left it enabled on the msk adapters, so this is indeed an em-only problem (at least here). TSO should be disabled in the em driver until fixed. Thanks again for the hint. -Andre