The Industrial Raspberry Pi Forum

Posted: **13 Jan 2023, 13:03**

I have just installed a new image (Buster) and noticed that after installing python jupyter, this became unknowingly slow. Startup takes 15s, opening a file costs 5s. This is not the case with Pi's in general, and was not the case with the Jesse version.

Could this be related to these 'irq's that run at idle:

Code: Select all

top - 12:58:16 up  3:13,  1 user,  load average: 1.33, 1.32, 1.28
Tasks: 133 total,   1 running, 132 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.0 us,  0.8 sy,  0.0 ni, 98.2 id,  0.0 wa,  0.0 hi,  1.0 si,  0.0 st
MiB Mem :    923.2 total,    664.6 free,     49.9 used,    208.8 buff/cache
MiB Swap:      0.0 total,      0.0 free,      0.0 used.    802.2 avail Mem

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
   84 root     -51   0       0      0      0 S  12.5   0.0  26:37.82 irq/66-3f980000
   87 root     -51   0       0      0      0 S  12.2   0.0  27:49.07 irq/66-dwc2_hso
   37 root      20   0       0      0      0 S   5.3   0.0   3:48.53 ksoftirqd/3
  167 root     -39   0       0      0      0 D   2.6   0.0   5:16.61 piControl I/O
 3179 pi        20   0   10192   2824   2452 R   0.7   0.3   0:00.59 top
    1 root      20   0   33684   7948   6380 S   0.0   0.8   0:05.61 systemd
    2 root      20   0       0      0      0 S   0.0   0.0   0:00.02 kthreadd
    3 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 rcu_gp
    4 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 rcu_par_gp
    8 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 mm_percpu_wq
    9 root      20   0       0      0      0 S   0.0   0.0   0:00.00 rcu_tasks_kthre

Posted: **16 Jan 2023, 13:27**

Hello,

Could this be related to these 'irq's that run at idle:

The irq/66-3f980000 and irq/66-dwc2_hso are kernel threads that use drivers to handle tasks. In this case the USB (DWC2) driver.

It is normal for these to have a CPU load of around 25%, as there is a lot of traffic over USB, this cannot be avoided.

Startup takes 15s, opening a file costs 5s. This is not the case with Pi's in general, and was not the case with the Jesse version.

I cannot say what this is caused by.

Have you flashed the latest image?
https://revolutionpi.de/tutorials/downl ... evpiimages

Best regards
Giuseppe Pagano

The Industrial Raspberry Pi Forum

RevPi Connect fresh install, 25% of CPU already loaded at idle

RevPi Connect fresh install, 25% of CPU already loaded at idle

Re: RevPi Connect fresh install, 25% of CPU already loaded at idle