• Announcements

    • 1. Check power supply, check SD card and check other people experiences

      Power supply issues are one of the three biggest issues you'll face when starting with Single Board Computers (SBCs). SD card issues, whether fake or faulty, are another and issues resulting from poor board design is the other common issues you can encounter.   Power supply issues can be tricky. You might have a noisy power supply that works with one board because it has extra filtering, but won't work with another. Or you're using that cheap phone charger because your board has a microUSB connector, and it is either erratic, or doesn't start up, or even becomes the cause of some SD card issues.    Some tips to avoid the most common causes of problems reported:   Don't power via micro USB  - unless you have optimised your setup for low power requirements. Micro USB is great for mobile phones because they are simply charging a battery. It's bad for SBCs. Yes, it does work for a lot of people, but it also causes more problems and headaches over time than it is worth, unless you know exactly what you are doing. If you have a barrel jack power connector on your SBC, use it instead! If there is an option for powering via header connections, use that option!
        Don't use mobile phone chargers. They might be convenient and cheap, but this is because they are meant for charging phones, not powering your SBC which has particular power requirements.
        When you are evaluating a power supply, make sure you run some stress tests on your system to ensure that it will not cause issues down the path.   (Micro) SD card issues can be sneaky. They might appear right at the start causing strange boot and login errors, or they might cause problems over time. It is best to run a test on any new SD card you use, to ensure that it really is what it is, and to ensure that isn't faulty. Armbian provides you a simple way to do this   --   armbianmonitor -c /path/to/device/to/test  
    • 2. Make sure to collect and provide all necessary information

      We can only help if you provide quality information for us to work with. All stable images from the download section are tested, most stable upgrades are tested and we have tens of thousands of users. Even with regular and extensive testings, bugs sometimes do slip through. This is a voluntary support service and is unrelated to board makers, and is not obligated to provide you any answers. Repeated asking the same questions because you're not happy with the answers will result in you being ignored.

      Before you post a question, use the forum search as someone else might have already had the same problem and resolved it. And make sure you've read the Armbian documentation. If you still haven't found an answer, make sure you include the following in your post:   1. Logs when you can boot the board: armbianmonitor -u (paste URL to your forum post)   2. If your board does not boot, provide a log from serial console or at least make a picture, where it stops.   3. Describe the problem the best you can and provide all necessary info that we can reproduce the problem. We are not clairvoyant or mind readers. Please describe your setup as best as possible so we know what your operating environment is like.     We will not help in cases you are not using stable official Armbian builds, you have a problem with 3rd party hardware or reported problem would not be able to reproduced.

Le Potato Ethernet Problems
2 2

28 posts in this topic

Recommended Posts

So, I've been struggling to figure out the reason behind this problem.

 

I have 4 Le Potatoes, all connected to a 100 mbps switch. Each of them have a 32 GB Samsung SD Card EVO.

 

Initially, the problem was that my SSH session would hang at random usually when I download something. I can't SSH again unless I reboot the PI (I didn't bother waiting longer than 5min)

 

Initially, I thought SD Cards were bad, I moved them around, done reinstalls. I'm also using SD Formatter to format them and Etcher to install them.

Still, this freezing problem had no consistent behavior according to PI hardware or the SD cards..

 

For Power, I'm using Anker 40W 4-Port USB Wall Charger, which it should (I think) be enough power. I've checked all the cables using my phone to verify.

 

I plugged HDMI into them, and see if they were still running after those SSH crashes. (why didn't I do this earlier) I ssh'd into them and see what happened when the "crash" behavior happened.

 

After SSH hangs, I check the PI, and the computer is still running as usual.

 

I reboot the PI, and I start doing some downloads, and then now I see the network hang I get from ssh. To me it seems like the ethernet driver is crashing or something.

I'm not sure what else to try for debugging / what the problem is.  Send Help.

 

Version: ARMBIAN 5.34.171017 nightly Ubuntu 16.04.3 LTS 4.13.7-meson64
Using Le Potato 2GB Version.

Share this post


Link to post
Share on other sites

to help u look in the documentation section, what these thingy can report.

 

/sent from mobile phone /

Share this post


Link to post
Share on other sites
29 minutes ago, Tido said:

to help u look in the documentation section, what these thingy can report.

 

I think you forgot to link something.

Share this post


Link to post
Share on other sites

I'm not sure this carries over to the s905x from the s905, as the s905x can only officially go 1.5 GHz in the first place.  If he has time, @Neil Armstrong may be able to answer better, I don't know all of the differences between the C2 and K2 GXBB and the Le Potato GXL.

 

I haven't seen this issue on my board, but of course I haven't done too many long-term tests.

 

@NinjaKitty, are you using the latest kernel image?  File download was the simplest way for me to trip the memory fault associated with 

 

The board didn't typically die immediately after the hang, it took some other activity first.  

 

If you can give me the output of armbianmonitor -u maybe the fault left some evidence. 

 

My Le Potato was left 24 hours without incident last night, I will repeat but give it some sort of activities to see if it fails.

Share this post


Link to post
Share on other sites

@TonyMac32

 

I'm on version 4.13, which I downloaded yesterday. From your post, I'm assuming there's a 4.15 version?

 

I'll try to reproduce it (it happened again as I was downloading the python2.7 docker container) and see.

 

Share this post


Link to post
Share on other sites

No, 4.15 doesn't exist yet, I pulled a patch that is scheduled to be included in a future kernel.  I apologize for any confusion. 

 

I've moved multi-GB files with this image, that's the only reason I'm curious.  the armbianmonitor link will provide basic info about the machine and dmesg info if you provide it.

Share this post


Link to post
Share on other sites

http://sprunge.us/ORAj

 

Also, I've noticed with this particular version, static IPs aren't working on boot and I have to do ifdown/ifup to make it work.

 

It used to work fine with the previous versions. I'm not sure what's wrong with that either.

Share this post


Link to post
Share on other sites

Sorry, I should've checked before posting.
ARMBIAN 5.33.171011 nightly Ubuntu 16.04.3 LTS 4.13.5-meson64

 

Currently, I'm on 4.13.7-meson64

Share this post


Link to post
Share on other sites

### Group membership of dan : dan dialout sudo audio video plugdev systemd-journal netdev bluetooth docker

 

Was docker installed at the same time the issues appeared?

 

21.620963] docker_gwbridge: port 1(vethe7075d6) entered forwarding state [ 21.621367] docker_gwbridge: port 1(vethe7075d6) entered disabled state [ 21.797479]

