Hello azur,
On Mon, Sep 02, 2013 at 12:38:02PM +0200, azurIt wrote:
> >>Hi azur,
> >>
> >>here is the x86-only rollup of the series for 3.2.
> >>
> >>Thanks!
> >>Johannes
> >>---
> >
> >
> >Johannes,
> >
> >unfortunately, one problem arises: I have (again) cgroup which cannot be deleted :( it's a user who had very high memory usage and was reaching his limit very often. Do you need any info which i can gather now?
Did the OOM killer go off in this group?
Was there a warning in the syslog ("Fixing unhandled memcg OOM
context")?
If it happens again, could you check if there are tasks left in the
cgroup? And provide /proc/<pid>/stack of the hung task trying to
delete the cgroup?
> Now i can definitely confirm that problem is NOT fixed :( it happened again but i don't have any data because i already disabled all debug output.
Which debug output?
Do you still have access to the syslog?
It's possible that, as your system does not deadlock on the OOMing
cgroup anymore, you hit a separate bug...
Thanks!
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>