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

Elevated CPU temps and utilisation following 1.4.2 update on Pi 4 4GB #3685

Closed
morphias2004 opened this issue Aug 9, 2020 · 4 comments
Closed
Labels
bug Issue describes a bug triage This issue needs triage unreproduced No reproduction in a dev setting yet, further analysis blocked by that

Comments

@morphias2004
Copy link

morphias2004 commented Aug 9, 2020

What were you doing?

Upgraded to 1.4.2 from 1.4.0

What did you expect to happen?

Improved functionality, etc

What happened instead?

Raspberry Pi4 CPU temps now consistently ~15 degree celcius higher. CPU usage at idle is around double as well. Was typically 6% when idle, but now site at 12-15%. Temps used to site around 54C doing a print, now sits at 69-71C whilst doing nothing.

Running a Pi4 Model B Rev 1.2 4GB

Did the same happen when running OctoPrint in safe mode?

Yes. Does drop the temp about 4C when doing nothing.

Version of OctoPrint

1.4.2

Operating System running OctoPrint

OctoPi 0.17.0

Printer model & used firmware incl. version

Pusa i3 MK3S

Browser and version of browser, operating system running browser

Windows 10 x64
Chrome 84.0.4147.105 x64

Link to octoprint.log

https://github.com/morphias2004/Octoprint-Logs

Link to contents of terminal tab or serial.log

https://github.com/morphias2004/Octoprint-Logs

Link to contents of Javascript console in the browser

https://github.com/morphias2004/Octoprint-Logs

Screenshot(s)/video(s) showing the problem:

I note when running a 'top' on the pi, kworker/u8:3-brcmf_wq/mmc1:0001:1 is generally at the top around 15% CPU.

I've uploaded a number of screen captures.

https://github.com/morphias2004/Octoprint-Logs

CPU Temp
pi TOP

I have read the FAQ.

YES

@GitIssueBot GitIssueBot added the triage This issue needs triage label Aug 9, 2020
@Boerner1337
Copy link

I am running a Pi 3 B+ model and don't see this issue with 1.4.2

grafik

My CPU load is somewhere between 4% and 7% while printing. Also did not notice any changes in temps.

Greetings,
Kev

@foosel
Copy link
Member

foosel commented Aug 10, 2020

I cannot report any kind of abnormal CPU load either, nor increased kworker usage.

image

This is from an idle system connected to a printer. Can't do test prints right now or my office will reach melting temperatures even with AC, but I didn't notice anything during RC phase either (and I was on the lookout since the first RC did have a CPU usage issues on the octoprint process).

kworker/u8:3-brcmf_wq/mmc1:0001:1 is part of the kernel, not OctoPrint itself. I'm pretty sure that's actually the wlan driver and it's related to data transfers going over the wifi interface (that looks mightily familiar from my time debugging the performance issues observed on the 0w on bandwidth usage of any kind). Is this with the webcam active? Any changes when disabling octodash?

@foosel foosel added the unreproduced No reproduction in a dev setting yet, further analysis blocked by that label Aug 10, 2020
@morphias2004
Copy link
Author

Thanks for coming back to me so quickly. I am a new to the whole 'Pi' experience, so I appreciate everyone's patience and support. 😄

The printer and Pi have been powered off completely for 36hrs. I just fired the Pi up after seeing the replies to this and the CPU is sitting around 47-50C. I've then installed the Resource Monitor plugin so I could see more of what was going on - awesome plugin BTW! 👍

After about 10mins, the temp was still stable at 47-48C.

I then powered on the printer to get OctoDash to wake up and have not seen any increase in temp or CPU utilization.

What I did notice in Resource Monitor was constant WLAN traffic upload of ~43MB/s. I quickly realised that was the webcam. The camera is streaming 1920x1080 @ 15FPS, so the traffic is expected. I unplugged it to see what difference it made.

Here is the stats without the webcam - CPU drops to about 3-4%:

No webcam
No webcam 2

And with the webcam - CPU at 7-12% and temps stabilised at ~54C, which is where it was prior to the update:

With webcam
With webcam 2

My guess is that the system just needed a full power cycle following the update - the good old "Have you tried turning it off and on again?" 🤷 No amount of rebooting or restarting from the menus got it to clear the other day.

Anyway, I'm happy to have this one closed out and thank-you again for coming back to me so quickly. 👍

@foosel
Copy link
Member

foosel commented Aug 10, 2020

Perfect, closing this then. Glad it cleared up, thanks for the pleasant interaction!

@foosel foosel closed this as completed Aug 10, 2020
@foosel foosel added the bug Issue describes a bug label Oct 8, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 10, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue describes a bug triage This issue needs triage unreproduced No reproduction in a dev setting yet, further analysis blocked by that
Projects
None yet
Development

No branches or pull requests

4 participants