Date: Fri, 11 Oct 2019 10:20:19 +0200 From: =?UTF-8?Q?Morgan_Wesstr=c3=b6m?= <freebsd-database@pp.dyndns.biz> To: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Intermittent connectivity loss with em(4) Message-ID: <e2f7c15e-5e8e-3541-e6d0-0555651f82db@pp.dyndns.biz> In-Reply-To: <d88f51c1a29ca0dfba5218f844c74d9f.squirrel@webmail.harte-lyne.ca> References: <mailman.84.1570622403.89999.freebsd-questions@freebsd.org> <d88f51c1a29ca0dfba5218f844c74d9f.squirrel@webmail.harte-lyne.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e2f7c15e-5e8e-3541-e6d0-0555651f82db>