Date: Fri, 05 Mar 2021 20:57:05 +0000 From: bugzilla-noreply@freebsd.org To: usb@FreeBSD.org Subject: [Bug 254036] Linksys USB3GIG fails to ping with large packets (maxfragsperpacket was increased) Message-ID: <bug-254036-19105-RbLASBScdU@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-254036-19105@https.bugs.freebsd.org/bugzilla/> References: <bug-254036-19105@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=3D254036 --- Comment #7 from Mike Belanger <mibelanger@qnx.com> --- I had captured some traces, but realized I made a mistake. And in trying to recapture I discovered something that I found confusing. My original testing was against a Linux PC with an on board NIC. It failed consistently. For capturing the traces, I used a QNX target and most pings were successfu= l. I don't believe there is a fundamental issue with the Linux PC as it will w= ork with other devices. >From FreeBSD->QNX, the large pings worked a lot of the time and a trace of a failure showed a missing fragment at the remote side. (local =3D FreeBSD). I have two other device that I have been using and one of them also seems to show problems with larger UDP packets. (axge): Vendor : 0x0b95 (ASIX Elec. Corp.) Product : 0x1790 (AX88179) However, the following device seems to work fine (axe): Vendor : 0x0b95 (ASIX Elec. Corp.) Product : 0x7720 (AX88x72A) (FYI...the original context of this issue is nfs failing) I need to systematically capture more information and will present it more clearly with traces. Btw...unless I am mistaken, the send queue appears to be large enough,=20 net.link.ifqmaxlen: 50 Regards. --=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-254036-19105-RbLASBScdU>