Bug 195811 - Problem with axge driver for AX88179
Summary: Problem with axge driver for AX88179
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: usb (show other bugs)
Version: 10.1-RELEASE
Hardware: amd64 Any
: --- Affects Many People
Assignee: freebsd-usb (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-08 17:25 UTC by jseidel
Modified: 2015-03-06 18:09 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jseidel 2014-12-08 17:25:41 UTC
All,

I am having an issue with the axge driver on 10.1-RELEASE, it was working perfectly fine with 10.0-STABLE and since the upgrade it will work fine for awhile then its like the device just turns off. The only way to fix it is to either reboot of unplug the usb ethernet adapter and plug it back in.

I've tried it both as a module and building the driver into the kernel as well. Same results.

This is from the messages log.

Dec  8 03:06:48 nuc kernel: <6<6>newnfs>n server ewnfs server 192.11692ne.w168.1
n0n.2f:s se/rMuvletri m1e9d2i.a16:8 .10n.o2t: /rMesupolndtiinmged
Dec  8 03:06:48 nuc kernel: i8e
Dec  8 03:06:48 nuc kernel:
Dec  8 03:06:48 nuc kernel: <<66>>wn.1fs0 .se2r:v/eMurlt im1e9d2.i1a6:8 .no1t0 .
2:/reMsultim
Dec  8 03:06:48 nuc kernel: epdionad:i ngnot r
Dec  8 03:06:48 nuc kernel: e
Dec  8 03:06:48 nuc kernel: sp<6>a: not respondoinng
Dec  8 03:06:48 nuc kernel: d
Dec  8 03:06:48 nuc kernel: ing
Dec  8 03:07:22 nuc kernel: ue0: link state changed to DOWN

Dec  8 03:13:39 nuc kernel: ugen0.2: <ASIX Elec. Corp.> at usbus0 (disconnected)
Dec  8 03:13:40 nuc kernel: axge0: at uhub0, port 12, addr 2 (disconnected)
Dec  8 03:13:40 nuc kernel: rgephy0: detached
Dec  8 03:13:40 nuc kernel: miibus0: detached
Dec  8 03:13:43 nuc kernel: ugen0.2: <ASIX Elec. Corp.> at usbus0
Dec  8 03:13:43 nuc kernel: axge0: <NetworkInterface> on usbus0
Dec  8 03:13:43 nuc kernel: axge0: <NetworkInterface> on usbus0
Dec  8 03:13:44 nuc kernel: miibus0: <MII bus> on axge0
Dec  8 03:13:44 nuc kernel: rgephy0: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 3 on miibus0
Dec  8 03:13:44 nuc kernel: rgephy0:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow
Dec  8 03:13:44 nuc kernel: ue0: <USB Ethernet> on axge0
Dec  8 03:13:44 nuc kernel: ue0: Ethernet address: 8c:ae:4c:fd:2b:25
Dec  8 03:13:44 nuc devd: Executing '/etc/pccard_ether ue0 start'
Dec  8 03:13:44 nuc kernel: ue0: link state changed to DOWN
Dec  8 03:13:49 nuc kernel: ue0: link state changed to UP
Dec  8 03:13:49 nuc devd: Executing '/etc/rc.d/dhclient quietstart ue0'
Dec  8 03:13:52 nuc kernel: ue0: link state changed to DOWN
Dec  8 03:13:56 nuc kernel: ue0: link state changed to UP
Dec  8 03:13:56 nuc devd: Executing '/etc/rc.d/dhclient quietstart ue0'
Dec  8 03:14:02 nuc kernel: newnfs server 192.168.10.2:/Multimedia: is alive again


Here is the usbconfig:
ugen1.1: <EHCI root HUB Intel> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
ugen0.1: <XHCI root HUB 0x8086> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA)
ugen1.2: <product 0x8000 vendor 0x8087> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
ugen0.2: <AX88179 ASIX Elec. Corp.> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON (124mA)
Comment 1 jseidel 2014-12-08 17:27:00 UTC
at Dec  8 03:13:39 is when I unplug the device to get it working again.
Comment 2 jseidel 2015-01-29 15:32:29 UTC
Seems to be fixed in 10.1-STABLE.
Comment 3 Armando Amaral 2015-03-05 00:09:27 UTC
I'm afraid the bug is still on.
I have an installation with Intel NUC using a USB3 Trendnet Adapter based on AX88179.

My interface resets every other hour in a softer way but I still lose network access for a few seconds.

Loggging:

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-fpm[92691]: /rc.linkup: Hotplug event detected for LAN(lan) but ignoring since interface is configured with static IP (192.168.13.1 )
Mar  4 15:58:18 gwaus php-fpm[92691]: /rc.linkup: Hotplug event detected for LAN(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-fpm[92691]: /rc.newwanip: rc.newwanip: Info: starting on ue0.
Mar  4 15:58:19 gwaus php-fpm[92691]: /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-fpm[92691]: /rc.linkup: Hotplug event detected for LAN(lan) but ignoring since interface is configured with static IP (192.168.13.1 )
Mar  4 16:34:41 gwaus php-fpm[92691]: /rc.linkup: Hotplug event detected for LAN(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-fpm[92691]: /rc.newwanip: rc.newwanip: Info: starting on ue0.
Mar  4 16:34:42 gwaus php-fpm[92691]: /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
Comment 4 Armando Amaral 2015-03-05 00:12:15 UTC
I'm using PfSense: 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
Comment 5 jseidel 2015-03-05 20:22:08 UTC
(In reply to Armando Amaral from comment #4)
Try upgrading to 10.1-Stable, it fixed my issue.
Comment 6 Armando Amaral 2015-03-06 18:09:00 UTC
(In reply to jseidel from comment #5)

Thanks Jseidel. I'm trying to report this bug for pfSense developers. They have to change the kernel version for the stable. Even in the developer version now they're still using the Release.