MichaIng / DietPi

Lightweight justice for your single-board computer!
https://dietpi.com/
GNU General Public License v2.0
4.9k stars 499 forks source link

OrangePI 5+ error after kernel update to 24.11.0-trunk-dietpi1 (cgroup: fork rejected by pids controller...) #7237

Closed ctraber closed 1 month ago

ctraber commented 1 month ago

Creating a bug report/issue

Required Information

After update to new kernel packages: armbian-firmware 24.11.0-trunk-dietpi1 linux-dtb-vendor-rk35xx 24.11.0-trunk-dietpi1 linux-image-vendor-rk35xx 24.11.0-trunk-dietpi1

k3s cannot start additional processes. dmesg e.g.: cgroup: fork rejected by pids controller in /kubepods.slice/kubepods-burstable.slice/kubepods-burstable-podf03920d0_4917_430d_a15e_a25e63ff86bb.slice/cri-containerd-b2a0a20a1bf54f3630971193120d6f66f096cbbe447ae006c519bb35bad2ab97.scope

downgrade to 24.8.0 solved the problem.

MichaIng commented 1 month ago

For now I took the kernel off the repository, since it broke booting from NVMe SSD as well. Will start to investigate for next release.

ctraber commented 1 month ago

Booting from NVMe worked without problem here.

MichaIng commented 1 month ago

There is a bug in the latest vendor kernel sources which breaks NVMe boot on Orange Pi 5 and 5 Plus, not sure whether this one is related. Armbian however also froze the kernel to 24.8 for those two SBCs (and some others): https://github.com/armbian/build/commit/edbf678

So we did the same, monitoring the freeze at Armbian. Sadly, the original commit was done without any comment, and also subsequent commits did not explain why it is actually frozen. So not sure about the underlying issue. Armbian's vendor kernel sources for RK3588 are based on Radxa sources, so either ROCK 5 family will work fine, but commits they do on top of the base source from Rockchip can theoretically always break (features on) any other RK3588 board. Mainline kernel would enhance the situation, but it still lacks a lot of features.

I'll close the issue, and as fast as Armbian unfreezes the kernel for these boards, we'll provide a package for testing, and provide it via APT in case it does not cause the two known issues (NVMe boot and K3s/cgroups).