On Sun, Nov 23, 2014 at 07:21:08PM +0100, Oleg Nesterov wrote:
> > Perhaps this is migration thread? stop_sched_class doesn't have
> > ->update_curr.
>
> Yes, I think this can explain the problem, but
>
> > could you try to cat /proc/pid-of-migration-thread/stat on your machine?
>
> This won't trigger the crash unless it is running.
This ?
$ for pid in $(pgrep migration); do cat /proc/$pid/stat; done
10 (migration/0) S 2 0 0 0 -1 69238848 0 0 0 0 0 10 0 0 -100 0 1 0 8 0 0
18446744073709551615 0 0 0 0 0 0 0 2147483647 0 18446744073709551615 0 0 17 0
99 1 0 0 0 0 0 0 0 0 0 0 0
13 (migration/1) S 2 0 0 0 -1 69238848 0 0 0 0 0 4 0 0 -100 0 1 0 9 0 0
18446744073709551615 0 0 0 0 0 0 0 2147483647 0 18446744073709551615 0 0 17 1
99 1 0 0 0 0 0 0 0 0 0 0 0
18 (migration/2) S 2 0 0 0 -1 69238848 0 0 0 0 0 4 0 0 -100 0 1 0 11 0 0
18446744073709551615 0 0 0 0 0 0 0 2147483647 0 18446744073709551615 0 0 17 2
99 1 0 0 0 0 0 0 0 0 0 0 0
23 (migration/3) S 2 0 0 0 -1 69238848 0 0 0 0 0 10 0 0 -100 0 1 0 14 0 0
18446744073709551615 0 0 0 0 0 0 0 2147483647 0 18446744073709551615 0 0 17 3
99 1 0 0 0 0 0 0 0 0 0 0 0
28 (migration/4) S 2 0 0 0 -1 69238848 0 0 0 0 0 4 0 0 -100 0 1 0 16 0 0
18446744073709551615 0 0 0 0 0 0 0 2147483647 0 18446744073709551615 0 0 17 4
99 1 0 0 0 0 0 0 0 0 0 0 0
33 (migration/5) S 2 0 0 0 -1 69238848 0 0 0 0 0 11 0 0 -100 0 1 0 19 0 0
18446744073709551615 0 0 0 0 0 0 0 2147483647 0 18446744073709551615 0 0 17 5
99 1 0 0 0 0 0 0 0 0 0 0 0
38 (migration/6) S 2 0 0 0 -1 69238848 0 0 0 0 0 10 0 0 -100 0 1 0 21 0 0
18446744073709551615 0 0 0 0 0 0 0 2147483647 0 18446744073709551615 0 0 17 6
99 1 0 0 0 0 0 0 0 0 0 0 0
43 (migration/7) S 2 0 0 0 -1 69238848 0 0 0 0 0 6 0 0 -100 0 1 0 23 0 0
18446744073709551615 0 0 0 0 0 0 0 2147483647 0 18446744073709551615 0 0 17 7
99 1 0 0 0 0 0 0 0 0 0 0 0
It doesn't trigger, of course, as I've reverted the patch. Second resume
looks ok.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
