Date: Sun, 6 Oct 2019 20:44:34 -0700 From: Doug Hardie <bc979@lafn.org> To: =?utf-8?Q?Morgan_Wesstr=C3=B6m?= <freebsd-database@pp.dyndns.biz> Cc: freebsd-questions@freebsd.org Subject: Re: Intermittent connectivity loss with em(4) Message-ID: <04E8EDA2-FA9D-439E-B055-6D1A9B9947C5@mail.sermon-archive.info> In-Reply-To: <43f0decc-d459-4ded-dc46-c249bc8e24c9@pp.dyndns.biz> References: <ba24db9b-6a34-76d4-7c95-4c2e64d0a5a0@pp.dyndns.biz> <94B563F6-55C4-46BC-BD79-5CC2AD86E6C1@mail.sermon-archive.info> <43f0decc-d459-4ded-dc46-c249bc8e24c9@pp.dyndns.biz>
next in thread | previous in thread | raw e-mail | index | archive | help
I am a bit surprised about that. I used to see a number of messages when there were issues. Most of them were the em connection down/up. The only remaining things I can think of are to reboot the machine and run the ping till you get some failures. Then run "netstat -s". Look for non-zero numbers. That may provide a clue. If that fails run tcpdump on the inteface while pinging and see if the packets are actually going out and if anything is received in return. You might also ping the first router on the way out and see if that is also dropping packets. -- Doug > On 6 October 2019, at 14:10, Morgan Wesström <freebsd-database@pp.dyndns.biz> wrote: > >> 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. > > Yes, I did check /var/log/messages too but there's nothing written there during the outages unfortunately. > > /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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?04E8EDA2-FA9D-439E-B055-6D1A9B9947C5>