Date: Fri, 6 Jul 2018 14:26:19 +0100 From: tech-lists <tech-lists@zyxst.net> To: Michael Butler <imb@protected-networks.net>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: em0 link fail Message-ID: <10e5354f-44e1-ba6f-4f50-552b2cec5680@zyxst.net> In-Reply-To: <739ef71a-f29f-68ea-955a-fb53c57960a6@protected-networks.net> References: <739ef71a-f29f-68ea-955a-fb53c57960a6@protected-networks.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/07/2018 18:47, Michael Butler wrote: > On June 1st, I was able to do my monthly laptop ZFS snap-shot/back-up > (using "zfs snapshot -r zroot@backup; zfs send -R >nfs-filesys"). Now I > can't without the em0 interface stalling :-( > > On a guess, I tried reverting SVN r335303 but that didn't help. > > em0: <Intel(R) PRO/1000 Network Connection> port 0xf080-0xf09f mem > 0xf7e00000-0xf7e1ffff,0xf7e39000-0xf7e39fff irq 20 at device 25.0 on pci0 > em0: attach_pre capping queues at 1 > em0: using 1024 tx descriptors and 1024 rx descriptors > em0: msix_init qsets capped at 1 > em0: PCIY_MSIX capability not found; or rid 0 == 0. > em0: Using an MSI interrupt > em0: allocated for 1 tx_queues > em0: allocated for 1 rx_queues > em0: Ethernet address: f0:1f:af:66:95:7e > em0: netmap queues/slots: TX 1/1024, RX 1/1024 > em0: link state changed to UP > > [ initiate "zfs send" ] > > em0: TX(0) desc avail = 41, pidx = 172 > em0: link state changed to DOWN > em0: TX(0) desc avail = 1024, pidx = 0 > em0: TX(0) desc avail = 1024, pidx = 0 > > .. ad nauseum .. > > "ifconfig em0 down; ifconfig em0 up" doesn't help. > > Any hints? Hi, I'm not seeing any problems using em0/saturating upstream using 12.0-CURRENT #0 r335979 -- J.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?10e5354f-44e1-ba6f-4f50-552b2cec5680>