From owner-freebsd-net@FreeBSD.ORG Tue Apr 14 05:54:51 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 04EDBD74 for ; Tue, 14 Apr 2015 05:54:51 +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 9139381D for ; Tue, 14 Apr 2015 05:54:49 +0000 (UTC) Received: from mail2.siemens.de (localhost [127.0.0.1]) by goliath.siemens.de (8.14.3/8.14.3) with ESMTP id t3E5sjqO003649; Tue, 14 Apr 2015 07:54:46 +0200 Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.40.130]) by mail2.siemens.de (8.14.3/8.14.3) with ESMTP id t3E5sjCo018372; Tue, 14 Apr 2015 07:54:45 +0200 Received: (from user@localhost) by curry.mchp.siemens.de (8.14.9/8.14.9) id t3E5sjgB051965; Date: Tue, 14 Apr 2015 07:54:45 +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: <20150414055445.GA54779@bali> References: <20150413101626.GA47411@bali> <552BBF48.4090808@sentex.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <552BBF48.4090808@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: Tue, 14 Apr 2015 05:54:51 -0000 On Mon, 13-Apr-2015 at 09:06:16 -0400, Mike Tancsa wrote: > On 4/13/2015 6:16 AM, Andre Albsmeier wrote: > > I don't want to say that I can easily reproduce it but chances are > > quite good when I transfer a lot of stuff over the network _AND_ > > the CPU is heavily loaded. The CPU is a > > try disabling tso > ifconfig em0 -tso > and see if it makes a difference. Hmm, maybe it's too early but from a very first glance this might have helped. I'll see what will happen during the next days... 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? Thanks, -Andre