ARM GLX Khadas VIM Pro - Ethernet detected as only 10Mbps and stalled after some traffic
crow at linux.org.ba
Thu Jun 8 10:30:12 PDT 2017
I have here two problems with Khadas VIM Pro device and Ethernet.
1) sometimes with the Kernel Linux 4.12-rc4 the Ethernet link is Up
but only 10Mbps.
Don't work (either SSH to device nor over serial console to ping out)
meson8b-dwmac c9410000.ethernet eth0: Link is Up - 10Mbps/Half - flow
Works (if I do ifconfig eth0 down / up):
meson8b-dwmac c9410000.ethernet eth0: Link is Down
meson8b-dwmac c9410000.ethernet eth0: Link is Up - 100Mbps/Full - flow
Whole log could be found in .
2) if downloading an amount of data while connected to device over
SSH, connection will stall and after some minutes SSH session would be
disconnected. Nothing is written in dmesg and ethtool shows me same
values before when Ethernet was working, and after when connection
stall. Whole log can be found in 
SSH to device (OK)
-> Cloning linux git repo...
Cloning into bare repository '/opt/mmcblk1/linux-aarch64-git/linux'...
remote: Counting objects: 5399033, done.
remote: Compressing objects: 100% (1495/1495), done.
Receiving objects: 3% (161971/5399033), 73.20 MiB | 6.19 MiB/s
here the download stalled and SSH connection also stalled but not disconnected
# ethtool eth0
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Link partner advertised link modes: 10baseT/Half 10baseT/Full
Link partner advertised pause frame use: No
Link partner advertised auto-negotiation: Yes
Supports Wake-on: ug
Current message level: 0x0000003f (63)
drv probe link timer ifdown ifup
Link detected: yes
after 2 min SSH connection disconnected
over serial console:
# ping -c3 18.104.22.168
PING 22.214.171.124 (126.96.36.199) 56(84) bytes of data.
>From 10.8.8.6 icmp_seq=1 Destination Host Unreachable
--- 188.8.131.52 ping statistics ---
3 packets transmitted, 0 received, +1 errors, 100% packet loss, time 2060ms
nothing in dmesg or in journalctl
also here is helps only to take port down and again up. restarting
networking services fails "timed out".
More information about the linux-amlogic