AXE(4) bug still present in 2.5.1
-
Re: Driver bug for AX88179 on pfSense 2.2
I have same exact device and have same issues w/ 2.5.1
Hotplug detection about every 20 secs.
This is also happening w/ my APC UPS and the HP mouse.I'm suspecting this is more to do not w/ specific devices, but w/ how pfSense polls the USB bus for status changes. Other OSs on same hardware, Win, Linux, etc... don't have this issue at all.
Using HP t730 Plus as the hardware w/o VMs.
DG
-
Every 20s seems significantly different to either the previously reported cases or the linked bug report.
The same advice still applies though. Test it in FreeBSD. If it fails there open bug with FreeBSD.
If there is an existing fix we can try to pull that into pfSense if it's not in 12.2 stable yet.What do your logs show?
Try booting in verbose mode, do you see anything additional logged?
Steve
-
This is what I'm getting on interface (ue0):
Jun 28 18:57:39 check_reload_status 375 Linkup starting ue0
Jun 28 18:57:39 kernel ue0: link state changed to DOWN
Jun 28 18:57:39 kernel ue0: link state changed to UP
Jun 28 18:57:39 check_reload_status 375 Linkup starting ue0
Jun 28 18:57:39 check_reload_status 375 Linkup starting ue0
Jun 28 18:57:40 php-fpm 13765 /rc.linkup: Hotplug event detected for IOT(opt2) static IP (192.168.50.1 )
Jun 28 18:57:40 check_reload_status 375 Reloading filter
Jun 28 18:57:40 php-fpm 13765 /rc.linkup: Hotplug event detected for IOT(opt2) static IP (192.168.50.1 )
Jun 28 18:57:40 check_reload_status 375 rc.newwanip starting ue0
Jun 28 18:57:40 check_reload_status 375 Reloading filter
Jun 28 18:57:40 php-fpm 37650 /rc.linkup: Hotplug event detected for IOT(opt2) static IP (192.168.50.1 )
Jun 28 18:57:40 php-fpm 13765 /rc.linkup: Hotplug event detected for IOT(opt2) static IP (192.168.50.1 )
Jun 28 18:57:40 check_reload_status 375 rc.newwanip starting ue0
Jun 28 18:57:41 php-fpm 46987 /rc.newwanip: rc.newwanip: Info: starting on ue0.
Jun 28 18:57:41 php-fpm 46987 /rc.newwanip: rc.newwanip: on (IP address: 192.168.50.1) (interface: IOT[opt2]) (real interface: ue0).
Jun 28 18:57:41 check_reload_status 375 Reloading filter
Jun 28 18:57:41 php-fpm 46987 /rc.newwanip: rc.newwanip: Info: starting on ue0.
Jun 28 18:57:41 php-fpm 46987 /rc.newwanip: rc.newwanip: on (IP address: 192.168.50.1) (interface: IOT[opt2]) (real interface: ue0).
Jun 28 18:57:49 kernel ue0: link state changed to DOWN
Jun 28 18:57:49 kernel ue0: link state changed to UP
Jun 28 18:57:49 check_reload_status 375 Linkup starting ue0
Jun 28 18:57:49 check_reload_status 375 Linkup starting ue0
Jun 28 18:57:49 kernel ue0: link state changed to DOWN
Jun 28 18:57:49 kernel ue0: link state changed to UPNothing physically changes about the machine and I've even tried replugging into different ports. Same problem, even from different root hubs. FreeBSD devs previously closed a ticket on this exact device issue, so I'm stumped. This is a new setup for me as I needed to upgrade from consumer dd-wrt router (can't handle Gb+ services).
DG
-
Which FreeBSD ticket?
USB NICs are notoriously bad in FreeBSD unfortunately which is why almost everyone will tell you not to use them unless you absolutely have no choice.
One thing we have seen is USB NICs using the generic driver rather than the specific one for the hardware which can give odd results.
What does the system log show when you connect the USB NIC?
Steve
-
This is what I get from a phy disconnect and re-con:
Jun 29 16:39:14 kernel ugen0.2: <ASIX Elec. Corp. AX88179> at usbus0 (disconnected)
Jun 29 16:39:14 kernel axge0: at uhub3, port 2, addr 1 (disconnected)
Jun 29 16:39:14 kernel rgephy1: detached
Jun 29 16:39:14 kernel miibus1: detached
Jun 29 16:39:14 avahi-daemon 90518 Withdrawing address record for 192.168.50.1 on ue0.
Jun 29 16:39:14 avahi-daemon 90518 Leaving mDNS multicast group on interface ue0.IPv4 with address 192.168.50.1.
Jun 29 16:39:14 avahi-daemon 90518 Interface ue0.IPv4 no longer relevant for mDNS.
Jun 29 16:39:14 avahi-daemon 90518 Withdrawing workstation service for ue0.
Jun 29 16:39:14 kernel axge0: detached
Jun 29 16:39:15 vnstatd 79820 Interface "ue0" disabled.
Jun 29 16:39:23 kernel ugen0.2: <ASIX Elec. Corp. AX88179> at usbus0
Jun 29 16:39:23 kernel axge0 on uhub3
Jun 29 16:39:23 kernel axge0: <NetworkInterface> on usbus0
Jun 29 16:39:24 kernel miibus1: <MII bus> on axge0
Jun 29 16:39:24 kernel rgephy1: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 3 on miibus1
Jun 29 16:39:24 kernel rgephy1: 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
Jun 29 16:39:24 kernel ue0: <USB Ethernet> on axge0
Jun 29 16:39:24 kernel ue0: Ethernet address: 28:ee:52:15:97:82
Jun 29 16:39:25 vnstatd 79820 Interface "ue0" enabled.
Jun 29 16:39:25 check_reload_status 375 Linkup starting ue0
Jun 29 16:39:25 kernel ue0: link state changed to DOWN
Jun 29 16:39:26 php-fpm 337 /rc.linkup: Hotplug event detected for IOT(opt2) static IP (192.168.50.1 )
Jun 29 16:39:26 check_reload_status 375 Reloading filter
Jun 29 16:39:28 check_reload_status 375 Linkup starting ue0
Jun 29 16:39:28 kernel ue0: link state changed to UP
Jun 29 16:39:29 php-fpm 57281 /rc.linkup: Hotplug event detected for IOT(opt2) static IP (192.168.50.1 )
Jun 29 16:39:29 check_reload_status 375 rc.newwanip starting ue0
Jun 29 16:39:29 check_reload_status 375 Reloading filter
Jun 29 16:39:30 php-fpm 57281 /rc.newwanip: rc.newwanip: Info: starting on ue0.
Jun 29 16:39:30 php-fpm 57281 /rc.newwanip: rc.newwanip: on (IP address: 192.168.50.1) (interface: IOT[opt2]) (real interface: ue0).
Jun 29 16:39:30 check_reload_status 375 Reloading filter
Jun 29 16:40:36 check_reload_status 375 Syncing firewall
Jun 29 16:40:42 check_reload_status 375 Reloading filter
Jun 29 16:40:42 php-fpm 338 /interfaces.php: Creating rrd update script
Jun 29 16:40:46 check_reload_status 375 Syncing firewall
Jun 29 16:40:48 check_reload_status 375 Linkup starting ue0
Jun 29 16:40:48 kernel ue0: link state changed to DOWN
Jun 29 16:40:48 check_reload_status 375 Restarting ipsec tunnels
Jun 29 16:40:49 php-fpm 338 /rc.linkup: Hotplug event detected for IOT(opt2) static IP (192.168.50.1 )
Jun 29 16:40:49 check_reload_status 375 Reloading filter
Jun 29 16:40:51 check_reload_status 375 Linkup starting ue0
Jun 29 16:40:51 kernel ue0: link state changed to UP
Jun 29 16:40:52 php-fpm 338 /rc.linkup: Hotplug event detected for IOT(opt2) static IP (192.168.50.1 )
Jun 29 16:40:52 check_reload_status 375 rc.newwanip starting ue0
Jun 29 16:40:52 check_reload_status 375 Reloading filter
Jun 29 16:40:52 check_reload_status 375 updating dyndns opt2
Jun 29 16:40:53 php-fpm 338 /rc.newwanip: rc.newwanip: Info: starting on ue0.
Jun 29 16:40:53 php-fpm 338 /rc.newwanip: rc.newwanip: on (IP address: 192.168.50.1) (interface: IOT[opt2]) (real interface: ue0).
Jun 29 16:40:53 check_reload_status 375 Reloading filter
Jun 29 16:40:54 check_reload_status 375 Reloading filter
Jun 29 16:40:54 php-fpm 57281 /interfaces.php: Creating rrd update script
Jun 29 16:41:10 upsmon 86403 UPS BE600M1 is unavailable
Jun 29 16:41:17 kernel ue0: link state changed to DOWN
Jun 29 16:41:18 check_reload_status 375 Linkup starting ue0
Jun 29 16:41:18 kernel ue0: link state changed to UP
Jun 29 16:41:18 check_reload_status 375 Linkup starting ue0
Jun 29 16:41:18 kernel ue0: link state changed to DOWN
Jun 29 16:41:18 kernel ue0: link state changed to UP
Jun 29 16:41:18 kernel ue0: link state changed to DOWN
Jun 29 16:41:18 check_reload_status 375 Linkup starting ue0
Jun 29 16:41:18 kernel ue0: link state changed to UP
Jun 29 16:41:18 check_reload_status 375 Linkup starting ue0
Jun 29 16:41:18 check_reload_status 375 Linkup starting ue0
Jun 29 16:41:18 check_reload_status 375 Linkup starting ue0
Jun 29 16:41:19 php-fpm 338 /rc.linkup: Hotplug event detected for IOT(opt2) static IP (192.168.50.1 )
Jun 29 16:41:19 check_reload_status 375 Reloading filter
Jun 29 16:41:19 php-fpm 337 /rc.linkup: Hotplug event detected for IOT(opt2) static IP (192.168.50.1 )
Jun 29 16:41:19 check_reload_status 375 rc.newwanip starting ue0
Jun 29 16:41:19 check_reload_status 375 Reloading filter
Jun 29 16:41:19 php-fpm 57281 /rc.linkup: Hotplug event detected for IOT(opt2) static IP (192.168.50.1 )
Jun 29 16:41:19 php-fpm 338 /rc.linkup: Hotplug event detected for IOT(opt2) static IP (192.168.50.1 )
Jun 29 16:41:19 check_reload_status 375 rc.newwanip starting ue0
Jun 29 16:41:19 php-fpm 337 /rc.linkup: Hotplug event detected for IOT(opt2) static IP (192.168.50.1 )
Jun 29 16:41:19 php-fpm 57281 /rc.linkup: Hotplug event detected for IOT(opt2) static IP (192.168.50.1 )
Jun 29 16:41:19 check_reload_status 375 rc.newwanip starting ue0
Jun 29 16:41:20 php-fpm 338 /rc.newwanip: rc.newwanip: Info: starting on ue0.
Jun 29 16:41:20 php-fpm 338 /rc.newwanip: rc.newwanip: on (IP address: 192.168.50.1) (interface: IOT[opt2]) (real interface: ue0).
Jun 29 16:41:20 check_reload_status 375 Reloading filter
Jun 29 16:41:20 php-fpm 337 /rc.newwanip: rc.newwanip: Info: starting on ue0.
Jun 29 16:41:20 php-fpm 337 /rc.newwanip: rc.newwanip: on (IP address: 192.168.50.1) (interface: IOT[opt2]) (real interface: ue0).
Jun 29 16:41:20 php-fpm 337 /rc.newwanip: rc.newwanip: Info: starting on ue0.
Jun 29 16:41:20 php-fpm 337 /rc.newwanip: rc.newwanip: on (IP address: 192.168.50.1) (interface: IOT[opt2]) (real interface: ue0).DG
-
@djgans said in AXE(4) bug still present in 2.5.1:
Jun 29 16:39:23 kernel axge0 on uhub3
Definitely using the correct driver then.
It might be stuck autonegotiating and it looks to support all the expected manual modes.
Can you set it to a fixed link speed/duplex in the interface config? Does that stop it flapping?
Steve
-
I'm currently using the USB for 2 reasons, 1) repurposing my old router, I found I can't pass-through the VLAN to wifi, so I had to segment the LAN side with separate radios. 2) I'm reserving my bxe1 10Gb SFP+ port for november when COX is supposedly doing FTTH roll-out in Phx.
I'd rather not use the SFP+ port w/ RJ45 trans. since they get very hot and having a thin client, I don't want to test it's TDP tolerances yet.
As an aside, I did find the t730 won't work w/ most PCIe x8 NICs w/ SFP+. Tried Mellanox 3 Pro and 4, DED. Tried an Intel X520-DA2, won't boot w/o CMOS resetting. Tried an BCM57810S generic Qlogic NetXtreme and zero problems. Never got around to testing a Chelsio after the Broadcom success. The Realtek native port works just fine. Also, for whatever reason, displayport connection goes to sleep and I lose console access, except through webconfig.
Why is USB such a stink for FreeBSD? Any "good" USB NICs out there?
DG
-
@stephenw10
Tried them all. No change.Here's my usbconfig output:
ugen5.1: <AMD EHCI root HUB> at usbus5, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
ugen1.1: <0x1022 XHCI root HUB> at usbus1, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA)
ugen3.1: <AMD EHCI root HUB> at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
ugen0.1: <0x1022 XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA)
ugen2.1: <AMD OHCI root HUB> at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA)
ugen4.1: <AMD OHCI root HUB> at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA)
ugen2.2: <vendor 0x0d62 HP USB Business Slim Keyboard> at usbus2, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (100mA)
ugen2.3: <American Power Conversion Back-UPS ES 600M1 FW:928.a8 .D USB FW:a8> at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (2mA)
ugen0.2: <ASIX Elec. Corp. AX88179> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON (124mA)Could the power status on the hubs be causing an issue (pwr=save (0mA) )? I read in the FreeBSD forums something about "USB quirks" settings for the kernel and hubs falsifying their power status.
DG
-
I don't think it's something a USB quirk would help with, the NIC itself is not being disconnected it's the Ethernet losing link.
I would look at using VLANs on the existing LAN interface with a managed switch rather than a USB NIC.
Steve
-
I kind of figured that was where u were leading w/ this. It just means I need to just dump the old Asus 68 and get a WAP w/ VLAN capability for private & IoT SSIDs. I already have a Microtik CRS305 online and I'm think of an Engenius 357 or 377 to attach; not so sure about Ubiquiti. Never messed w/ either, but this is what's coming w/ consumers needing to upgrade to prosumer equipment. It's just unfortunate that DIYs can have a number of complications, even though repurposing thin clients has it's appeal.
David
-
The AP doesn't have to support VLANs, it could be untagged between the AP and switch.
You just couldn't use multiple SSIDs on it. It would need to be for IoT only.Steve
-
Any particular 5-port gigabit managed switch u recommend? I'd pass the CRS305 ethernet thru it to feed the separate APs.
David
-
Not really, anything that is VLAN capable should be fine in that application.
Steve