From owner-freebsd-current@freebsd.org Sat Apr 29 23:22:20 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 B2DF5D550EC for ; Sat, 29 Apr 2017 23:22:20 +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 2D357138F for ; Sat, 29 Apr 2017 23:22:19 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([92.225.1.98]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MMoU7-1dAPm030gB-008Y2A; Sun, 30 Apr 2017 01:22:03 +0200 Date: Sun, 30 Apr 2017 01:21:55 +0200 From: "O. Hartmann" To: AN Cc: FreeBSD CURRENT Subject: Re: DHCP/network issues Message-ID: <20170430012155.2f977934@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: <20170318152013.761c4999@thor.intern.walstatt.dynvpn.de> <20170318191142.083f279d@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/Hdr.KXtrv6Zp81eSSAtZEfF"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:I/iIJh2wVqNn3+iMKicLyImqF9YQoFbSgG880G387n/85AnQXZB 70ZNj2eqKxLbc8lIbmWkIDcz2jQyb4R1VgE+/lULjj41Zr2jPhHeGASNIZ3vB0MJL/x6+Kb nh5VH1Bd+n7CzDemrheVYyV9ejGojjZE36Zcg3Ikcxgc8oi/QstcYZndMmbzXrXuhLzk8VU MreoO+VdG/3dtlyNnefTg== X-UI-Out-Filterresults: notjunk:1;V01:K0:de1Vi/leUsM=:FOoEtB+LxCDHfGlE+TDRiH q4oX07rteDhgjoqD87H/yqMZomto1tpPUp8gBtAUUYIWV7lpeW6HokSiASNV+pmJUB6L775rh YgSbZV2hd/QyQoZT9YwegXia8hvFLPnRovKr3yWU2Wuf8ARwoGvIxLpFZACe7xspEGsycL5CI 9atE5xpmw0wSABxo443zG2wDKczw2DyPv9ULlJlTkq9ZaN7F4m4skE6TxKGtPCB1uX47IDBrT d/vHIdIKtX2Gh2qdnm+jSl0UiANNfK+ol40NwzvaQBb3hb/9Ch4BuS5WFsuGQbZfbh1/auurO yWc5hwv/zhzd1TcUTEYtBaRLVRwF8GS3iPfYe48XMCDWdQx9ME3azL/0tq7Q0/n5sbYJnKYFO E8untmp/2E/31OXDuPVYYphQhpmYr99z04dWC/q4caPBktC68HD88Y+uob8etXouYItRLFm5P OUUCVmsYvUph3m5y61gRlbvWKnSIiTEGZgcBVBlikTdCIvPjTwZza2tFfajrKmrQyzRFvrbjH qVd+BBuNuaMjR9hD669ulbLRTizdF1gNQjiIYjRnx/DEaBpfsz5AbzWnYeTPpKWbv5u5N/GhK L4LCXMSx4B8OvNH54j1T5kdzwNCOirRBNmOAcIjASaoV2HocSZantpF4PvNSUdFpWjMROmi14 mpGLHDkwFxbQvmXOGalkwJRwkIHzskxdTtvfPRomdaMNsXLG/TqNvWBaBPUuhfAefWeZkzUj6 1s2Hyh6egSChOzN56bsgvEEbkMvg/ot5X7FM3ip/eGLSm293/vVjiihYp2k= 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: Sat, 29 Apr 2017 23:22:20 -0000 --Sig_/Hdr.KXtrv6Zp81eSSAtZEfF Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Sat, 29 Apr 2017 19:07:06 -0400 (EDT) AN schrieb: > Hi OH: >=20 > On Sat, 18 Mar 2017, O. Hartmann wrote: >=20 > > Date: Sat, 18 Mar 2017 19:11:42 +0100 > > From: O. Hartmann > > To: AN > > Cc: O. Hartmann > > Subject: Re: DHCP/network issues > >=20 > > Am Sat, 18 Mar 2017 10:25:58 -0400 (EDT) > > AN schrieb: > > =20 > >> Hi: > >> > >> On Sat, 18 Mar 2017, O. Hartmann wrote: > >> =20 > >>> Date: Sat, 18 Mar 2017 15:20:13 +0100 > >>> From: O. Hartmann > >>> To: AN > >>> Cc: freebsd-current@freebsd.org > >>> Subject: Re: DHCP/network issues > >>> > >>> Am Sat, 18 Mar 2017 09:45:31 -0400 (EDT) > >>> AN schrieb: > >>> =20 > >>>> Is anyone seeing network or DHCP issues with a recent update to > >>>> 12-current? > >>>> > >>>> On new hardware > >>>> Dual Core Celeron J1800 Bay Trail 2.4GHz, 2MB L2 Cache > >>>> 2 Gigabit Ethernet Intel NIC ports > >>>> > >>>> I'm seeing the following issues: > >>>> > >>>> - install latest 12-current snapshot > >>>> FreeBSD-12.0-CURRENT-amd64-20170316-r315413-memstick.img, try DHCP d= uring > >>>> install and it fails. Setup networking manually and try to ping def= ault gateway > >>>> results in the response > >>>> ping: sendto: Host is down =20 > >>> > >>> Yes. Since IFLIB has been introduced, Intel NICs seem to be suffering= from not > >>> working properly anymore. i217-LM, i350 and sibblings are affected fo= r which I can > >>> speak because we suffer the same problems here. Even if the NIC works= , it dies > >>> after some time under heavy I/O. > >>> =20 > >> > >> Thank you for the reply, I remember seeing your messages on the list a= bout > >> this now. Is anyone trying to fix it, did you file a PR? =20 > > > > I think, as you may already have read, some of the developers are aware= of this > > problem. I haven't file a PR so far. > > > > Kind regards, > > > > oh > > > > =20 >=20 >=20 > Do you know if the problem with Intel Nic in 12-current has been fixed? >=20 > Thanks, >=20 > AN Hello. The problem still persists!! I have a Fujitsu Celsius M740, which uses a i2= 17 NIC. This NIC freezes up while under heavy I/O. In most cases, I can get it back online by bringing it first down and then = up again with ifconfig em0 down/up. But sometimes I have to reboot. I get some strange er= rors on the console about "RX/TX no buffer left" - I'm sorry to be not more specific, I= 'm not in the lab at the moment where I have a more specific record of that problem. The = i217 NIC suffers from this problem after IFLIB has been introduced and I can trigger= the problem easily whily rsyncing poudriere repository packages with the NFSv4 connecte= d package server. I haven't checked on igb NICs (we also use i350 based dual-port NICs as I d= o with some private servers). But last time I pushed them very hard with I/O, I was abl= e to freeze them the same way. I do not know whether someone is working on this, I recall having filed a P= R on this, but I was very unspecific, because I do not have further details and running CU= RRENT with no DEBUG features. As of your question: it hasn't been fixed so far. Kind regards, Oliver --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/Hdr.KXtrv6Zp81eSSAtZEfF Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWQUgEwAKCRDS528fyFhY lA//AgCQMkT7JtDfgglhBLMUuLQR2sGvZFsnZzbodLK8KBC4wkdMgd9HXTym3yzZ UvlfbSpu3ovwVy3QX082De/+lNJRAfsEMmjqulck9YPwH72YOMcyMU3i+7iQZXPH LNN4s+kBMfYkm6P4ufY2RiORV+0Q7+Y0wbwZ4y93vBkvyDUt+ss1 =P+Ax -----END PGP SIGNATURE----- --Sig_/Hdr.KXtrv6Zp81eSSAtZEfF--