eth1: renamed from vethc6ce16b

 

I have not tried Docker on this image, @Igor    could this be related?

Share this post


Link to post
Share on other sites
15 minutes ago, TonyMac32 said:

I have not tried Docker on this image, @Igor    could this be related?


Neither did I. It could be a Docker (dependencies) related issue. Unfortunately, I am not in deep familiar with possible troubles.

Share this post


Link to post
Share on other sites

I've ran into this problem a few times without docker for things like sudo apt-get update, but most of the time that I've ran into this was something involved with docker. Either running the get.docker script, installing docker, or downloading a container (i.e. python2.7-slim). I can test later today and see if other workloads cause this to happen.

Share this post


Link to post
Share on other sites

Did you comile your own kernel? Just asking as I had similar issues when compiling a custom kernel with any other CPU frequency governor than Performance. This is how it should be:

$ gunzip -c /proc/config.gz | grep CPU_FREQ_GOV
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_GOV_POWERSAVE is not set
# CONFIG_CPU_FREQ_GOV_USERSPACE is not set
# CONFIG_CPU_FREQ_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_GOV_CONSERVATIVE is not set
# CONFIG_CPU_FREQ_GOV_SCHEDUTIL is not set

 

Share this post


Link to post
Share on other sites

@V10lator Nope, just downloaded from armbian's site.

 

Mine looks like this

 

CONFIG_CPU_FREQ_GOV_ATTR_SET=y
CONFIG_CPU_FREQ_GOV_COMMON=y
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=m
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m
CONFIG_CPU_FREQ_GOV_SCHEDUTIL=y

 

Share this post


Link to post
Share on other sites

I'm going to uninstall docker-ce and just use them and see if I still crash.

 

For my other question of not being able to access the internet on boot, am I doing something wrong here?

 

/etc/network/interfaces

# Wired adapter #1
allow-hotplug eth0
no-auto-down eth0
iface eth0 inet static
    address 192.168.5.200
    netmask 255.255.255.0
    gateway 192.168.5.6
    dns-nameservers 8.8.8.8 192.168.5.6

 

For more context,

 

I have it setup to static IP, but every time on boot, i have to do sudo ifdown eth0; sudo ifup eth0 every single time to get internet access. I can SSH it just fine, and I can ping 8.8.8.8, but I can't resolve any hostnames like nslookup google.com

 

Edit: I uninstalled docker-ce and so far, it hasn't crashed. I've done some stress tests, iperfs, and it seems to be working fine... Will keep checking. Maybe something wrong with docker with amlogic?

Share this post


Link to post
Share on other sites
4 hours ago, NinjaKitty said:

Mine looks like this


CONFIG_CPU_FREQ_GOV_ATTR_SET=y
CONFIG_CPU_FREQ_GOV_COMMON=y
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=m
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m
CONFIG_CPU_FREQ_GOV_SCHEDUTIL=y

 

That's weird and might be why you see these errors. Could you check the outut of cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor and if it says anything other than performance do sudo echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor (please note that this setting won't survive a reboot) and then redo your testing?

BTW: Is wget https://git.kernel.org/torvalds/t/linux-4.14-rc5.tar.gz a good way to reproduce the issue for you?
 

 

1 hour ago, NinjaKitty said:

For my other question of not being able to access the internet on boot, am I doing something wrong here?

What's ifconfig and cat /etc/resolv.conf telling before and after you do ifdown/ifup?

Share this post


Link to post
Share on other sites
9 hours ago, V10lator said:

That's weird and might be why you see these errors. Could you check the outut of cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor and if it says anything other than performance do sudo echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor (please note that this setting won't survive a reboot) and then redo your testing?

BTW: Is wget https://git.kernel.org/torvalds/t/linux-4.14-rc5.tar.gz a good way to reproduce the issue for you?

 

1) cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor returns ondemand

2) I'll do some testing when I get back home from work.

3) I just did the wget command, and it works fine (didn't change scaling_governor)

4) I'll try changing scaling_governor to performance and then reinstall docker-ce, and then redo the same stuff I was doing before.

Share this post


Link to post
Share on other sites
On 10/19/2017 at 11:33 PM, V10lator said:

What's ifconfig and cat /etc/resolv.conf telling before and after you do ifdown/ifup?

Before:

eth0      Link encap:Ethernet  HWaddr 8e:fc:0c:bb:94:16
          inet addr:192.168.5.200  Bcast:192.168.5.255  Mask:255.255.255.0
          inet6 addr: fe80::8cfc:cff:febb:9416/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:86915 errors:0 dropped:42 overruns:0 frame:0
          TX packets:658 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:13818114 (13.8 MB)  TX bytes:88602 (88.6 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:116878 errors:0 dropped:0 overruns:0 frame:0
          TX packets:116878 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:9303074 (9.3 MB)  TX bytes:9303074 (9.3 MB)

 

After

 

eth0      Link encap:Ethernet  HWaddr 8e:fc:0c:bb:94:16
          inet addr:192.168.5.200  Bcast:192.168.5.255  Mask:255.255.255.0
          inet6 addr: fe80::8cfc:cff:febb:9416/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:87076 errors:0 dropped:42 overruns:0 frame:0
          TX packets:731 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:13833694 (13.8 MB)  TX bytes:96799 (96.7 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:116962 errors:0 dropped:0 overruns:0 frame:0
          TX packets:116962 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:9309598 (9.3 MB)  TX bytes:9309598 (9.3 MB)

 

Share this post


Link to post
Share on other sites

I changed /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor to performance

 

I did curl https://get.docker.com | sh 

 

dan@lepotato1:~$ curl  https://get.docker.com | sh
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 11070  100 11070    0     0  13792      0 --:--:-- --:--:-- --:--:-- 13785
# Executing docker install script, commit: 49ee7c1
+ sudo -E sh -c apt-get update -qq >/dev/null
+ sudo -E sh -c apt-get install -y -qq apt-transport-https ca-certificates curl software-properties-common >/dev/null
+ sudo -E sh -c curl -fsSL "https://download.docker.com/linux/ubuntu/gpg" | apt-key add -qq - >/dev/null
+ sudo -E sh -c echo "deb [arch=arm64] https://download.docker.com/linux/ubuntu xenial edge" > /etc/apt/sources.list.d/docker.list
+ [ ubuntu = debian ]
+ sudo -E sh -c apt-get update -qq >/dev/null
+ sudo -E sh -c apt-get install -y -qq --no-install-recommends docker-ce >/dev/null
E: Failed to fetch https://download.docker.com/linux/ubuntu/dists/xenial/pool/edge/arm64/docker-ce_17.10.0~ce-0~ubuntu_arm64.deb  Operation too slow. Less than 10 bytes/sec transferred the last 120 seconds

E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Immediately after this, SSH hangs and becomes unaccessible. 

 

I went onto the computer directly, reset the ethernet, and did armbianmonitor -u. (Ethernet was dead and couldn't do apt-get update)

 

http://sprunge.us/EFfg

Share this post


Link to post
Share on other sites

I have the Libre Le Potato, running the Armbian Ubuntu image [Ubunutu desktop - mainline kernel] from the download page. 2GB model, exactly as the OP has above. I see the same issue - ethernet connectivity reliably just stops after about 15 minutes or so of use, just running turbovncserver and one remote session, nothing too strenuous.

 

Apart from that, it's a wonderful little board and Armbian on it is really excellent.

 

So, just adding more weight to this observation by others.

 

Share this post


Link to post
Share on other sites

Thanks @Andro for the report, and @Da Xue for the information.

 

I've now observed the same thing, however in my case it takes up to a day to appear, although admittedly I'm not doing server activities (I set the device up to stream an entire Youtube channel, which it did successfully overnight, setting it up where I would ping it periodically eventually *seems* to have knocked it out)  It seems as though incoming requests may be to blame, rather than outgoing traffic?  I'll set up a server with it and see how differently that behaves.

Share this post


Link to post
Share on other sites

Hi @TonyMac32 now confirming that I can indeed confirm that a constant stream of inbound traffic causes the ethernet to lock up after 15 minutes to an hour or so. This test is repeatable and reliable.

 

As to how to provide logs or any further detail, I don't really know.

 

Share this post


Link to post
Share on other sites

Alright, Da Xue says Amlogic is looking into it, I'll build another image and see if I can get your results.  (I am not doubting you, I'm just curious why I'm seeing a different behavior)

Share this post


Link to post
Share on other sites

I built the latest 5.34 Armbian image for the Le Potato and it still locks up after about an hour or so of ethernet traffic (using turbovnc), rendering this very nice little board unusable. I see others confirming the problem, but are there any people able to run this board successfully? A bit of a puzzle.

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

2 2

  • Support the project

    We need your help to stay focused on the project.

    Choose the amount and currency you would like to donate in below.