Date: Thu, 07 Jul 2016 08:19:41 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 210488] ue0 axge AX88179 Ierrs errors under havy network load Message-ID: <bug-210488-2472-Bx4rIr16on@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-210488-2472@https.bugs.freebsd.org/bugzilla/> References: <bug-210488-2472@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210488 --- Comment #8 from Pyun YongHyeon <yongari@FreeBSD.org> --- (In reply to mtatarin76 from comment #7) Probably you can put flow control options to '/etc/start_if.ue0' file as a workaround(Not tested though). Enabling flow-control by default in driver would be a POLA violation so I wanted to mitigate the issue when flow-control is not active. However, it seems there is no good way to mitigate the issue without increasing H/W RX FIFO size. The hardware have a fixed sized buffer so we may have to rely on other way like flow-control to mitigate that. The issue shall frequently happen when the controller operates at high-speed(USB 2.0) and established link is 1000baseT(i.e. the network bottleneck is USB 2.0 bus). I contacted the vendor to get more information on the issue so let's see how it goes. If the vendor confirms my theory, documenting it in axge(4) would be best one. I guess you may see better result when you plug the controller to USB 3.0 port. Due to lack of H/W, I wasn't able to test that. Thanks for testing! --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-210488-2472-Bx4rIr16on>