cancel
Showing results for 
Search instead for 
Did you mean: 
cancel

Who Me Too'd this topic

Auto-negociation messages from kernel on RV320 when forced in 100-full?

aforster.home
Level 1
Level 1

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:28Kernelkernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[2] 
2015-09-06, 00:11:28Kernelkernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[1] 
2015-09-06, 00:11:31Kernelkernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[2] 
2015-09-06, 00:11:31Kernelkernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[1] 
2015-09-06, 00:11:33Kernelkernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[2] 
2015-09-06, 00:11:33Kernelkernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[1] 
2015-09-06, 00:11:34Kernelkernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[2] 
2015-09-06, 00:11:34Kernelkernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[1] 
2015-09-06, 00:11:41Kernelkernel: WARNING: no highest common denominator or auto-negotiation not complete 
2015-09-06, 00:11:41Kernellast message repeated 2 times 
2015-09-06, 00:11:41Kernelkernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[0], duplex[0] 
2015-09-06, 00:11:41Kernelkernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[1] 
2015-09-06, 00:11:52Kernelkernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[2] 
2015-09-06, 00:11:52Kernelkernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[1] 
2015-09-06, 00:11:55Kernelkernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[2] 
2015-09-06, 00:11:55Kernelkernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[1] 
2015-09-06, 00:11:56Kernelkernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[2] 
2015-09-06, 00:11:56Kernelkernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[1] 
2015-09-06, 00:15:02Kernelkernel: wrong ip[0],not_list[0] 
2015-09-06, 00:21:10Kernelkernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[2] 
2015-09-06, 00:21:11Kernelkernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[1] 
2015-09-06, 00:21:14Kernelkernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[2] 
2015-09-06, 00:21:15Kernelkernel: nk_bcm53115_sync_speeds_phy_to_mac(): sport[5], speed[1], duplex[1] 
2015-09-06, 00:21:54Kernel

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?

 

Who Me Too'd this topic