From owner-freebsd-current@freebsd.org Mon Aug 6 19:03:22 2018 Return-Path: Delivered-To: freebsd-current@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 229441062282 for ; Mon, 6 Aug 2018 19:03:22 +0000 (UTC) (envelope-from tyler@monkeypox.org) Received: from starfish.geekisp.com (starfish.geekisp.com [216.168.135.166]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail.geekisp.com", Issuer "mail.geekisp.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C33D584C34 for ; Mon, 6 Aug 2018 19:03:21 +0000 (UTC) (envelope-from tyler@monkeypox.org) Received: (qmail 4258 invoked by uid 1003); 6 Aug 2018 18:56:39 -0000 Received: from unknown (HELO grape.lasagna.io) (tyler@monkeypox.org@142.254.21.68) by mail.geekisp.com with (AES256-SHA encrypted) SMTP; 6 Aug 2018 18:56:39 -0000 Date: Mon, 6 Aug 2018 11:48:47 -0700 From: "R. Tyler Croy" To: Michael Butler Cc: tech-lists , freebsd-current@freebsd.org Subject: Re: em0 link fail Message-ID: <20180806184847.GA17800@grape.lasagna.io> References: <739ef71a-f29f-68ea-955a-fb53c57960a6@protected-networks.net> <8e2bf594-6d7e-477e-836b-4cc4483cb525@protected-networks.net> <64e462dd-16fc-b57f-7bf2-02068d0e24c8@zyxst.net> <7a4607ce-e212-5cba-bc04-1d0abf1a7824@protected-networks.net> <20180726044705.GB5081@grape.lasagna.io> <20180801042034.GD3303@grape.lasagna.io> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HlL+5n6rz5pIUxbD" Content-Disposition: inline In-Reply-To: <20180801042034.GD3303@grape.lasagna.io> User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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: Mon, 06 Aug 2018 19:03:22 -0000 --HlL+5n6rz5pIUxbD Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable (replies inline) On Tue, 31 Jul 2018, R. Tyler Croy wrote: > On Wed, 25 Jul 2018, R. Tyler Croy wrote: >=20 > > On Sun, 15 Jul 2018, Michael Butler wrote: > >=20 > > > On 07/05/18 09:54, I wrote: > > > > On 07/05/18 09:27, tech-lists wrote: > > > >> On 03/07/2018 19:47, Michael Butler wrote: > > > >>> That would've been .. > > > >>> > > > >>> Jun=A0 1 09:56:15 toshi kernel: FreeBSD 12.0-CURRENT #35 r334484:= Fri Jun > > > >>> 1 08:25:58 EDT 2018 > > > >>> > > > >>> I'm going to build one with SVN r334862 reverted to see if that w= orks, > > > >> > > > >> Is it working now? Am asking because a system I'd like to take from > > > >> 11-stable to 12 uses the em driver. > > > >=20 > > > > No :-( I haven't had the chance yet to revisit it, > > >=20 > > > As it turns out, SVN r336313 (committed today) solves the issue I was > > > having with the hardware stalling, > >=20 > > I'll give r336313 a try as soon as possible and corroborate the fixes! >=20 > After a couple days with this new build, it looks like i can corroborate = the > fix referenced by Michael. :D Regrettably I spoke too soon. I've had two failures thus far today unfortunately :( It appears to be correlated either with my link state changing rapidly due = to upstream fluctuations from my ISP, or a new DHCP lease being offered. Some relevant snippets from syslog around the time of the link loss: Aug 1 16:17:10 strawberry kernel: em1: link state changed to DOWN Aug 1 16:17:20 strawberry kernel: em1: link state changed to UP Aug 1 16:17:26 strawberry kernel: em1: link state changed to DOWN Aug 1 16:17:28 strawberry kernel: em1: link state changed to UP Aug 1 16:17:32 strawberry kernel: em1: link state changed to DOWN Aug 1 16:17:34 strawberry kernel: em1: link state changed to UP Aug 1 16:17:41 strawberry kernel: em1: link state changed to DOWN Aug 1 16:17:43 strawberry kernel: em1: link state changed to UP Aug 1 16:18:04 strawberry dhclient: New IP Address (em1): 173.228.82.91 Aug 1 16:18:04 strawberry dhclient: New Subnet Mask (em1): 255.255.255= =2E0 Aug 1 16:18:04 strawberry dhclient: New Broadcast Address (em1): 173.228.82.255 Aug 1 16:18:04 strawberry dhclient: New Routers (em1): 173.228.82.1 Aug 5 22:32:32 strawberry syslogd: last message repeated 1 times Aug 5 23:44:53 strawberry kernel: em1: Watchdog timeout Queue[0]-- res= etting Aug 5 23:44:53 strawberry kernel: Interface is RUNNING and ACTIVE Aug 5 23:44:53 strawberry kernel: em1: TX Queue 0 ------ Aug 5 23:44:53 strawberry kernel: em1: hw tdh =3D 282, hw tdt =3D 176 Aug 5 23:44:53 strawberry kernel: em1: Tx Queue Status =3D -2147483648 Aug 5 23:44:53 strawberry kernel: em1: TX descriptors avail =3D 106 Aug 5 23:44:53 strawberry kernel: em1: Tx Descriptors avail failure = =3D 0 Aug 5 23:44:53 strawberry kernel: em1: RX Queue 0 ------ Aug 5 23:44:53 strawberry kernel: em1: hw rdh =3D 176, hw rdt =3D 174 Aug 5 23:44:53 strawberry kernel: em1: RX discarded packets =3D 0 Aug 5 23:44:53 strawberry kernel: em1: RX Next to Check =3D 175 Aug 5 23:44:53 strawberry kernel: em1: RX Next to Refresh =3D 174 Aug 5 23:44:53 strawberry kernel: em1: link state changed to DOWN Aug 5 23:44:55 strawberry kernel: em1: link state changed to UP Aug 5 23:46:18 strawberry dhclient: New IP Address (em1): 173.228.82.91 Aug 5 23:46:18 strawberry dhclient: New Subnet Mask (em1): 255.255.255= =2E0 Aug 5 23:46:18 strawberry dhclient: New Broadcast Address (em1): 173.228.82.255 Aug 5 23:46:18 strawberry dhclient: New Routers (em1): 173.228.82.1 Aug 5 23:46:19 strawberry syslogd: last message repeated 1 times Aug 5 23:49:35 strawberry dhclient[12645]: send_packet: No route to ho= st At the tail end of the syslog I was trying to get a new lease but was then unable to get a lease or restore functionality to the em1 device. This is rather perplexing to me, but I'm not savvy enough to figure out how= to further be a useful debugger here :-/ Any suggestions would be appreciated! Cheers -R Tyler Croy --HlL+5n6rz5pIUxbD Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQSQYoZaRujHSSvxiNcUJsfcP1HhbwUCW2iYDwAKCRAUJsfcP1Hh b8aHAKCJQpwMpuC0QZpjRc6a9gfuWNTrTwCeO4zZLbFDmU4o2nbksOh2Qot8Ouw= =NsHA -----END PGP SIGNATURE----- --HlL+5n6rz5pIUxbD--