On Mon 11-07-16 10:40:55, Shayan Pooya wrote: > > > > Could you post the stack trace of the hung oom victim? Also could you > > post the full kernel log? > > Here is the stack of the process that lives (it is *not* the > oom-victim) in a run with 100 processes and *without* strace: > > # cat /proc/7688/stack > [<ffffffff81100292>] futex_wait_queue_me+0xc2/0x120 > [<ffffffff811005a6>] futex_wait+0x116/0x280 > [<ffffffff81102d90>] do_futex+0x120/0x540 > [<ffffffff81103231>] SyS_futex+0x81/0x180 > [<ffffffff81825bf2>] entry_SYSCALL_64_fastpath+0x16/0x71 > [<ffffffffffffffff>] 0xffffffffffffffff I am not sure I understand. Is this the hung task? -- Michal Hocko SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
