XU4 CPU speed reporting

Having issues with your DietPi installation, or, found a bug? Post it here.
Post Reply
User avatar
johnvick
Legend
Posts: 693
Joined: Wed Jun 08, 2016 11:53 am
Location: New Zealand

XU4 CPU speed reporting

Post by johnvick »

Did apt-get upgrade tonight and there was a new kernel - same version number.

root@odroid:~# uname -a
Linux odroid 3.10.104+ #1 SMP PREEMPT Tue Feb 21 14:20:54 CET 2017 armv7l GNU/Linux

Since installing this I cannot get CPU cores 0-4 to go above 200 no matter what governor settings I select.

Trying to max out the CPU with 265 - 264 video transcoding - same.

Any ideas? Is is possible to revert to the previous version?

John

EDIT - due to another problem restored from backup but still interested in how this could be done.
User avatar
Fourdee
Site Admin
Posts: 2787
Joined: Tue Feb 06, 2007 1:36 pm

Re: XU4 CPU speed reporting

Post by Fourdee »

johnvick wrote:Since installing this I cannot get CPU cores 0-4 to go above 200 no matter what governor settings I select.
Hi John,

I just updated kernel, 0-4 cores seems fine for me:

Code: Select all

root@DietPi:~# cpu

 ─────────────────────────────────────────────────────
 DietPi CPU Info
 Use dietpi-config to change CPU / performance options
 ─────────────────────────────────────────────────────
 Architecture |     armv7l
 Temp         |     48'c | Optimal temperature.
 Governor     |     ondemand
 Throttle up  |     50% CPU usage

                 Current Freq    Min Freq   Max Freq
 CPU0         |      1400 Mhz      200 Mhz    1400 Mhz
 CPU1         |      1400 Mhz      200 Mhz    1400 Mhz
 CPU2         |      1400 Mhz      200 Mhz    1400 Mhz
 CPU3         |      1400 Mhz      200 Mhz    1400 Mhz
 CPU4         |      1500 Mhz      200 Mhz    1500 Mhz
 CPU5         |      1500 Mhz      200 Mhz    1500 Mhz
 CPU6         |      1500 Mhz      200 Mhz    1500 Mhz
 CPU7         |      1500 Mhz      200 Mhz    1500 Mhz

root@DietPi:~# uname -a
Linux DietPi 3.10.104+ #1 SMP PREEMPT Tue Feb 21 14:20:54 CET 2017 armv7l GNU/Linux
Is your kernel date same as above? (uname -a)
If you find our project or support useful, then we’d really appreciate it if you’d consider contributing to the project however you can.
Donating is the easiest – you can use PayPal or become a DietPi patron.
User avatar
johnvick
Legend
Posts: 693
Joined: Wed Jun 08, 2016 11:53 am
Location: New Zealand

Re: XU4 CPU speed reporting

Post by johnvick »

Hi Fourdee,

Given that I did a restore I no longer have that kernel on the system - that date was what uname -a said.

John
User avatar
Fourdee
Site Admin
Posts: 2787
Joined: Tue Feb 06, 2007 1:36 pm

Re: XU4 CPU speed reporting

Post by Fourdee »

johnvick wrote:Hi Fourdee,

Given that I did a restore I no longer have that kernel on the system - that date was what uname -a said.

John
Hi John,

Ah ok. Although I am limiting cores to 1.5GHz max, shouldn't have any effect on scaling.

If you update the kernel again, lets check scaling for CPU 0 (1.4GHz):

Code: Select all

cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
You should get something similar to:

Code: Select all

root@DietPi:~# cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
1400000 279572
1300000 13
1200000 0
1100000 0
1000000 0
900000 0
800000 0
700000 4521
600000 10441
500000 13187
400000 14689
300000 13721
200000 1109614
If you find our project or support useful, then we’d really appreciate it if you’d consider contributing to the project however you can.
Donating is the easiest – you can use PayPal or become a DietPi patron.
User avatar
johnvick
Legend
Posts: 693
Joined: Wed Jun 08, 2016 11:53 am
Location: New Zealand

Re: XU4 CPU speed reporting

Post by johnvick »

Hi Fourdee,

Incidentally - I restored the system by copying over boot folder from the backup made earlier that evening. I am using v144.

When I rebooted it thought I was on v141 and suggested update to v144 which I did and all is working.

Why is this?

John
User avatar
Fourdee
Site Admin
Posts: 2787
Joined: Tue Feb 06, 2007 1:36 pm

Re: XU4 CPU speed reporting

Post by Fourdee »

johnvick wrote:Hi Fourdee,

Incidentally - I restored the system by copying over boot folder from the backup made earlier that evening. I am using v144.

When I rebooted it thought I was on v141 and suggested update to v144 which I did and all is working.

Why is this?

John
Hi John,

When powering down system, DietPi-RAMdisk will overwrite /boot/dietpi with /DietPi/dietpi.
When doing a manual restore to /boot, also copy the files from /boot/dietpi to /DietPi/dietpi.

And

/boot/dietpi.txt > /DietPi/dietpi.txt
/boot/config.txt > /DietPi/config.txt
Post Reply