Date: Sat, 13 Jul 2019 13:28:24 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: bugzilla-noreply@freebsd.org Cc: FreeBSD Net <net@freebsd.org> Subject: Re: [Bug 219428] em network driver broken in current Message-ID: <CAN6yY1sihpCy2scxY%2BGsBNvnjKaNzwns2d=RbcmCB461YJku2g@mail.gmail.com> In-Reply-To: <bug-219428-7501-BMQSmg38yk@https.bugs.freebsd.org/bugzilla/> References: <bug-219428-7501@https.bugs.freebsd.org/bugzilla/> <bug-219428-7501-BMQSmg38yk@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jul 13, 2019 at 12:54 PM <bugzilla-noreply@freebsd.org> wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219428 > > --- Comment #23 from IPTRACE <arkadiusz.majewski@iptrace.pl> --- > Is there any workaround instead of restart a system? > I was trying below without progress as well. > > # ifconfig igb0 down > # ifconfig igb0 up > > I think the problem is when the network card loses ethernet link and then > errors occurs with non-working interface. > No idea whether it will do the trick, but you might try "service netif restart ibg0". It does a lot more than just down-up of the interface. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1sihpCy2scxY%2BGsBNvnjKaNzwns2d=RbcmCB461YJku2g>