This one is ok.
The dump indicates Sched Debug Version: v0.11, 4.8.0-11-generic
#12~lp1627108Commit3d30544Reverted
so this is without the culprit commit
This one has the exact same odds values for system.slice->tg_load_avg
than the 1st dump that you sent yesterday
The dump indicates Sched Debug Version: v0.11, 4.8.0-22-generic #24-Ubuntu
So this dump has been done with a different kernel than for the dump above.
As I can't find any stress task in the dump, i tend to believe that
the dump has been done before starting the stress tasks and not after
starting them. Can you confirm ?
If i'm right, it mean that the problem was already there before
starting stress tasks."
From Upstream:
"> Here is the dump before stress is started: /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/1627108/ +attachment/ 4760437/ +files/ dump_nonbuggy
> https:/
This one is ok. mmit3d30544Reve rted
The dump indicates Sched Debug Version: v0.11, 4.8.0-11-generic
#12~lp1627108Co
so this is without the culprit commit
> /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/1627108/ +attachment/ 4760436/ +files/ dump_buggy
> Here it is after:
> https:/
>
This one has the exact same odds values for system. slice-> tg_load_ avg
than the 1st dump that you sent yesterday
The dump indicates Sched Debug Version: v0.11, 4.8.0-22-generic #24-Ubuntu
So this dump has been done with a different kernel than for the dump above.
As I can't find any stress task in the dump, i tend to believe that
the dump has been done before starting the stress tasks and not after
starting them. Can you confirm ?
If i'm right, it mean that the problem was already there before
starting stress tasks."