Kiwid using 95% CPU whilst idling [normal behavior]
Hi,
I've got a couple of kiwi SDR's that are both exhibiting the same behaviour that strikes me as strange.
When I open the admin Status webpage I see the Beagle CPU is reported very high as follows:
==Board 1 ==
Beagle CPU 95% usr / 4% sys / 1% idle, FPGA eCPU 2%
audio 0 kB/s, waterfall 0 kB/s (0/0 fps), http 0 kB/s, total 0 kB/s (0 kb/s)
==Board 2 ==
Beagle CPU 94% usr / 5% sys / 1% idle, FPGA eCPU 8%
audio 0 kB/s, waterfall 0 kB/s (0/0 fps), http 0 kB/s, total 0 kB/s (0 kb/s)
Firstly, they are both running the very latest version 1.335 from October 10th so no background updates should be in progress.
They are both plugged in to 2A power supplies with different ethernet cables.
One has no antennas attached (just power and ethernet), whilst the other has the standard GPS antenna and a very basic antenna for the RF.
I logged in to the ssh port and ran "top" which showed the that the process taking all the CPU was kiwid (see below)
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
591 root 20 0 81196 52892 4352 R 97.7 10.5 16:36.02 kiwid
Does anyone know why kiwid would be consuming so much CPU?
Presumably this is not normal...?
Cheers,
Mark
I've got a couple of kiwi SDR's that are both exhibiting the same behaviour that strikes me as strange.
When I open the admin Status webpage I see the Beagle CPU is reported very high as follows:
==Board 1 ==
Beagle CPU 95% usr / 4% sys / 1% idle, FPGA eCPU 2%
audio 0 kB/s, waterfall 0 kB/s (0/0 fps), http 0 kB/s, total 0 kB/s (0 kb/s)
==Board 2 ==
Beagle CPU 94% usr / 5% sys / 1% idle, FPGA eCPU 8%
audio 0 kB/s, waterfall 0 kB/s (0/0 fps), http 0 kB/s, total 0 kB/s (0 kb/s)
Firstly, they are both running the very latest version 1.335 from October 10th so no background updates should be in progress.
They are both plugged in to 2A power supplies with different ethernet cables.
One has no antennas attached (just power and ethernet), whilst the other has the standard GPS antenna and a very basic antenna for the RF.
I logged in to the ssh port and ran "top" which showed the that the process taking all the CPU was kiwid (see below)
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
591 root 20 0 81196 52892 4352 R 97.7 10.5 16:36.02 kiwid
Does anyone know why kiwid would be consuming so much CPU?
Presumably this is not normal...?
Cheers,
Mark
Comments