Bug #4494
closed
axge bug - AX88179 chipset (network interface reseting)
0%
Description
When a USB3 network adapter is needed, there isn't many options for Gigabit connection.
The most used chipset is the AX88179 that uses the axge driver.
This chipset is supported on FreeBSD 10.1-RELEASE but with a bug and it was apparently corrected on 10.1-STABLE (FreeBSD Bugzilla fixed: 195811 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195811)
I did some testing using pfSense 2.2 and 2.2.1 Developer build from 3/5/2015 and the bug is on in both versions.
The interface using the AX88179 resets every other hour in a softer way but I still lose network access for a few seconds.
Tested versions :
Stable:
FreeBSD gwaus.XXXXX.org 10.1-RELEASE-p4 FreeBSD 10.1-RELEASE-p4 #0 36d7dec(releng/10.1)-dirty: Thu Jan 22 15:12:35 CST 2015 root@pfsense-22-amd64-builder:/usr/obj.amd64/usr/pfSensesrc/src/sys/pfSense_SMP.10 amd64
Devel:
FreeBSD gwaus.XXXXX.org 10.1-RELEASE-p6 FreeBSD 10.1-RELEASE-p6 #0 b69ba8f(releng/10.1)-dirty: Thu Mar 5 01:07:05 CST 2015 cmb@pfs22-amd64-builder:/usr/obj.amd64/usr/pfSensesrc/src/sys/pfSense_SMP.10 amd64
Logging:
Mar 4 15:58:17 gwaus check_reload_status: Linkup starting ue0
Mar 4 15:58:17 gwaus kernel: ue0: link state changed to DOWN
Mar 4 15:58:17 gwaus kernel: ue0: link state changed to UP
Mar 4 15:58:17 gwaus check_reload_status: Linkup starting ue0
Mar 4 15:58:18 gwaus php-fpm92691: /rc.linkup: Hotplug event detected for LAN but ignoring since interface is configured with static IP (192.168.13.1 )
Mar 4 15:58:18 gwaus php-fpm92691: /rc.linkup: Hotplug event detected for LAN but ignoring since interface is configured with static IP (192.168.13.1 )
Mar 4 15:58:18 gwaus check_reload_status: rc.newwanip starting ue0
Mar 4 15:58:19 gwaus php-fpm92691: /rc.newwanip: rc.newwanip: Info: starting on ue0.
Mar 4 15:58:19 gwaus php-fpm92691: /rc.newwanip: rc.newwanip: on (IP address: 192.168.13.1) (interface: LAN[lan]) (real interface: ue0).
Mar 4 15:58:19 gwaus check_reload_status: Reloading filter
Mar 4 16:34:40 gwaus check_reload_status: Linkup starting ue0
Mar 4 16:34:40 gwaus kernel: ue0: link state changed to DOWN
Mar 4 16:34:40 gwaus kernel: ue0: link state changed to UP
Mar 4 16:34:40 gwaus check_reload_status: Linkup starting ue0
Mar 4 16:34:41 gwaus php-fpm92691: /rc.linkup: Hotplug event detected for LAN but ignoring since interface is configured with static IP (192.168.13.1 )
Mar 4 16:34:41 gwaus php-fpm92691: /rc.linkup: Hotplug event detected for LAN but ignoring since interface is configured with static IP (192.168.13.1 )
Mar 4 16:34:41 gwaus check_reload_status: rc.newwanip starting ue0
Mar 4 16:34:42 gwaus php-fpm92691: /rc.newwanip: rc.newwanip: Info: starting on ue0.
Mar 4 16:34:42 gwaus php-fpm92691: /rc.newwanip: rc.newwanip: on (IP address: 192.168.13.1) (interface: LAN[lan]) (real interface: ue0).
Mar 4 16:34:42 gwaus check_reload_status: Reloading filter
Updated by Chris Buechler about 10 years ago
- Category changed from Interfaces to Operating System
- Target version deleted (
2.2.1)
I don't see any obvious commits in -STABLE that are specific to that issue. If you can point us to a specific change that fixed it, we can pull that in as a patch.
re: your comment in that PR, stable releases are always from -RELEASE branches, -STABLE are development branches in FreeBSD. 2.2.x will stay on 10.1-REL. Where there are specific problems fixed in CURRENT or STABLE that impact our users, we may pull in those fixes.
Updated by Armando Lima Amaral about 10 years ago
Chris, thanks for explaining how it works.
I'm not sure it was corrected at all. The only reference that I have it is in that bug id at FreeBSD's bugzilla. I also looked for this correction and wasn't able to find anything.
Just to make sure that I understood, if it is a bug in the driver, FreeBSD developers have do correct that before you pull that code as a patch for the pfsense. am I right?
Thanks!
Updated by Chris Buechler about 10 years ago
Generally driver bug fixes only are made in FreeBSD-STABLE, so they hit the next release (10.2 in about 6 months, for what's now 10-STABLE). If this works now in 10-STABLE, there is something there we could pull in as a patch to our builds (like we did with one of the USB wifi cards last week). Without knowing what fixed it and that it's definitely fixed, it's not something we can do anything with. If you could point us to a specific commit that fixes it, we could get a patch in. I didn't see any relevant changes in that driver at a glance.
Updated by Chris Buechler almost 10 years ago
- Status changed from New to Needs Patch
not something we'll fix. Should work in 2.3 release, based on FreeBSD 10.2, and if someone wants to submit a patch to fix in 10.1 we can include it.
Updated by Oleg Cherkasov almost 8 years ago
It seems the problem remains in 2.3.4 release.
Updated by Russell Morris almost 8 years ago
FYI, still happening in v2.4 - but is on the FreeBSD HW compatibility list. Anything I can do to help debug?
Thanks!