Errors and overheating on fresh Picroft install

Hi,

I downloaded Picroft yesterday and flashed it to a micro-SD card using the recommended Etcher application. On first boot it was almost working, except some skills seemed not to be registered (so when I asked “what is the time” or “what is the weather” I would get an answer like a dictionary definition of those terms, rather than the expected timecheck or weather forecast).

I installed system-skill (via a voice command) and rebooted. That seems to have fixed the skills not being registered issue. However, now when I reboot (tried it a few times) the scrolling bootup messages get stuck on this for a while (perhaps a couple of minutes):

====================================
Mycroft Core Version: 0.9.10
====================================
Starting up services
Failed to restart mycroft-wifi-setup-client.service: Unit mycroft-wifi-setup-client.service failedd to load: No such file or directory.

After it has sat on that for a while, this message is displayed:

Job for mycroft-enclosure-client.service failed. See 'systemctl status mycroft-enclosure-client.service' and 'journalctl -xn' for details.

It does then seem to work. It has a log displayed, which shows me what is going on. It seems to pretty quickly and accurately get a transcription of my utterances; there is then a delay of a couple of seconds before anything happens.

I also found that with the official Raspberry Pi case, I kept getting a red thermometer sign popping up in the top right corner of the screen. I presume this means that it is running over temperature. I have popped the lid off the case, hoping to improve air-flow around the Raspberry Pi, and that seems to stop the thermometer from appearing. Is it common for Picroft to run hot (including when it’s just passively waiting to be woken)?

I am using the Sony Playstation 3 Eye as the USB mic. It seems to be pretty effective across the room. I have it plugged straight into the R-Pi, not via a hub. I don’t have anything else plugged into the R-Pi’s USB (inc no keyboard or mouse at present). It is currently plugged into my TV for video output.

Could the symbol be indicating low power available? I do know, on the raspberry pi when it’s plugged into a power supply that doesn’t give enough amperage, when anything stresses the CPU a bit, it displays a symbol and lags.

I don’t think it should be power - I’m using the official Raspberry Pi power supply, and only have the Sony PS3 Eye drawing current. And it was resolved by taking the lid off. I think it was the 80-85C warning icon shown on this page:

I saw the same message, that Jim described, on my picroft yesterday. It isn’t a fresh install, possibly is 2 months old. Today I notice that 2 of the processors are running flat on some bash scripts. The first two processes below (929 and 2893) are each hogging a cpu, which may account for some overheating.

Tasks: 146 total,   3 running, 143 sleeping,   0 stopped,   0 zombie
%Cpu0  :  7.7 us,  7.7 sy,  0.0 ni, 84.2 id,  0.0 wa,  0.0 hi,  0.3 si,  0.0 st
%Cpu1  :  8.2 us, 91.8 sy,  0.0 ni,  0.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
%Cpu2  :  8.2 us, 91.8 sy,  0.0 ni,  0.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
%Cpu3  : 53.8 us,  2.3 sy,  0.0 ni, 43.9 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
KiB Mem:    947740 total,   499792 used,   447948 free,    27484 buffers
KiB Swap:   204796 total,        0 used,   204796 free.   265536 cached Mem

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND                                            
  929 root      20   0    4620   2372   2236 R  99.9  0.3  31:03.08 bash                                               
 2893 root      20   0    4620   2312   2176 R  99.5  0.2  29:55.86 bash                                               
 4118 mycroft   20   0  278960  45760  25264 S  57.0  4.8  14:09.67 python2.7                                          
 1923 mycroft   20   0  244624  40056  10696 S   4.6  4.2   2:03.47 python2.7                                          
  931 mycroft   20   0   30532  23372   7540 S   3.9  2.5   1:21.48 python2.7                                          
 4160 mycroft   20   0  101296   7784   6476 S   2.0  0.8   0:29.59 pulseaudio                                         
 7058 pi        20   0    5112   2468   2080 R   1.0  0.3   0:00.28 top                                                
    7 root      20   0       0      0      0 S   0.3  0.0   0:05.91 rcu_sched                                          
  933 mycroft   20   0  188072  31348   8672 S   0.3  3.3   0:16.28 python2.7                                          
    1 root      20   0   23156   4060   2740 S   0.0  0.4   0:07.72 systemd                                            
    2 root      20   0       0      0      0 S   0.0  0.0   0:00.00 kthreadd                                           
    3 root      20   0       0      0      0 S   0.0  0.0   0:00.43 ksoftirqd/0                                        
    5 root       0 -20       0      0      0 S   0.0  0.0   0:00.00 kworker/0:0H                                       
    8 root      20   0       0      0      0 S   0.0  0.0   0:00.00 rcu_bh                                             
    9 root      rt   0       0      0      0 S   0.0  0.0   0:00.03 migration/0                                        
   10 root      rt   0       0      0      0 S   0.0  0.0   0:00.01 migration/1                                        
   11 root      20   0       0      0      0 S   0.0  0.0   0:00.07 ksoftirqd/1                                        
   12 root      20   0       0      0      0 S   0.0  0.0   0:00.07 kworker/1:0                                        
   13 root       0 -20       0      0      0 S   0.0  0.0   0:00.00 kworker/1:0H                                       
   14 root      rt   0       0      0      0 S   0.0  0.0   0:00.01 migration/2                                        
   15 root      20   0       0      0      0 S   0.0  0.0   0:00.14 ksoftirqd/2                                        
   17 root       0 -20       0      0      0 S   0.0  0.0   0:00.00 kworker/2:0H              

