On Mon 16-09-13 16:01:19, azurIt wrote: > > CC: "Johannes Weiner" <han...@cmpxchg.org>, "Andrew Morton" > > <a...@linux-foundation.org>, "David Rientjes" <rient...@google.com>, > > "KAMEZAWA Hiroyuki" <kamezawa.hir...@jp.fujitsu.com>, "KOSAKI Motohiro" > > <kosaki.motoh...@jp.fujitsu.com>, linux...@kvack.org, > > cgro...@vger.kernel.org, x...@kernel.org, linux-a...@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 -- 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/
