-
Notifications
You must be signed in to change notification settings - Fork 8
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
Utilize RPi throttled state to provide more information #209
Comments
Related: balena-os/balena-raspberrypi#485 |
This comment has some nice CLI math to parse the output of |
saintaardvark
pushed a commit
that referenced
this issue
May 28, 2020
This adds two checks that take different approaches to detecting CPU throttling: - check_throttling_dmesg examines dmesg output for throttling events - check_throttling_vcgencmd examines the output of the Raspberry Pi utility `vcgencmd` to determine if throttling is currently happening, or has occurred in the past. Connects-to: #183, #209 Change-type: minor Signed-off-by: Hugh Brown <[email protected]>
saintaardvark
pushed a commit
that referenced
this issue
May 28, 2020
This adds two checks that take different approaches to detecting CPU throttling: - check_throttling_dmesg examines dmesg output for throttling events - check_throttling_vcgencmd examines the output of the Raspberry Pi utility `vcgencmd` to determine if throttling is currently happening, or has occurred in the past. Connects-to: #183, #209 Change-type: minor Signed-off-by: Hugh Brown <[email protected]>
saintaardvark
pushed a commit
that referenced
this issue
May 29, 2020
This adds two checks that take different approaches to detecting CPU throttling: - test_throttling_dmesg examines dmesg output for throttling events - test_throttling_vcgencmd examines the output of the Raspberry Pi utility `vcgencmd` to determine if throttling is currently happening, or has occurred in the past. These are both called by check_throttling, which glues the output of both together. Connects-to: #183, #209 Change-type: minor Signed-off-by: Hugh Brown <[email protected]>
saintaardvark
pushed a commit
that referenced
this issue
Jun 1, 2020
This adds two checks that take different approaches to detecting CPU throttling: - test_throttling_dmesg examines dmesg output for throttling events - test_throttling_vcgencmd examines the output of the Raspberry Pi utility `vcgencmd` to determine if throttling is currently happening, or has occurred in the past. These are both called by check_throttling, which glues the output of both together. Connects-to: #183, #209 Change-type: minor Signed-off-by: Hugh Brown <[email protected]>
saintaardvark
pushed a commit
that referenced
this issue
Jun 1, 2020
This adds two checks that take different approaches to detecting CPU throttling: - test_throttling_dmesg examines dmesg output for throttling events - test_throttling_vcgencmd examines the output of the Raspberry Pi utility `vcgencmd` to determine if throttling is currently happening, or has occurred in the past. These are both called by check_throttling, which glues the output of both together. Connects-to: #183, #209 Change-type: minor Signed-off-by: Hugh Brown <[email protected]>
saintaardvark
pushed a commit
that referenced
this issue
Jun 1, 2020
This adds two checks that take different approaches to detecting CPU throttling: - test_throttling_dmesg examines dmesg output for throttling events - test_throttling_vcgencmd examines the output of the Raspberry Pi utility `vcgencmd` to determine if throttling is currently happening, or has occurred in the past. These are both called by check_throttling, which glues the output of both together. Connects-to: #183, #209 Change-type: minor Signed-off-by: Hugh Brown <[email protected]>
saintaardvark
pushed a commit
that referenced
this issue
Jun 2, 2020
This adds two checks that take different approaches to detecting CPU throttling: - test_throttling_dmesg examines dmesg output for throttling events - test_throttling_vcgencmd examines the output of the Raspberry Pi utility `vcgencmd` to determine if throttling is currently happening, or has occurred in the past. These are both called by check_throttling, which glues the output of both together. Connects-to: #183, #209 Change-type: minor Signed-off-by: Hugh Brown <[email protected]>
Closed via #221. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In this issue @ptrm highlights how the Pi VideoCore GPU can be polled to get the status of certain flags, see 'get_throttled' on this page: https://www.raspberrypi.org/documentation/raspbian/applications/vcgencmd.md
Could this be a more reliable way of obtaining status information when compared to looking at kernel error logs?
The text was updated successfully, but these errors were encountered: