From owner-freebsd-net@FreeBSD.ORG Mon Apr 13 10:17:58 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 CE7A33D4 for ; Mon, 13 Apr 2015 10:17:58 +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 66C778E for ; Mon, 13 Apr 2015 10:17:57 +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 t3DAGRUr008376 for ; Mon, 13 Apr 2015 12:16:27 +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 t3DAGRqV030849 for ; Mon, 13 Apr 2015 12:16:27 +0200 Received: (from user@localhost) by curry.mchp.siemens.de (8.14.9/8.14.9) id t3DAGQj4048607; Date: Mon, 13 Apr 2015 12:16:26 +0200 From: Andre Albsmeier To: freebsd-net@freebsd.org Subject: Intel em (82574L and 82573L) problems: stopping on high network and cpu load (Watchdog timeout) Message-ID: <20150413101626.GA47411@bali> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Apr 2015 10:17:58 -0000 Hi, em0 = '82574L Gigabit Network Connection': em0: port 0xd000-0xd01f mem 0xf0500000-0xf051ffff,0xf052 0000-0xf0523fff irq 17 at device 0.0 on pci5 em0: Using MSIX interrupts with 3 vectors OS = 9.3-STABLE #2: Wed Apr 1 07:20:47 CEST 2015 Sometimes em0 freezes and comes back about 1 minute later. We see the infamous "Watchdog timeout -- resetting" message: em0: Watchdog timeout -- resetting em0: Queue(0) tdh = 284, hw tdt = 239 em0: TX(0) desc avail = 31,Next TX to Clean = 270 em0: link state changed to DOWN em0: link state changed to UP 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 CPU: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz (3492.14-MHz 686-class CPU) running 2 avidemux encoding processes (each with 8 threads) all the time. With just 1 avidemux task I didn't see it happen so far. It does not matter if the heavy network traffic is inbound or outbound. BTW, this happens on two identical machines but on two completely different networks. It also happens on a machine using a 82573L card. It never occured on a Marvell based machine (msk driver) running similar tasks... Any ideas?