> CC: "Johannes Weiner" <hannes@xxxxxxxxxxx>, "Andrew Morton" <akpm@xxxxxxxxxxxxxxxxxxxx>, "David Rientjes" <rientjes@xxxxxxxxxx>, "KAMEZAWA Hiroyuki" <kamezawa.hiroyu@xxxxxxxxxxxxxx>, "KOSAKI Motohiro" <kosaki.motohiro@xxxxxxxxxxxxxx>, linux-mm@xxxxxxxxx, cgroups@xxxxxxxxxxxxxxx, x86@xxxxxxxxxx, linux-arch@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx >On Mon 16-09-13 16:01:19, azurIt wrote: >> > CC: "Johannes Weiner" <hannes@xxxxxxxxxxx>, "Andrew Morton" <akpm@xxxxxxxxxxxxxxxxxxxx>, "David Rientjes" <rientjes@xxxxxxxxxx>, "KAMEZAWA Hiroyuki" <kamezawa.hiroyu@xxxxxxxxxxxxxx>, "KOSAKI Motohiro" <kosaki.motohiro@xxxxxxxxxxxxxx>, linux-mm@xxxxxxxxx, cgroups@xxxxxxxxxxxxxxx, x86@xxxxxxxxxx, linux-arch@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx >> >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. Doesn't work here, it just prints 'l' resp. 't'. azur -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
