Messages in this thread | | | Date | Mon, 16 Sep 2013 16:06:07 +0200 | From | Michal Hocko <> | Subject | Re: [patch 0/7] improve memcg oom killer robustness v2 |
| |
On Mon 16-09-13 16:01:19, azurIt wrote: > > CC: "Johannes Weiner" <hannes@cmpxchg.org>, "Andrew Morton" <akpm@linux-foundation.org>, "David Rientjes" <rientjes@google.com>, "KAMEZAWA Hiroyuki" <kamezawa.hiroyu@jp.fujitsu.com>, "KOSAKI Motohiro" <kosaki.motohiro@jp.fujitsu.com>, linux-mm@kvack.org, cgroups@vger.kernel.org, x86@kernel.org, linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org > >On Sat 14-09-13 12:48:31, azurIt wrote: > >[...] > >> Here is the first occurence, this night between 5:15 and 5:25: > >> - this time i kept opened terminal from other server to this problematic one with htop running > >> - when server went down i opened it and saw one process of one user running at the top and taking 97% of CPU (cgroup 1304) > > > >I guess you do not have a stack trace(s) for that process? That would be > >extremely helpful. > > I'm afraid it won't be possible as server is completely not responding > when it happens. Anyway, i don't think it was a fault of one process > or one user.
You can use sysrq+l via serial console to see tasks hogging the CPU or sysrq+t to see all the existing tasks.
[...] -- Michal Hocko SUSE Labs
| |