You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
In bookworm, putting avoid_warnings=2 in /boot/config.txt does not prevent throttling due to undervoltage from occurring.
To reproduce
Install bookworm.
Put avoid_warnings=2 in /boot/config.txt.
Use a shoddy power supply.
Observe many messages like [Fri Oct 20 23:36:15 2023] hwmon hwmon1: Undervoltage detected! in dmesg -T output
Furthermore, observe that the output of vcgencmd get_throttled indicates throttling has occurred due to undervoltage
Expected behaviour
When running with avoid_warnings=2, there should be no undervoltage messages in dmesg, nor should there be throttling occurring due to undervoltage observed via vcgencmd get_throttled.
Actual behaviour
See reproduction steps above.
System
I apologize because I wiped the system before capturing the below diagnostics. But I had just today (2023-10-20) installed the latest 32 bit bookworm lite release with this download URL.
Describe the bug
In bookworm, putting
avoid_warnings=2
in/boot/config.txt
does not prevent throttling due to undervoltage from occurring.To reproduce
avoid_warnings=2
in/boot/config.txt
.[Fri Oct 20 23:36:15 2023] hwmon hwmon1: Undervoltage detected!
indmesg -T
outputvcgencmd get_throttled
indicates throttling has occurred due to undervoltageExpected behaviour
When running with
avoid_warnings=2
, there should be no undervoltage messages indmesg
, nor should there be throttling occurring due to undervoltage observed viavcgencmd get_throttled
.Actual behaviour
See reproduction steps above.
System
I apologize because I wiped the system before capturing the below diagnostics. But I had just today (2023-10-20) installed the latest 32 bit bookworm lite release with this download URL.
4B
cat /etc/rpi-issue
)?vcgencmd version
)?uname -a
)?Logs
Additional context
n/a
The text was updated successfully, but these errors were encountered: