[PATCH] sched: Checking for stop task appearance when balancing happens
Saying that indeed mine previous observation:
"""
--- <NMI exception stack> ---
#4 [ffff883fd2907d98] multi_cpu_stop+0x64 at ffffffff810f5944
208 } while (curstate != MULTI_STOP_EXIT);
---> RIP
RIP 0xffffffff810f5944 <+100>: cmp $0x4,%edx
---> CHECKING FOR MULTI_STOP_EXIT
RDX: ffff883fd2907d98 -> does not make any sense
"""
was right due to a stop task being picked by scheduler when it should not.
And this commit is present into:
$ git tag --contains a1d9a3231eac4117cadaf4b6bba5b2902c15a33e
v3.15-rc2
v3.15-rc3
...
v4.1-rc5
Sasha pointed me the a fix for this particular behaviour in between 3.16 and 3.17:
https:/ /lkml.org/ lkml/2014/ 4/10/297
[PATCH] sched: Checking for stop task appearance when balancing happens
Saying that indeed mine previous observation:
"""
--- <NMI exception stack> ---
#4 [ffff883fd2907d98] multi_cpu_stop+0x64 at ffffffff810f5944
208 } while (curstate != MULTI_STOP_EXIT);
---> RIP
RIP 0xffffffff810f5944 <+100>: cmp $0x4,%edx
---> CHECKING FOR MULTI_STOP_EXIT
RDX: ffff883fd2907d98 -> does not make any sense
"""
was right due to a stop task being picked by scheduler when it should not.
And this commit is present into:
$ git tag --contains a1d9a3231eac411 7cadaf4b6bba5b2 902c15a33e
v3.15-rc2
v3.15-rc3
...
v4.1-rc5
So only Trusty is affected.