From owner-freebsd-stable@freebsd.org Mon Apr 22 13:53:14 2019 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 136CE159A9D5 for ; Mon, 22 Apr 2019 13:53:14 +0000 (UTC) (envelope-from tyler@monkeypox.org) Received: from starfish.geekisp.com (starfish.geekisp.com [216.168.135.166]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (Client CN "mail.geekisp.com", Issuer "mail.geekisp.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DAAED8BC6C for ; Mon, 22 Apr 2019 13:53:12 +0000 (UTC) (envelope-from tyler@monkeypox.org) Received: (qmail 18572 invoked by uid 1003); 22 Apr 2019 13:46:30 -0000 Received: from unknown (HELO grape) (tyler@monkeypox.org@166.255.55.130) by mail.geekisp.com with (ECDHE-RSA-AES256-GCM-SHA384 encrypted) SMTP; 22 Apr 2019 13:46:29 -0000 Date: Mon, 22 Apr 2019 06:44:33 -0700 From: "R. Tyler Croy" To: freebsd-stable@freebsd.org Subject: em(4) cannot maintain link in 12.0-STABLE Message-ID: <20190422134433.otstsln56jmyfz3a@grape> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: NeoMutt/20180716 X-Rspamd-Queue-Id: DAAED8BC6C X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [3.70 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.73)[0.731,0]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[monkeypox.org]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[3]; RCVD_TLS_LAST(0.00)[]; MX_GOOD(-0.01)[a.mx.monkeypox.org]; NEURAL_SPAM_LONG(0.84)[0.836,0]; RCVD_IN_DNSWL_NONE(0.00)[166.135.168.216.list.dnswl.org : 127.0.10.0]; NEURAL_SPAM_MEDIUM(0.75)[0.751,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MID_RHS_NOT_FQDN(0.50)[]; ASN(0.00)[asn:11817, ipnet:216.168.135.0/24, country:US]; MIME_TRACE(0.00)[0:+]; IP_SCORE(-0.01)[country: US(-0.06)] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Apr 2019 13:53:14 -0000 I have two NICs in a machine which acts as a gateway, and with the upgrade from 11-STABLE to the latest 12.0-STABLE tree (r346473), neither em(4) based NIC will maintain a connection. The behavior is similar to what is described in the last couple comments of this ticket: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219428 The behavior is identical with both devices. Link is established, dhclient starts securing a DHCP lease, and then once traffic starts to flow, the link switches to DOWN. Then back to UP, and back and forth. A syslog snippet: Apr 21 20:03:42 strawberry kernel: em0: Link is up 100 Mbps Full Duplex Apr 21 20:03:42 strawberry kernel: em0: link state changed to UP Apr 21 20:03:46 strawberry dhclient[15534]: New IP Address (em0): 173.228.83.96 Apr 21 20:03:46 strawberry dhclient[16069]: New Subnet Mask (em0): 255.255.255.0 Apr 21 20:03:46 strawberry dhclient[18914]: New Broadcast Address (em0): 173.228.83.255 Apr 21 20:03:46 strawberry dhclient[21483]: New Routers (em0): 173.228.83.1 Apr 21 20:03:48 strawberry kernel: em0: link state changed to DOWN Apr 21 20:03:50 strawberry kernel: em0: Link is up 100 Mbps Full Duplex Apr 21 20:03:50 strawberry kernel: em0: link state changed to UP Apr 21 20:03:57 strawberry kernel: em0: link state changed to DOWN Apr 21 20:03:57 strawberry ntpd[75785]: error resolving pool 0.freebsd.pool.ntp.org: Name does not resolve (8) Apr 21 20:03:58 strawberry dhclient[38043]: send_packet: Network is down Apr 21 20:03:59 strawberry kernel: em0: Link is up 100 Mbps Full Duplex Apr 21 20:03:59 strawberry kernel: em0: link state changed to UP Apr 21 20:04:05 strawberry kernel: em0: link state changed to DOWN Apr 21 20:04:06 strawberry dhclient[38043]: send_packet: Network is down Apr 21 20:04:07 strawberry kernel: em0: Link is up 100 Mbps Full Duplex Apr 21 20:04:07 strawberry kernel: em0: link state changed to UP Apr 21 20:04:15 strawberry kernel: em0: link state changed to DOWN Apr 21 20:04:15 strawberry dhclient[38043]: send_packet: Network is down Apr 21 20:04:16 strawberry kernel: em0: Link is up 100 Mbps Full Duplex THe version/hardware details: FreeBSD strawberry 12.0-STABLE FreeBSD 12.0-STABLE r346473 GENERIC amd64 em0@pci0:7:0:0: class=0x020000 card=0xa01f8086 chip=0x10d38086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82574L Gigabit Network Connection' class = network subclass = ethernet em1@pci0:8:0:0: class=0x020000 card=0xa01f8086 chip=0x10d38086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82574L Gigabit Network Connection' class = network subclass = ethernet My temporary workaround has been to use a USB-based NIC, but I am wondering if there are any tunables I could tweak to get this misbehaving driver to mind its manners? Cheers -- GitHub: https://github.com/rtyler GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2