(replies inline) On Tue, 31 Jul 2018, R. Tyler Croy wrote: > On Wed, 25 Jul 2018, R. Tyler Croy wrote: > > > On Sun, 15 Jul 2018, Michael Butler wrote: > > > > > 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 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 works, > > > >> > > > >> Is it working now? Am asking because a system I'd like to take from > > > >> 11-stable to 12 uses the em driver. > > > > > > > > No :-( I haven't had the chance yet to revisit it, > > > > > > As it turns out, SVN r336313 (committed today) solves the issue I was > > > having with the hardware stalling, > > > > I'll give r336313 a try as soon as possible and corroborate the fixes! > > 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.0 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]-- resetting 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 = 282, hw tdt = 176 Aug 5 23:44:53 strawberry kernel: em1: Tx Queue Status = -2147483648 Aug 5 23:44:53 strawberry kernel: em1: TX descriptors avail = 106 Aug 5 23:44:53 strawberry kernel: em1: Tx Descriptors avail failure = 0 Aug 5 23:44:53 strawberry kernel: em1: RX Queue 0 ------ Aug 5 23:44:53 strawberry kernel: em1: hw rdh = 176, hw rdt = 174 Aug 5 23:44:53 strawberry kernel: em1: RX discarded packets = 0 Aug 5 23:44:53 strawberry kernel: em1: RX Next to Check = 175 Aug 5 23:44:53 strawberry kernel: em1: RX Next to Refresh = 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.0 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 host 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
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:17 UTC