Avnet SmartEdge IoT Gateway - cgroup memory

It depends on what release you have stopje . https://github.com/raspberrypi/linux/commit/ba742b52e5099b3ed964e78f227dc96460b5cdc0  explains the confusion. Please post the release from:

uname -a

uname -a gives:

Linux raspberrypi 4.14.79-v7+ #91 SMP Tue Jul 16 05:42:32 PDT 2019 armv7l GNU/Linux

I used both  cgroup_enable=memory  and  cgroup_memory=1 but unfortunatelly  it still didn't work. Might it be related to some avnet modifications?

Here is all the details cgroups(7) - Linux manual page .

• the availability  of the cgroups feature is governed by the CONFIG_CGROUPS kernel con‐

  figuration option. So maybe it was not built with this!

• Linux cgroup started version 2 in Linux 4.5. Since you are not there yet, an upgrade or newer version may help.
• Check docker for which you need. Version 1 may be OK! Or not.
• Can you use standard Rasbian?

https://medium.com/@kasunmaduraeng/docker-namespace-and-cgroups-dece27c209c7  A good read...

systemd-cgls <== to check if used and available

Thank you,

I cannot use standard Raspbian directly as Avnet added some extra layers. Will try to modify their build.

It is not for docker but for AWS IoT greengrass. I use it on other devices and now I am playing with the Avnet SmartEdge IoT Gateway.

Oh I never heard of greengrass until now. But in looking at an overview, I found this statement for 1.10:

A new Greengrass Docker application deployment connector that runs a Docker application on a core device. For more information, see Docker Application Deployment Connector.

That reference implies usage of docker under the covers.

Greengrass is great technology, anyway it is independent from docker but they released version that can be run inside container as well.

I found interesting thing.

my cmdline.txt look like this:

cat /boot/cmdline.txt

dwc_otg.lpm_enable=0 console=tty1 rootfstype=ext4 rootwait console=serial0,115200 root=/dev/mmcblk0p2 fsck.repair=yes cgroup_enable=memory cgroup_memory=1 elevator=deadline

but

dmesg | grep Kernel

shows:

[    0.000000] Kernel command line: dwc_otg.lpm_enable=0 console=tty1 rootfstype=ext4 rootwait root=/dev/mmcblk0p2 fsck.repair=yes elevator=deadline

I am confused. From where is it coming?

stopje

Well, I think I found the problem: the one who parses cmdline.txt does not like empty lines before the valid cmdline: I have that:

# comment 
# <previous cmmdline line commented out>
  
# comment 
<new cmdline> 

changing it to:

# comment 
# <previous cmmdline line commented out> 
# comment 
<new cmdline> 

makes it work.

Be careful of newline characters as they are trouble too.

Also it is /boot/cmdline.txt.

So, I would test things by adding

disable_splash=1

and looking at

dmesg | grep Kernel

like before. This will stop the multi color splash screen...

Clem

clem57 my cmdline.txt is absolutely one liner. Single space between entries. I stumbled upon the other post

But mistery is solved. They use custom bootloader https://github.com/Avnet/smartedge-iiot-gateway-uboot

and treadme states:

Note:

We do not process cmdline.txt so if you need to change it then edit .config file entry BOOTCOMMAND=.

So now I need to follow their instruction and hopefully it will work.

Thanks for guidance on other steps.

BR,

Jerzy