bobross419
Golden Member
After installing the most recent auto-updates earlier I started noticing some of the migration/# processes using a ridiculously high amount of CPU (1 illion+ %😉 according to my widget. Everything looks fine on a top and also when looking at the System Monitor (both processes tab and resources tab).
Unfortunately, googling for "migration/0" anything returns results from every single person that ever posted up a top.
ps
top
/proc/loadavg
uptime
Current values are after a reboot. Prior to reboot all four of the migration processes were showing these crazy values.
It looks like ps is calculating using the same data as top's TIME+ (cpu time, hundredths).
I've found plenty of information about the migration processes being a kernel process that is supposed to send threads to different processors or something, but no explanation as to why it is giving such crazy values in ps.
Also not seeing any excessive CPU temps or fan speeds based upon comparing current values to some previous logs that I had collected. Functionally, this doesn't appear to be actually impacting anything, but I'd still like to understand why the ps value and top TIME+ are so outrageous.
Thanks in advance guys.
Unfortunately, googling for "migration/0" anything returns results from every single person that ever posted up a top.
ps
Code:
$ ps ax -o pid,comm,pcpu | grep "migration"
6 migration/0 0.0
7 migration/1 389094773
11 migration/2 0.0
14 migration/3 0.0
Code:
$ top -p 6,7,11,14 -b
top - 18:27:10 up 23 min, 7 users, load average: 0.09, 0.13, 0.14
Tasks: 4 total, 0 running, 4 sleeping, 0 stopped, 0 zombie
Cpu(s): 7.7%us, 1.3%sy, 0.0%ni, 90.5%id, 0.4%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 8192592k total, 1700872k used, 6491720k free, 99512k buffers
Swap: 8385532k total, 0k used, 8385532k free, 473816k cached
PID VIRT RES SHR S %CPU %MEM TIME+ COMMAND
6 0 0 0 S 0 0.0 0:00.00 migration/0
7 0 0 0 S 0 0.0 5124095h migration/1
11 0 0 0 S 0 0.0 0:00.00 migration/2
14 0 0 0 S 0 0.0 0:00.00 migration/3
Code:
$ cat /proc/loadavg
0.12 0.14 0.14 1/345 7995
Code:
$ uptime
18:45:11 up 41 min, 7 users, load average: 0.25, 0.18, 0.15
It looks like ps is calculating using the same data as top's TIME+ (cpu time, hundredths).
I've found plenty of information about the migration processes being a kernel process that is supposed to send threads to different processors or something, but no explanation as to why it is giving such crazy values in ps.
Also not seeing any excessive CPU temps or fan speeds based upon comparing current values to some previous logs that I had collected. Functionally, this doesn't appear to be actually impacting anything, but I'd still like to understand why the ps value and top TIME+ are so outrageous.
Thanks in advance guys.