From owner-freebsd-questions@freebsd.org Mon Oct 7 03:55:59 2019 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8BA0713CCED for ; Mon, 7 Oct 2019 03:55:59 +0000 (UTC) (envelope-from SRS0=FuLd=YA=mail.sermon-archive.info=doug@sermon-archive.info) Received: from mail.sermon-archive.info (sermon-archive.info [71.177.216.148]) by mx1.freebsd.org (Postfix) with ESMTP id 46mmqL5s9Fz4CGg for ; Mon, 7 Oct 2019 03:55:58 +0000 (UTC) (envelope-from SRS0=FuLd=YA=mail.sermon-archive.info=doug@sermon-archive.info) Received: from [10.0.1.251] (mini [10.0.1.251]) by mail.sermon-archive.info (Postfix) with ESMTPSA id 46mmqK05Rpz2fjW0; Sun, 6 Oct 2019 20:55:56 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: Intermittent connectivity loss with em(4) From: Doug Hardie In-Reply-To: <43f0decc-d459-4ded-dc46-c249bc8e24c9@pp.dyndns.biz> Date: Sun, 6 Oct 2019 20:55:56 -0700 Cc: freebsd-questions@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <094A1786-98A8-4CEF-A036-5809D9705EC8@mail.sermon-archive.info> References: <94B563F6-55C4-46BC-BD79-5CC2AD86E6C1@mail.sermon-archive.info> <43f0decc-d459-4ded-dc46-c249bc8e24c9@pp.dyndns.biz> To: =?utf-8?Q?Morgan_Wesstr=C3=B6m?= X-Mailer: Apple Mail (2.3445.104.11) X-Virus-Scanned: clamav-milter 0.101.2 at mail X-Virus-Status: Clean X-Rspamd-Queue-Id: 46mmqL5s9Fz4CGg X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of SRS0=FuLd=YA=mail.sermon-archive.info=doug@sermon-archive.info designates 71.177.216.148 as permitted sender) smtp.mailfrom=SRS0=FuLd=YA=mail.sermon-archive.info=doug@sermon-archive.info X-Spamd-Result: default: False [-1.51 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-0.96)[-0.960,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:71.177.216.148:c]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(-0.16)[asn: 5650(-0.76), country: US(-0.05)]; NEURAL_HAM_LONG(-0.98)[-0.985,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[148.216.177.71.list.dnswl.org : 127.0.10.0]; FORGED_SENDER(0.30)[bc979@lafn.org,SRS0=FuLd=YA=mail.sermon-archive.info=doug@sermon-archive.info]; RCVD_NO_TLS_LAST(0.10)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:5650, ipnet:71.177.216.0/23, country:US]; FROM_NEQ_ENVFROM(0.00)[bc979@lafn.org,SRS0=FuLd=YA=mail.sermon-archive.info=doug@sermon-archive.info]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2019 03:55:59 -0000 Forgot to include, I use a lot of bge devices and some rl. However, I = just discovered one of the remote client's computers has 2 em nics. I = am running the ping test now on it. I did find the following in = messages: zgrep em /var/log/messages* /var/log/messages.6.gz:Sep 29 15:22:33 brain kernel: em0: link state = changed to DOWN /var/log/messages.6.gz:Sep 29 17:08:14 brain kernel: em0: link state = changed to UP /var/log/messages.6.gz:Sep 29 17:09:46 brain kernel: em0: link state = changed to DOWN /var/log/messages.6.gz:Sep 29 17:09:49 brain kernel: em0: link state = changed to UP The first outage was a complete outage to that site. I don't know what = caused it or how it got resolved. I never noticed the second one. The client has not been really thrilled with this machine. He had a = much better one, but it was too noisy and replaced it. Yet another idea: get mtr "my trace route". package mtr-nox11 and use = it to go to google. It is traceroute and ping combined. You can use -i = 60 with it also. -- Doug > On 6 October 2019, at 14:10, Morgan Wesstr=C3=B6m = wrote: >=20 >> I have had issues with em nics in the past and don't use them = anymore. However, none of the issues were as blatant as you are seeing. = The dmsg log is only written to during boot. Messages during operation = are written to /var/log/messages. Check there to see if there is = anything that correlates with the outages. >=20 > Yes, I did check /var/log/messages too but there's nothing written = there during the outages unfortunately. >=20 > /Morgan > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to = "freebsd-questions-unsubscribe@freebsd.org"