Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rising load caused by firmware #46

Closed
ocramleznem opened this issue Apr 30, 2014 · 6 comments

Comments

Projects
None yet
4 participants
@ocramleznem
Copy link

commented Apr 30, 2014

Yesterday I updated from 5c5ed95 to 8643317.
My "idling" load average has gone from 0.02 to 3.1. There are no obviouses processes. A few hours ago I did a downgrade back to 5c5ed95. Now I am back at a load average at about 0.02.
Will provide more nformation if needed.

@popcornmix

This comment has been minimized.

Copy link
Collaborator

commented Apr 30, 2014

Was the CPU low when the load was high?
Can you confirm if:
sudo rpi-update f6eef32dd6388c3b04dbf462bd324d93281bf397
sudo rpi-update b842df82b33d8aafcd6c9be3b6a86cdc2f195ade
have the high or low load?

@ocramleznem

This comment has been minimized.

Copy link
Author

commented Apr 30, 2014

The CPU usage was at about 1%.
#675 f6eef32 is fine. With #676 b842df8 the load is at 3 right after booting. So it should be related to the kernel change.

@popcornmix

This comment has been minimized.

Copy link
Collaborator

commented Apr 30, 2014

It is harmless. If you follow the advice here:
http://www.linuxquestions.org/questions/linux-newbie-8/high-cpu-load-but-low-cpu-usage-high-idle-cpu-902632/
You will see the processes responsible:

   30 root       1 -19     0    0    0 D   0.0  0.0   0:00.00 VCHIQ-0
   31 root       1 -19     0    0    0 D   0.0  0.0   0:00.00 VCHIQr-0
   32 root       0 -20     0    0    0 D   0.0  0.0   0:00.00 VCHIQs-0

These are TASK_UNINTERRUPTIBLE kernel threads that are sleeping. They take no CPU and are doing no harm, but contribute to the load average.

It's a result of this commit:
raspberrypi/linux@9b9d7bb

I'll see if I can find a way of avoiding this.

@ocramleznem

This comment has been minimized.

Copy link
Author

commented May 1, 2014

Thank you for this detailed explanation!
I'll "go back" to the latest revision an be pleased with your great work.

@Jmtyra

This comment has been minimized.

Copy link

commented May 7, 2014

Perhaps a dumb question on my part, but will this be resolved in the next update?

@vrampal

This comment has been minimized.

Copy link

commented May 9, 2014

Same issue here, rolled back using:
sudo rpi-update f6eef32dd6388c3b04dbf462bd324d93281bf397
Could you please give an estimated date for fix ? Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.