Here re details of the two processes:

root       929 99.7  0.2   4620  2372 ?        Rs   05:00  40:50 bash -c /opt/mycroft/enclosure/upload.sh /opt/mycroft/enclosure --skipService
root      2893 99.7  0.2   4620  2312 ?        Rs   05:02  39:41 bash -c /opt/mycroft/enclosure/upload.sh /opt/mycroft/enclosure --skipService

For the time being I have killed them.

I can concur I’m seeing the same process hogging CPU and causing RPi to heat up, seeming to lead to other performance issues. Today is my first day actually experimenting with MyCroft, so this is a brand new fresh install on an RPi 3. I’m attempting to get it working with the Google AIY kit (see my other post). I came upon this thread when I noticed my thermometer showing up in the upper right corner of my HDMI output. htop clearly traced it to a few instances of this process running.

/opt/mycroft/enclosure/upload.sh /opt/mycroft/enclosure --skipService

I killed the processes, but they come back on reboot.

Changes last week in the Mycroft infrastructure haven’t been reflected in the existing Picroft scripts, resulting in the error message about the ‘wifi-setup-client’. This is an known issue we will address in the next couple days.

The bash processes you are referring to, @aussieW, are running the script that does the upload on a Mark 1 to the Arduino over the serial port. I’m surprised to see them running on a Picroft platform. Let me investigate that.

As a quick solution, you should be able to delete the scripts since they aren’t needed for picroft by running sudo rm -rf /opt/mycroft/enclosure/. We are working on putting out a new image to fix this.

Thanks for the updates, @steve.penrod and @Wolfgange.

Do you have an estimated timeline on the new image? (Knowing whether it’s expected this side of Christmas or after would be helpful, in particular.)

And will it auto-update, or is this a ‘reflash your SD card from a fresh image’ situation?

My guess is it will be a new image for the sd card.

ETA on the new RPi is within 24-36 hours, will post here as soon as it’s shipped. Fixing this bug is a priority.
Hold tight for Picroft goodness,

Best, Kathy

1 Like

Any update on progress on this? Or are we looking post-Christmas now?

For anyone using Picroft, we just updated the Picroft platform script. So upon next boot it should notify you that it is updating itself. This will address the issue where you have one or two processes that chew up CPU.

We are still creating a new Picroft system image, but you shouldn’t need to re-install that if everything else if working for you. It will contain a few other minor changes (like reverting the system password the the Raspbian default of “raspberry”), but nothing huge that would require a re-imaging.

Sorry it took us so long to track this down!

1 Like