Jump to content

Odroid C2 - Loosing conection after 5 minutes work


constantius

Recommended Posts

3 hours ago, constantius said:

4.14 does not working properly with amlogic S905 devices

Absolutely and fundamentally incorrect.  Legacy u-boot does not properly configure the memory space for the patched kernel.  That may not be the issue with C2, however that is the issue with K2

Link to comment
Share on other sites

8 hours ago, TonyMac32 said:

Legacy u-boot does not properly configure the memory space for the patched kernel.

As I said, it is a U-boot problem, not a kernel problem that is the issue with the K2, so the comparison is incorrect and has nothing to do with the blanket of "S905 devices".  The only issues I know of with C2 on mainline *kernel* involve the eMMC clock speeds needing throttled, but we have that accounted for.

Link to comment
Share on other sites

I checked the settings eth0, DNS, uninstalled even the network-manager, interfaces, even saved the resolv.conf settings in the head file. and I definitely say meson-driver loses eth0 in Armbian odroid c2 and nanopi k2. etho works about 5-10 minutes. After ping yahoo.com name or service not known - ping 192.168.1.1 destination host unreachable. With all valid eth0 settings. In nano pi k2 I can switch to wlan0 in the odroid I need to reset

Link to comment
Share on other sites

34 minutes ago, radek said:

meson8b-dwmac does not works

