>From the command line...  Do note that I log in over X so nothing gets plugged in or removed from the USB ports.    
  
1.  dmesg should be pretty clean.  Those times on the left are in seconds since boot.  
  
[   23.088460] Bluetooth: BNEP (Ethernet Emulation) ver 1.3  


[   23.088467] Bluetooth: BNEP filters: protocol multicast  


[   23.088479] Bluetooth: BNEP socket layer initialized  


[   23.124540] Bluetooth: RFCOMM TTY layer initialized  


[   23.124559] Bluetooth: RFCOMM socket layer initialized  


[   23.124577] Bluetooth: RFCOMM ver 1.11  


 10:54:29 up 18 days, 15:37,  1 user,  load average: 0.00, 0.00, 0.00  


  
  
2. Mine is not throttling now but my memory is that one of the following commands will give you some lines  
  
sudo zgrep -i throt  /var/log/messages*.gz  


sudo zgrep -i throt  /var/log/syslog*.gz  


  
3.  There is a vcgencmd get_throttled  
  
[http://raspberrypi.stackexchange.com/questions/83184/ddg#83185](http://raspberrypi.stackexchange.com/questions/83184/ddg#83185)  
  
vcgencmd is an interesting command for many of these sorts of things.  You can measure the CPU and GPU temp.  
  
cheers  
  
bruce  

> > On 2020-10-02, at 3:14 PM, Eliot Miranda wrote:  
>  >  
>  > So two questions, a) is there a way from software or GUI to find out if the pi is throttling? b) is there a way from software or GUI to find out if the input voltage is dripping  
>   
>  There is existence proof of this in that the menubar has a widget (in Raspbian, at least) that shows the cpu temperature and changes color when it is throttling. I'm making a possibly naive assumption that it actually tells the truth.  
>   
>  >  
>  > oh, and c) how did you debug this?  
>   
>  Oh, the usual way; curse, swear, try ludicrous ideas that make no sense just moments later. Since I have two Pi4, one with an SSD and one without I was able to swap the SSD out and try the uSD to see if it was anything to do with that. I ran an eeprom state updater/checker (remember, unlike the earlier models the Pi 4 has a chunk of eeprom for the hardware boot code) and showed that they were claimed identical. I made sure to run the exact same vm/image on both.  
>   
>  Eventually the Pi told me what the problem was itself - a widget I'd never seen before appeared saying 'voltage low. check your power supply'. Well, yes, there you go. I'd not previously considered that throttling was caused by anything other than temperature and was in the middle of writing a post to the Pi forums to ask why the problem Pi was indicating throttled when it was only at 30C, whereas the other was happy up to 50C with no throttling. Lesson learned.  
>  Luckily I had another suitable PSU on my desk awaiting a case build for the other Pi 4 so I had one to swap in.  
>   
>  All in all, just like debugging an errant Cog. But swearier.  
>   
>   
>  tim  
>  --  
>  tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim  
>  Java: the best argument for Smalltalk since C++
  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20201003/5ed7cc55/attachment.html>