09-05-2015 08:36 PM
Hello,
My RV320 has been freezing a lot, and although I have posted in other threads about this continued "Connected/Inactive" issue on WAN1, I didn't see any fix yet.
This problem has been happening since early versos of the firmware, and still on the current version (1.2.1.13), it is still there.
I noticed a lot of kernel messages and errors about auto-negociation, so I decided to give it a try, and fixed all ports to 100-full, as there is no way to fix them on Gigabit. The weird thing is: kernel messages about auto-negociation error are still there, as follows:
2015-09-06, 00:11:28 | Kernel | kernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[2] |
2015-09-06, 00:11:28 | Kernel | kernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[1] |
2015-09-06, 00:11:31 | Kernel | kernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[2] |
2015-09-06, 00:11:31 | Kernel | kernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[1] |
2015-09-06, 00:11:33 | Kernel | kernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[2] |
2015-09-06, 00:11:33 | Kernel | kernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[1] |
2015-09-06, 00:11:34 | Kernel | kernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[2] |
2015-09-06, 00:11:34 | Kernel | kernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[1] |
2015-09-06, 00:11:41 | Kernel | kernel: WARNING: no highest common denominator or auto-negotiation not complete |
2015-09-06, 00:11:41 | Kernel | last message repeated 2 times |
2015-09-06, 00:11:41 | Kernel | kernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[0], duplex[0] |
2015-09-06, 00:11:41 | Kernel | kernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[1] |
2015-09-06, 00:11:52 | Kernel | kernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[2] |
2015-09-06, 00:11:52 | Kernel | kernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[1] |
2015-09-06, 00:11:55 | Kernel | kernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[2] |
2015-09-06, 00:11:55 | Kernel | kernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[1] |
2015-09-06, 00:11:56 | Kernel | kernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[2] |
2015-09-06, 00:11:56 | Kernel | kernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[1] |
2015-09-06, 00:15:02 | Kernel | kernel: wrong ip[0],not_list[0] |
2015-09-06, 00:21:10 | Kernel | kernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[2] |
2015-09-06, 00:21:11 | Kernel | kernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[1] |
2015-09-06, 00:21:14 | Kernel | kernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[2] |
2015-09-06, 00:21:15 | Kernel | kernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[1] |
2015-09-06, 00:21:54 | Kernel | kernel: wrong ip[0],not_list[0] |
I tried to search for this error message on google, and Google could not find this sync_speeds_phy_to_mac string (believe it or not).
Anyone else has this issue?