From owner-freebsd-current@freebsd.org Fri Mar 17 11:20:33 2017 Return-Path: Delivered-To: freebsd-current@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 A4289D0BDC1 for ; Fri, 17 Mar 2017 11:20:33 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 07FEA1CF5 for ; Fri, 17 Mar 2017 11:20:32 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MGzwE-1d1XEQ2sMM-00DpWX for ; Fri, 17 Mar 2017 12:20:24 +0100 Date: Fri, 17 Mar 2017 12:20:18 +0100 From: "O. Hartmann" To: freebsd-current Subject: CURRENT: massive em0 NIC problems since IFLIB changes/introduction Message-ID: <20170317122018.21384497@freyja.zeit4.iv.bundesimmobilien.de> Organization: Walstatt X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.29; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:0VcdCTTUvf9XNbv6KUwVXSVvQchrOgpvIo9SNzCcKQeXcP2qyE3 2VulHmayGPThvPfFnsFVW28XXVjQjfyZo+Wq8nk8ioYwvho1N3TKpgQfQNpqzVZXhJvZi1b 9867DM4V0UQyji6xygNMg+1elxNXTi3Uxoyg//YeSNOeOdAkG7Ge9YKY/Vb1/0DhkPLFuIL s374hb0DLVBJUV9EbGHaA== X-UI-Out-Filterresults: notjunk:1;V01:K0:dpcjIX3bE2g=:zIN6+QA281pPHKw+HrlSs3 FjtbCzCxij2v7srMo6PrD8uxtAeBUkvgXMHo8NyMxliKjQNZmfnFZiylPkn8WEiOhGRGUeU75 Pl5aa/tgG72Kb/JaHSck+i6c3wnNRrqdYA4HAN4F6U4vLITgQEB3pIq/MiljMkKJ4VdsGoNxW 3LEt6L++URWfVCeluSZK8/21GqMkLMnioSUAL7MyX1yMZ29ii7QiWsNfWbWi9MYtM8Dn12VUX btsH7uLMuhFVMhGOtgMIAJFn96wdStqMsegvzU1uawiRV+/wzgHlRIyiW2EgDpQ8UG4Lj2wpT qL4s09w2GdzqbcSHNWMHo+KULIQSxqBBtJUxCLt5WlVm/c6lFg22OuoRDisxSwsfX4Sy0G6qL PFd2vyZpomzaixA4CyFlm/W9TV+fNRsDeXeAk7oD+vvcDgQDvrFWNg50fcnTvPnuU3NHnt5j2 9uteR7qYq0v4FOI49isQzJtI/aQgDEYZHPsDyxnSsgVMPMdtPLNWpUi3IfMuo2X5SVx3xalJ5 HOJQX4RAM9rC1+f7Tm9QGSus92zdx8nhfCKWLT+BXoVmC03YxJe13BNdCvR+Sr8JV2sSnTPeY +24FeabfmXUtJqyHwvLzq8HV1goHR5tEhoW+4edgIcSkkaTPyNnPA8kHhH2LSQuQcDb2Z2M+L /y/oVOBhpMXC393tCzXQv5R38lmCWEwL5F0vj7CP3RggbKBlW02tEz7Mq2roc5rgaB6G9poN/ /U/kt8ZI3md+j2JGRNBTUuJcKkFMFL+kMycItf7dp8zrkutgsCneChaitOuQv3W2J7qa7DWjy RNKEaJL X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2017 11:20:33 -0000 Since the introduction of the IFLIB changes, I realise severe problems on CURRENT. Running the most recent CURRENT (FreeBSD 12.0-CURRENT #27 r315442: Fri Mar 17 10:46:04 CET 2017 amd64), the problems on a workstation got severe within the past two days: since a couple of weeks the em0 NIC (Intel i217-LM, see below) dies on heavy I/O. I realised this first when "rsync"ing poudriere repositories to a remote NFSv4 (automounted) folder. The em0 device could be revived by ifconfig down/up procedure. But not the i217-LM chip is affected. On another box equipted with a i350 dual port GBit NIC I observed a similar behaviour under (artificially) high I/O load (but I didn't investigate that further since it occured very seldom). Now, since around yesterday, the i217-LM dies without being reviveable with ifconfig down/up: Doing so, my FreeBSD CURRENT machine (Fujitsu Celsius M740) remains with a dead em0 device, reporting "no route" in some occasions but stuck in the dead state. Every attempt to establish manually the route again fails, only rebooting the box gives some relief. On the console, I have some very strange reports: - ping reports suddenly about no buffer space - or I see sometimes massive occurences of "em0: TX(0) desc avail = 1024, pidx = 0" on the console Either way, sending/receiving large files on an established network GBit line which could be saturated by approx 100 MBytes/s tend to make the NIC fail. Since yesterday, it is quite impossible to tranfer larger files in a burst, the NIC dies rapidly and can not be revived anymore except via reboot. Kind regards, O. Hartmann