You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When updating the above device to the latest trunk, LAN access is lost, however Wireless works fine. The issue is apparent on both my own self compiled image as well as the dev openwrt snapshot, as can be seen from the below log snippet, eth0 enters a disabled state and never comes up;
boot-log-broken.txt:Sat Mar 9 19:10:05 2019 kern.info kernel: [ 1.860843] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:18 [uid=00808008, driver=Generic PHY]
boot-log-broken.txt:Sat Mar 9 19:10:05 2019 kern.info kernel: [ 1.870771] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:SGMII
boot-log-broken.txt:Sat Mar 9 19:10:05 2019 kern.info kernel: [ 4.619239] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
boot-log-broken.txt:Sat Mar 9 19:10:12 2019 kern.info kernel: [ 20.205456] br-lan: port 1(eth0) entered blocking state
boot-log-broken.txt:Sat Mar 9 19:10:12 2019 kern.info kernel: [ 20.210911] br-lan: port 1(eth0) entered disabled state
boot-log-broken.txt:Sat Mar 9 19:10:12 2019 kern.info kernel: [ 20.216564] device eth0 entered promiscuous mode
Expected behaviour taken from the logs of the device running the stable release;
boot-log-working.txt:Sat Mar 9 19:30:12 2019 kern.info kernel: [ 2.025604] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:00 [uid=004dd036, driver=Atheros AR8216/AR8236/AR8316]
boot-log-working.txt:Sat Mar 9 19:30:12 2019 kern.info kernel: [ 2.037168] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:SGMII
boot-log-working.txt:Sat Mar 9 19:30:12 2019 kern.info kernel: [ 4.573592] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
boot-log-working.txt:Sat Mar 9 19:30:12 2019 kern.info kernel: [ 5.635550] eth0: link up (1000Mbps/Full duplex)
boot-log-working.txt:Sat Mar 9 19:30:12 2019 kern.info kernel: [ 5.640453] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
boot-log-working.txt:Sat Mar 9 19:30:12 2019 kern.info kernel: [ 22.348036] eth0: link down
boot-log-working.txt:Sat Mar 9 19:30:20 2019 kern.info kernel: [ 43.666896] br-lan: port 1(eth0) entered blocking state
boot-log-working.txt:Sat Mar 9 19:30:20 2019 kern.info kernel: [ 43.672306] br-lan: port 1(eth0) entered disabled state
boot-log-working.txt:Sat Mar 9 19:30:20 2019 kern.info kernel: [ 43.678060] device eth0 entered promiscuous mode
boot-log-working.txt:Sat Mar 9 19:30:21 2019 kern.info kernel: [ 44.675621] eth0: link up (1000Mbps/Full duplex)
boot-log-working.txt:Sat Mar 9 19:30:21 2019 kern.info kernel: [ 44.680539] br-lan: port 1(eth0) entered blocking state
boot-log-working.txt:Sat Mar 9 19:30:21 2019 kern.info kernel: [ 44.685973] br-lan: port 1(eth0) entered forwarding state
boot-log-working.txt:Sat Mar 9 19:30:21 2019 daemon.notice netifd: Network device 'eth0' link is up
The problem appears to the PHY being detected incorrectly, in the broken example, the below is observed and the Generic PHY driver used;
ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:18 [uid=00808008, driver=Generic PHY
where as this is seen on the working example, with the Atheros driver being used ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:00 [uid=004dd036, driver=Atheros AR8216/AR8236/AR8316]
I believe this issue is related to commit d3506d1 and reversing the patch restores LAN connectivity, with the PHY being detected exactly as per the above working example
I've attached boot logs with working/non-working examples, please let me know if any other information is required or if there's anything I can test to help resolve
The text was updated successfully, but these errors were encountered:
I've prepared following [[https://git.openwrt.org/?p=openwrt/staging/ynezz.git;a=commit;h=dafbbf8eff947a81ccfd531cf0dab433b9c39c35
|commit]] which I planto push once you confirm, that it's working for you. Could you please give me your Tested-by: Real Name real@email.com so I can add it to the commit which fixes this problem as well?
noblemtw:
When updating the above device to the latest trunk, LAN access is lost, however Wireless works fine. The issue is apparent on both my own self compiled image as well as the dev openwrt snapshot, as can be seen from the below log snippet, eth0 enters a disabled state and never comes up;
boot-log-broken.txt:Sat Mar 9 19:10:05 2019 kern.info kernel: [ 1.860843] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:18 [uid=00808008, driver=Generic PHY]
boot-log-broken.txt:Sat Mar 9 19:10:05 2019 kern.info kernel: [ 1.870771] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:SGMII
boot-log-broken.txt:Sat Mar 9 19:10:05 2019 kern.info kernel: [ 4.619239] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
boot-log-broken.txt:Sat Mar 9 19:10:12 2019 kern.info kernel: [ 20.205456] br-lan: port 1(eth0) entered blocking state
boot-log-broken.txt:Sat Mar 9 19:10:12 2019 kern.info kernel: [ 20.210911] br-lan: port 1(eth0) entered disabled state
boot-log-broken.txt:Sat Mar 9 19:10:12 2019 kern.info kernel: [ 20.216564] device eth0 entered promiscuous mode
Expected behaviour taken from the logs of the device running the stable release;
boot-log-working.txt:Sat Mar 9 19:30:12 2019 kern.info kernel: [ 2.025604] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:00 [uid=004dd036, driver=Atheros AR8216/AR8236/AR8316]
boot-log-working.txt:Sat Mar 9 19:30:12 2019 kern.info kernel: [ 2.037168] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:SGMII
boot-log-working.txt:Sat Mar 9 19:30:12 2019 kern.info kernel: [ 4.573592] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
boot-log-working.txt:Sat Mar 9 19:30:12 2019 kern.info kernel: [ 5.635550] eth0: link up (1000Mbps/Full duplex)
boot-log-working.txt:Sat Mar 9 19:30:12 2019 kern.info kernel: [ 5.640453] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
boot-log-working.txt:Sat Mar 9 19:30:12 2019 kern.info kernel: [ 22.348036] eth0: link down
boot-log-working.txt:Sat Mar 9 19:30:20 2019 kern.info kernel: [ 43.666896] br-lan: port 1(eth0) entered blocking state
boot-log-working.txt:Sat Mar 9 19:30:20 2019 kern.info kernel: [ 43.672306] br-lan: port 1(eth0) entered disabled state
boot-log-working.txt:Sat Mar 9 19:30:20 2019 kern.info kernel: [ 43.678060] device eth0 entered promiscuous mode
boot-log-working.txt:Sat Mar 9 19:30:21 2019 kern.info kernel: [ 44.675621] eth0: link up (1000Mbps/Full duplex)
boot-log-working.txt:Sat Mar 9 19:30:21 2019 kern.info kernel: [ 44.680539] br-lan: port 1(eth0) entered blocking state
boot-log-working.txt:Sat Mar 9 19:30:21 2019 kern.info kernel: [ 44.685973] br-lan: port 1(eth0) entered forwarding state
boot-log-working.txt:Sat Mar 9 19:30:21 2019 daemon.notice netifd: Network device 'eth0' link is up
The problem appears to the PHY being detected incorrectly, in the broken example, the below is observed and the Generic PHY driver used;
ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:18 [uid=00808008, driver=Generic PHY
where as this is seen on the working example, with the Atheros driver being used
ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:00 [uid=004dd036, driver=Atheros AR8216/AR8236/AR8316]
I believe this issue is related to commit d3506d1 and reversing the patch restores LAN connectivity, with the PHY being detected exactly as per the above working example
I've attached boot logs with working/non-working examples, please let me know if any other information is required or if there's anything I can test to help resolve
The text was updated successfully, but these errors were encountered: