From owner-freebsd-questions@freebsd.org Fri Oct 11 08:20:30 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 EC18F1425C0 for ; Fri, 11 Oct 2019 08:20:30 +0000 (UTC) (envelope-from freebsd-database@pp.dyndns.biz) Received: from keymaster.local (ns1.xn--wesstrm-f1a.se [IPv6:2a00:d880:5:1b9::8526]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "keymaster.pp.dyndns.biz", Issuer "keymaster.pp.dyndns.biz" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 46qLVj3hDDz49Bj for ; Fri, 11 Oct 2019 08:20:28 +0000 (UTC) (envelope-from freebsd-database@pp.dyndns.biz) Received: from [192.168.69.69] ([192.168.69.69]) by keymaster.local (8.15.2/8.15.2) with ESMTP id x9B8KJlu075481 for ; Fri, 11 Oct 2019 10:20:20 +0200 (CEST) (envelope-from freebsd-database@pp.dyndns.biz) Subject: Re: Intermittent connectivity loss with em(4) References: To: FreeBSD Questions From: =?UTF-8?Q?Morgan_Wesstr=c3=b6m?= Message-ID: Date: Fri, 11 Oct 2019 10:20:19 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 46qLVj3hDDz49Bj X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd-database@pp.dyndns.biz has no SPF policy when checking 2a00:d880:5:1b9::8526) smtp.mailfrom=freebsd-database@pp.dyndns.biz X-Spamd-Result: default: False [2.12 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.54)[-0.545,0]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; HFILTER_HELO_IP_A(1.00)[keymaster.local]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_LAST(0.00)[]; TO_DN_ALL(0.00)[]; NEURAL_SPAM_LONG(0.54)[0.541,0]; HFILTER_HELO_NORES_A_OR_MX(0.30)[keymaster.local]; R_SPF_NA(0.00)[]; DMARC_NA(0.00)[pp.dyndns.biz]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:198203, ipnet:2a00:d880::/32, country:NL]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-0.07)[asn: 198203(-0.38), country: NL(0.02)]; 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: Fri, 11 Oct 2019 08:20:31 -0000 > It the host with the problem has an Intel Atom mainboard then the BIOS > might be set to power off the NIC chip if there is no traffic on the > port for an extended period. The hub might be generating enough > heartbeat traffic to keep the timeout from happening while the cable > modem does not. > > We had this happen with some of our gateways built on Atom board > systems. The BIOS was factory set to use this feature as a > power-saving device on laptops. > I've scrutinized every BIOS setting as well as every jumper on the motherboard itself without finding anything power related with the exception of ACPI version. The fact that the link and activity LEDs remain on when connectivity is lost probably points to something else. I went with Sergio's suggestion and put a small switch between my two routers and the cable modem and the problem went away. 10 hours running now with no loss of connectivity on either machine. The behaviour intrigues me and I'd sure like to figure out why this happens but for now I will add SagemCom to my long list of manufacturers with buggy firmware/hardware. Unfortunately I have no freedom to chose another cable modem with my current ISP so I'll have to work around the problem for now. Thank you all for your valuable input and support. :) Regards Morgan