My guess would be something has killed the firmware.
In this state you'll probably find things likedon't respond.
Reason for this to happen?
Too high an overclock
Inadequate power supply
Sending invalid messages (less likely on the pi5 where firmware does a lot less).
Corrupting firmware's memory (would likely need sudo/mmap to be allowed to do this outside of kernel)
Faulty hardware
Can you identify if the failure correlates with doing "something" (a specific application, or using specific hardware)?
Can you check "vcgencmd get_throttled" is always zero? (this may not work after the dmesg failure, but run it periodically before the failure)
In this state you'll probably find things like
Code:
vcgencmd versionReason for this to happen?
Too high an overclock
Inadequate power supply
Sending invalid messages (less likely on the pi5 where firmware does a lot less).
Corrupting firmware's memory (would likely need sudo/mmap to be allowed to do this outside of kernel)
Faulty hardware
Can you identify if the failure correlates with doing "something" (a specific application, or using specific hardware)?
Can you check "vcgencmd get_throttled" is always zero? (this may not work after the dmesg failure, but run it periodically before the failure)
Statistics: Posted by dom — Tue Feb 20, 2024 6:49 pm
