Load is 2.0 on idle VIM3 Focal Linux-4.9

VIM3
#1

Hi, I’m using the new VIM3_Ubuntu-server-focal_Linux-4.9_arm64_EMMC_V0.9-20200530 and I discovered that the load of the idle board is always 2.0 (or greater).

It seems, there are all the time two kernel processes in D state:

ps aux | grep D
USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root        2193  0.0  0.0      0     0 ?        D    15:07   0:00 [videosync]
root        2800  0.0  0.0      0     0 ?        D    15:07   0:00 [isp_process]

I think it is related to the camera. There is no camera connected to my VIM3. How do I disable these?

I tried

sudo systemctl disable camera_isp_3a_server.service
sudo systemctl stop camera_isp_3a_server.service

and rebooted, but it didn’t help.

#2

I could get rid of one of them by blocking camera modules in /etc/modprobe.d/blacklist.conf

blacklist iv009_isp_sensor
blacklist iv009_isp_lens
blacklist iv009_isp_iq
blacklist iv009_isp

The second still stays:

ps aux | grep D
USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root        2193  0.0  0.0      0     0 ?        D    17:41   0:00 [videosync]
#3

I have the same issue with bionic, did the same, removed the camera module and that brought the load to 1.0 , not 0.0 as one would expect when nothing is running.
As of late I had to re-enable the camera driver so the load is back to 2. Must be some bug hogging resources.

#4

Hello @j.fikar

Here is a patch to revert videosync to reduce system load. But I’m not sure whether it will effect video playback. You can try.

Vim3pro v12 usb启动报错
#5

On bionic, there is the following which normally should take almost no cpu on idle:

ps aux | sort -d -r -k 3
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 3.0 0.2 161108 8364 ? Ss Jun15 71:26 /sbin/init
message+ 3253 1.1 0.1 7344 4492 ? Ss Jun15 26:07 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
root 2569 0.7 0.2 36224 10732 ? S<s Jun15 18:20 /lib/systemd/systemd-journald
syslog 3251 0.2 0.1 219972 4688 ? Ssl Jun15 5:57 /usr/sbin/rsyslogd -n
root 3237 0.2 0.1 10408 5204 ? Ss Jun15 6:23 /lib/systemd/systemd-logind
root 24919 0.1 0.0 0 0 ? S 11:46 0:01 [kworker/3:2]

And on > journalctl --no-full -f
you get a continuous stream of this:
Jun 17 12:11:32 core_a systemd[1]: camera_isp_3a_server.service: Service hold-off time over, scheduling restart.
Jun 17 12:11:32 core_a systemd[1]: camera_isp_3a_server.service: Scheduled restart job, restart counter is at 562023.
Jun 17 12:11:32 core_a systemd[1]: Stopped Camera ISP 3A server service.
Jun 17 12:11:32 core_a systemd[1]: Started Camera ISP 3A server service.
Jun 17 12:11:32 core_a systemd[1]: camera_isp_3a_server.service: Service hold-off time over, scheduling restart.
Jun 17 12:11:32 core_a systemd[1]: camera_isp_3a_server.service: Scheduled restart job, restart counter is at 562024.
Jun 17 12:11:32 core_a systemd[1]: Stopped Camera ISP 3A server service.
Jun 17 12:11:32 core_a systemd[1]: Started Camera ISP 3A server service.
Jun 17 12:11:32 core_a systemd[1]: camera_isp_3a_server.service: Service hold-off time over, scheduling restart.
Jun 17 12:11:32 core_a systemd[1]: camera_isp_3a_server.service: Scheduled restart job, restart counter is at 562025.
Jun 17 12:11:32 core_a systemd[1]: Stopped Camera ISP 3A server service.
Jun 17 12:11:32 core_a systemd[1]: Started Camera ISP 3A server service.

#6

On the video sync issue I found there are similar issues with the odroid-n2 as well https://forum.odroid.com/viewtopic.php?f=181&t=37912
For my purpose (and others I guess) I don’t use the video playback at all.

#7

It seems, the patch discussed in Odroid forum is the same as pointed out by numbqq. I’ve tried to apply the patch and compile. The patch does not apply cleanly, but compilation works.

Then I manually replaced the kernel in /boot with the new one, but I think I missed some uboot magic. It does not boot now. What should be done after replacing the kernel image?

#8

Actually my VIM3 was stuck on reboot. After power-cycle it works, the load is 0.0 and no process in D state.

2 Likes