[FS#4032] Uplink ethernet ports not connecting at gigabit speeds (Ath79) (Attachment added)
openwrt-bugs at lists.openwrt.org
Sat Oct 9 09:00:25 PDT 2021
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#4032 - Uplink ethernet ports not connecting at gigabit speeds (Ath79)
User who did this - Boris Gjenero (dreamlayers)
It's weird that "Atheros AR8216/AR8236/AR8316 mdio.0:04" is printing messages about LAN switch ports going up and down, like this:
[ 2598.530695] Atheros AR8216/AR8236/AR8316 mdio.0:04: Port 1 is down
[ 2602.626507] Atheros AR8216/AR8236/AR8316 mdio.0:04: Port 1 is up
[ 2681.473414] Atheros AR8216/AR8236/AR8316 mdio.0:04: Port 2 is down
[ 2687.617192] Atheros AR8216/AR8236/AR8316 mdio.0:04: Port 2 is up
That is supposed to be the phy for eth1, the WAN interface, but those are LAN events, which I can create manually. Why are LAN things being printed? This made me think that maybe the phy were swapped in the old configuration and mdio.0:00 might make gigabit work. So I tried the attached patch, and got a gigabit connection according to both dmesg and the router. However, no data was received on eth1, and so there was no internet access. With the patch, WAN port disconnection and reconnection was reported as "Port 5". With unpatched 21.02.0, there is no such reporting, and instead I see "eth1: link down" and "eth1: link up (100Mbps/Full duplex)".
This patch is attached for exact record of what I did, not as a recommended solution.
One or more files have been attached.
More information can be found at the following URL:
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
More information about the openwrt-bugs