strange :(

I do use 

Linux odroid-c2 4.14.40-odroidc2 #53 SMP PREEMPT Fri May 11 09:18:03 CEST 2018 aarch64 aarch64 aarch64 GNU/Linux

 

root@odroid-c2:/var/log# lsmod
Module                  Size  Used by

dwmac_meson8b          16384  0
meson_drm              45056  3 meson_dw_hdmi
stmmac_platform        20480  2 dwmac_generic,dwmac_meson8b
drm_kms_helper        188416  3 meson_dw_hdmi,meson_drm,dw_hdmi
stmmac                114688  3 stmmac_platform,dwmac_generic,dwmac_meson8b
 

and dont have any disconnects - my C2 is running several days...

 

The only problem is that I have a massise growing file names /var/log/wtmp :(

In dmesg it shown after 1-2 days:
[62910.273705] systemd-journald[1405]: Failed to open system journal: No space left on device
[62910.274272] systemd-journald[1405]: Failed to open system journal: No space left on device
[62910.274562] systemd-journald[1405]: Failed to open system journal: No space left on device
[62910.275904] systemd-journald[1405]: Failed to open system journal: No space left on device
[62910.276227] systemd-journald[1405]: Failed to open system journal: No space left on device

 

Link to comment
Share on other sites

4 hours ago, radek said:

just do not tell me everything is fine

Did I ever?  I simply pointed out that a blanket statement such as "Kernel 4.14 is bad for Amlogic S905 devices" was incorrect.  I then pointed to a possible cause of the problem, memory corruption.

 

4 hours ago, radek said:

on others images eth0 driver is stmmaceth.. and this driver works

 

What is the kernel being used on these images?  4.9?  The meson8b-dwmac driver is an extension of the stmmaceth driver, with adjustments specific to differences in the IP block implementation in the Meson and Meson64 SoC's (S905).

 

This could be a tx-delay issue on the C2. 

 

The K2 is WIP.  I update it as I have time, interest, and resources.

Link to comment
Share on other sites

memory is good. I hava 6 images on 6 different micro-sd cards. 1. Armbian 5.38 Jessie XFCE  / 2. Android 6.0.1 / 3. Harkernel Ubuntu 16.04 Mate 1.12.1 / 4. Armbian 5.30 XFCE Ubuntu 16.04 / 5. Armbian 5.43 Debian 9 XFCE  / 6. Armbian 5.44 Ubuntu 18.04 XFCE ... sory android not that story but works perfectly.  Ubuntu 16.04 Mate from Hardkernel team. works perfekt. Armbian Jessie 5.38 works perfectly but slowly maybe slow micro-sd... never mind no problem, - stmmaceth driver. All these images works but strange is that Armbian 5.43 Debian 9 is on meson8b-dwmac driver and works also !!!!

Problem is Armbian 5.44 Ubuntu 18.04 - driver meson8b-dwmac.... lost connection very quickly 3-5 minutes...

I have also Nanopi K2 Armbian 5.38 ubuntu 16.04 also driver meson8b-dwmac. also lost connection but after 10-15 minutes. Needs more time to crash. But this have wifi and i can switch to wifi. But this image hangs very often without purpose. I think when i use browsers.

I really check everything. manualy configured eth0, interfaces, network manager install uninstall, edit resolv.conf... etc. Every time the same strange story. After reboot eth0 exist and when i run apt-get upgrade or apt-get install packages i have lost internet. Just doing nothing only fetching packages....

Link to comment
Share on other sites

I see that we boast about the number of single boards I have:

 

VS Mecool RK3399         FireFly RK3399     OrangePI RK3399 ,  Odroid XU4               Asus Tinker         MIQI                Cubieboard 4                    Khadas VIM2         FA NanoPiM3        Rock64              Odroid C2               FA NanoPI K2         Khadas VIM1            Minix Neo X7           Cubieboard 5         BananaPiM3        Pine H64       , Le Potato,  Renegade from Libre computers ,      Orangepi Lite 2                Orangepi OnePLUS   RaspberryPI 3+     OrangePI Prime          OrangePIPC2            Pine A64-LTS             OrangePI WIN PLUS         BananaPIM64       Pine 64+                   FA NanoPIA64       NanoPIM2       BananaPiM2Ultra      OrangePi2PlusE         OrangePi2          BananapiM2+               Odroid C1+                   Hummingboard      BananaPiM2        RaspberryPi2              Olimex Lime2                  Creator CI20 ,  (  Nano pi K1 plus - iam waiting for delivery form china. )

 

I use it in production on a daily basis tasks and I can tell every model which one is sucked up, which overheats, does not hold the cpu clocking that the image that works on it. I can also say a lot about micro-SD cards. I use finally only sandisk and samsung.

Link to comment
Share on other sites

30 minutes ago, radek said:

But this image hangs very often without purpose. I think when i use browsers.

 After reboot eth0 exist and when i run apt-get upgrade or apt-get install packages i have lost internet. Just doing nothing only fetching packages....

Maybe these are 2 problems?
Iam personally didnt use the Desktop & Browsers, becausse - from my personal view - a Desktop and WebBrowser need more than 2GB of Ram to work properly. Mostly because I often have more than 30 tabs open :) So your C2 could run into low memory before if there are some scripts at the webpages.

 

The second problem which sound familiar to me is that I sometime cant "apt upgrade" / fetch packages via "apt install" - BUT thats only a file-lock of the automatic package-installer.
So I can do a "apt update" but when the automatic updater is running I cant "apt upgrade" or install a package.

 

In this case I do use "ps -ef|grep apt" and if I see more apt-command-lines in working state I do wait some minutes and check again.

When the commands are ready then I could do my "apt upgrade"

 

But I did never lost the connection to the internet - because when the automatic updater is running I allways could do successfull a "ping 8.8.8.8" 

Link to comment
Share on other sites

46 minutes ago, radek said:

strange is that Armbian 5.43 Debian 9 is on meson8b-dwmac driver and works also !!!!

Problem is Armbian 5.44 Ubuntu 18.04 - driver meson8b-dwmac.... lost connection very quickly 3-5 minutes...

Not a surprise. We don't have any supported Bionic builds so there may be issues with beta/testing builds (since they are made only for testing and not for everyday use). They need to be compared to Xenial builds with the same kernel before claiming kernel issues.

 

And I don't see any useful logs (dmesg, armbianmonitor -u / armbianmonitor -U, ifconfig, ethtool -S, route) that could help diagnose the problem (especially since Bionic images are still testing and testing without providing logs won't help us find problems if there are any)

