![killer e2200 gigabit ethernet controller poor upload killer e2200 gigabit ethernet controller poor upload](https://www.drivermax.com/download/Qualcomm-Atheros-Killer-e2200-Gigabit-Ethernet-Controller-NDIS-6_30_using_drivermax_809578.jpg)
![killer e2200 gigabit ethernet controller poor upload killer e2200 gigabit ethernet controller poor upload](https://helpdeskgeek.com/wp-content/pictures/2018/09/FEATURED-IMAGE.jpg)
I am experiencing an intermittent bug with the alc(4) driver with the Killer E2200 Gigabit Ethernet NIC on FreeBSD-12.3-RELEASE-p5 for amd64 that may be related. Specific patch to be made, unless someone that knows reports If yes-and-yes, then I'd first need to somehow identify the Is the patch expected to be NUMA-specific as far as fixing things?Īre you asking that I try the patch when the ACPI information isĬonfigured for NUMA (called "local" mode in that Ryzen Master)? (Knowing the later might help identify the former I've no clue what the modification was nor where the two new lines Pair of lines was to be put somewhere ("with modified if condition"). The way I read the forum message, the shown lines of code wereĪlready in /usr/src/sys/dev/alc/if_alc.c and a somewhat different Rebuilt and reinstalled, I'd just be testing if it stopped the I am no longer actively experimenting with NUMA mode for other It is working without the patch when the threadripper 1950X ACPI isĬonfigured as non-NUMA (via what the old Ryzen Master version calls (In reply to Kubilay Kocak from comment #7) I have not tried making any code changes. My experiments with things like "tcpdump -npi alc0" did not show packets I recently jumped from head -r352341 to -r355027 and This was not limited to any specific versions of FreeBSD but has been Interface when native-booted from their drives, I've historically eitherīooted the FreeBSD drive under HyperV so Windows would deal with theĮtherNet or used the poorly working WiFi for native FreeBSD. (1903 now but for a long time) have had no problems using this EtherNet While Fedora (such as 31 now but for a long time) and Windows 10 Pro 圆4 (Note the numa domain use, in case numa matters for some reason.) A ThreadRipper 1950X X399 AORUS gaming 7 I use has an E2500:Īlc0: port 0x1000-0x107f mem 0xba000000-0xba03ffff irq 27 at device 0.0 numa-domain 0 on pci5Īlc0: 4GB boundary crossed, switching to 32bit DMA addressing mode.Ītphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow