Description of problem: make too slow load balansing not utilized all CPU cores system freez some time Version-Release number of selected component (if applicable): 3.15.10-200.fc20.x86_64 #1 SMP Thu Aug 14 15:39:24 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux How reproducible: 100% Steps to Reproduce: 1. reboot 2. ps awx | grep migration 3. make distclean; make -j12 Actual results: # ps awx | grep migration 9 ? S 0:00 [migration/0] 12 ? S 32951:29 [migration/1] 18 ? S 0:00 [migration/2] 23 ? S 0:00 [migration/3] 28 ? S 0:00 [migration/4] 33 ? S 0:00 [migration/5] 38 ? S 0:00 [migration/6] 43 ? S 0:00 [migration/7] 48 ? S 0:00 [migration/8] 53 ? S 0:00 [migration/9] 58 ? S 0:00 [migration/10] 63 ? S 0:00 [migration/11] make work, but very slow Expected results: Balanced CPU load. Additional info: Try cpupower frequency-set --governor performance But without fix my problem
Created attachment 929438 [details] INFO: rcu_sched detected stalls on CPUs/tasks: {}
Linux maxim.local.rfdyn.ru 3.15.10-200.vanilla.stable.knurd.1.fc20.x86_64 #1 SMP Fri Aug 15 06:52:32 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux 9 ? S 0:00 [migration/0] 12 ? S 0:00 [migration/1] 18 ? S 0:00 [migration/2] 23 ? S 0:00 [migration/3] 28 ? S 0:00 [migration/4] 33 ? S 0:00 [migration/5] 38 ? S 0:00 [migration/6] 43 ? S 0:00 [migration/7]
vanilla work, but where my 4 cores? lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 1 Core(s) per socket: 6 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 62 Model name: Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz Stepping: 4 CPU MHz: 3784.757 CPU max MHz: 3900,0000 CPU min MHz: 1200,0000 BogoMIPS: 6800.32 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 12288K NUMA node0 CPU(s): 0-7
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.17.2-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.