Link to comment
Share on other sites

guidol it is no problem with automatic upgrades .. i usually uninstall unattended-upgrades and I dont use it.

 

OK finally.;  I report that such a problem exists and I ask you to keep this in mind as the bionic will come out of the test. There are many images that I do not have to immediately have ubuntu 18.04. The problem concerns the odroid  c2 and nano pi k2, kernel 4.14, armbian kernel more than 5.38. Thank you for your attention, I wish you a good evening.

Link to comment
Share on other sites

But you still didn't deliver the needed information so that this 'bug report' is useful to solve things.. Just read again the post of @zador.blood.stained. If you want that a developer has this on his todo list (or 'to keep in mind list'). Things aren't solved by: there's a bug, now it's up to you to solve it... Things are solved by giving as much information as possible to understand what's going wrong. Why should a dev even think about takes this on his 'todo' list when the users aren't willig to deliver at least the needed informations to have a clue what's going on. 

 

Otherwise the Drepper/Poettering-approach how to react to 'bugs' seems to be reasonable...  :rolleyes: (there's probably some sarcasm inside the last part... )

Link to comment
Share on other sites

ifconfig
eth0      Link encap:Ethernet  HWaddr c2:2d:dc:69:09:b8  
          inet addr:192.168.1.13  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::bef9:68eb:35ba:dabc/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2597 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1839 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2651519 (2.6 MB)  TX bytes:846389 (846.3 KB)
          Interrupt:17 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:104 errors:0 dropped:0 overruns:0 frame:0
          TX packets:104 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:8882 (8.8 KB)  TX bytes:8882 (8.8 KB)

wlan0     Link encap:Ethernet  HWaddr b0:f1:ec:29:d5:5a  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
 

 

ethtool eth0
Settings for eth0:
    Supported ports: [ TP MII ]
    Supported link modes:   10baseT/Half 10baseT/Full 
                            100baseT/Half 100baseT/Full 
                            1000baseT/Full 
    Supported pause frame use: Symmetric Receive-only
    Supports auto-negotiation: Yes
    Advertised link modes:  10baseT/Half 10baseT/Full 
                            100baseT/Half 100baseT/Full 
                            1000baseT/Full 
    Advertised pause frame use: No
    Advertised auto-negotiation: Yes
    Link partner advertised link modes:  10baseT/Half 10baseT/Full 
                                         100baseT/Half 100baseT/Full 
    Link partner advertised pause frame use: Symmetric
    Link partner advertised auto-negotiation: Yes
    Speed: 100Mb/s
    Duplex: Full
    Port: MII
    PHYAD: 0
    Transceiver: external
    Auto-negotiation: on
    Supports Wake-on: ug
    Wake-on: d
    Current message level: 0x0000003f (63)
                   drv probe link timer ifdown ifup
    Link detected: yes
 

 

armbianmonitor -u 
System diagnosis information will now be uploaded to http://ix.io/1b8J

 

 

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         gateway         0.0.0.0         UG    100    0        0 eth0
link-local      *               255.255.0.0     U     1000   0        0 eth0
192.168.1.0     *               255.255.255.0   U     100    0        0 eth0
 

Link to comment
Share on other sites

after lost eth0 and switch to wlan0.:

ifconfig
eth0      Link encap:Ethernet  HWaddr c2:2d:dc:69:09:b8  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6805 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4405 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:7294757 (7.2 MB)  TX bytes:1189808 (1.1 MB)
          Interrupt:17 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:463 errors:0 dropped:0 overruns:0 frame:0
          TX packets:463 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:34169 (34.1 KB)  TX bytes:34169 (34.1 KB)

wlan0     Link encap:Ethernet  HWaddr b0:f1:ec:29:d5:5a  
          inet addr:192.168.1.17  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::bc1b:678c:a64a:b67c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3080 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2584 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3017837 (3.0 MB)  TX bytes:973929 (973.9 KB)
 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines