Date: Wed, 10 Aug 2022 14:01:01 -0400 From: mike tancsa <mike@sentex.net> To: "Pieper, Jeffrey E" <jeffrey.e.pieper@intel.com>, Jim King <jim@jimking.net>, "stable@freebsd.org" <stable@freebsd.org>, "kbowling@FreeBSD.org" <kbowling@FreeBSD.org> Subject: Re: igc problems with heavy traffic Message-ID: <3e69a2e6-9f74-5c77-5b97-a9d2590bb2b2@sentex.net> In-Reply-To: <MW4PR11MB5890493674ADD1757BB47075D0659@MW4PR11MB5890.namprd11.prod.outlook.com> References: <fc256428-3ff1-68ba-cfcc-a00ca427e85b@jimking.net> <59b9cec0-d8c2-ce72-b5e9-99d1a1e807f8@sentex.net> <e714cd76-0aaa-3ea0-3c31-5e61badffa18@sentex.net> <86995d10-af63-d053-972e-dd233029f3bf@jimking.net> <3d874f65-8ce2-8f06-f19a-14cd550166e3@sentex.net> <a8192d60-2970-edb5-ce1a-c17ea875bf07@jimking.net> <fd1e825b-c306-64b1-f9ef-fec0344a9c95@sentex.net> <a4ddc96a-3dd5-4fee-8003-05f228d10858@jimking.net> <MW4PR11MB5890493674ADD1757BB47075D0659@MW4PR11MB5890.namprd11.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/10/2022 1:47 PM, Pieper, Jeffrey E wrote: > You could try disabling EEE (Energy Efficient Ethernet). Something > like: sysctl dev.igc.0.eee_control=0. Thanks, I just tired, and it locks up the NIC. # sysctl dev.igc.2.eee_control=0 dev.igc.2.eee_control: 1 -> 0 # And up /down sort of brings it back # ping 192.168.20.2 PING 192.168.20.2 (192.168.20.2): 56 data bytes 64 bytes from 192.168.20.2: icmp_seq=0 ttl=64 time=0.169 ms 64 bytes from 192.168.20.2: icmp_seq=10 ttl=64 time=0.121 ms 64 bytes from 192.168.20.2: icmp_seq=12 ttl=64 time=0.113 ms 64 bytes from 192.168.20.2: icmp_seq=19 ttl=64 time=0.144 ms 64 bytes from 192.168.20.2: icmp_seq=22 ttl=64 time=0.143 ms 64 bytes from 192.168.20.2: icmp_seq=23 ttl=64 time=0.115 ms 64 bytes from 192.168.20.2: icmp_seq=24 ttl=64 time=0.135 ms ---Mike > Jeff >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3e69a2e6-9f74-5c77-5b97-a9d2590bb2b2>