Age | Commit message (Collapse) | Author | Files | Lines |
|
This issue have not occurred since systemd version 239.
This reverts commit 8b9882947cf6e9508eacdf543bd88a07d88f6598.
Signed-off-by: Thuy Tran <thuy.tran.xh@renesas.com>
Signed-off-by: Khang Nguyen <khang.nguyen.xw@renesas.com>
Signed-off-by: Takamitsu Honda <takamitsu.honda.pv@renesas.com>
Change-Id: If9d2cc31cf6dbdfd9a5837ab6017845cde73514d
|
|
In systemd v234, systemd-logind may now be restarted without losing
state, it stores the file descriptors (fd) for devices it manages
in the system manager. [1]
In graphic and multimedia configuration, above feature causes memory
leak with the use case of restarting Weston:
| root@salvator-x:~# cat /proc/meminfo | grep Cma
| CmaTotal: 671744 kB
| CmaFree: 629788 kB
| root@salvator-x:~#
| root@salvator-x:~# systemctl restart weston
| root@salvator-x:~#
| root@salvator-x:~# cat /proc/meminfo | grep Cma
| CmaTotal: 671744 kB
| CmaFree: 599404 kB
Because the system continues allocating memory for the new session
during the previous device fds still open.
This commit avoids saving device fds into the system manager by
setting "FileDescriptorStoreMax=0" [2] in "systemd-logind.service".
[1] https://lists.freedesktop.org/archives/systemd-devel/2017-July/039308.html
[2] https://www.freedesktop.org/software/systemd/man/systemd.service.html#FileDescriptorStoreMax=
Signed-off-by: Khang Nguyen <khang.nguyen.xv@rvc.renesas.com>
Signed-off-by: Takamitsu Honda <takamitsu.honda.pv@renesas.com>
|
|
This fix is not necessary for rocko branch.
Hence, we can remove it.
This reverts commit d6eff077c4a3afbe39f8ee1b2ad1a19a716ce31c.
Signed-off-by: Thuy Tran <thuy.tran.xh@rvc.renesas.com>
Signed-off-by: Takamitsu Honda <takamitsu.honda.pv@renesas.com>
|
|
This commit makes backporting changes from upstream systemd to fix
timeout dev-ttySN.device by following:
[systemd]
- Set journal RuntimeMaxSize to 64M as default [1]
[systemd-serialgetty]
- Use the default RestartSec [2]
[1] From Poky rev: d41968d8a8bd572b2892762f7092868950465014
[2] From Systemd rev: 4bf04322b8b7ecca4f3d65cfc642d0ac16356129
Signed-off-by: Thuy Tran <thuy.tran.xh@rvc.renesas.com>
Signed-off-by: Takamitsu Honda <takamitsu.honda.pv@renesas.com>
|
|
Renesas BSP v3.5.1 (kernel v4.9 stable)
[Environment]
poky: yocto-2.1.2 (cca8dd15c8096626052f6d8d25ff1e9a606104a3)
meta-openembedded: 55c8a76da5dc099a7bc3838495c672140cedb78e
meta-linaro: 2f51d38048599d9878f149d6d15539fb97603f8f
[Information]
- U-boot: Changed load address from H'49000000 to H'50000000
- XDG_RUNTIME_DIR has been changed from "/run/user/root" to "/run/user/0"
- Change location of include directory, which stores common user header
files, to $(INCSHARED)
- In BSP Only, core-image-weston is not supported even though
local-wayland.conf is provided.
- Please set Salvator-x SW7 Pin-1. In after Yocto BSP v2.12.0, it is
 necessary to enable BKUP_TRG signal for Suspend to RAM.
- The dtb filename was changed in R-Car H3. Only
"Image-r8a7795-es1-salvator-x.dtb" is supported in this version.
Please use "Image-r8a7795-es1-salvator-x.dtb" It supports R-Car H3
WS1.0 and WS1.1.
- Please update your local.conf and bblayers.conf corresponding to Yocto
v2.16.0 package. You can refer to meta-rcargen3/docs/sample/conf/ for
updated contents.
- You have to re-compile out-of-recipe software like user application by
v2.16.0 SDK toolchains.
- In some boards, the resuming from System Suspend to RAM may cause
unstable operation or failed to resume.
Signed-off-by: Takamitsu Honda <takamitsu.honda.pv@renesas.com>
|