>On Wed, Oct 09, 2013 at 08:44:50PM +0200, azurIt wrote:
>> Joahnnes,
>>
>> i'm very sorry to say it but today something strange happened.. :) i was
>> just right at the computer so i noticed it almost immediately but i don't
>> have much info. Server stoped to respond from the net but i was alr
Hi azur,
On Wed, Oct 09, 2013 at 08:44:50PM +0200, azurIt wrote:
> Joahnnes,
>
> i'm very sorry to say it but today something strange happened.. :) i was just
> right at the computer so i noticed it almost immediately but i don't have
> much info. Server stoped to respond from the net but i was
>Hi azur,
>
>On Mon, Oct 07, 2013 at 01:01:49PM +0200, azurIt wrote:
>> >On Thu, Sep 26, 2013 at 06:54:59PM +0200, azurIt wrote:
>> >> On Wed, Sep 18, 2013 at 02:19:46PM -0400, Johannes Weiner wrote:
>> >> >Here is an update. Full replacement on top of 3.2 since we tried a
>> >> >dead end and it w
Hi azur,
On Mon, Oct 07, 2013 at 01:01:49PM +0200, azurIt wrote:
> >On Thu, Sep 26, 2013 at 06:54:59PM +0200, azurIt wrote:
> >> On Wed, Sep 18, 2013 at 02:19:46PM -0400, Johannes Weiner wrote:
> >> >Here is an update. Full replacement on top of 3.2 since we tried a
> >> >dead end and it would be
>On Thu, Sep 26, 2013 at 06:54:59PM +0200, azurIt wrote:
>> On Wed, Sep 18, 2013 at 02:19:46PM -0400, Johannes Weiner wrote:
>> >Here is an update. Full replacement on top of 3.2 since we tried a
>> >dead end and it would be more painful to revert individual changes.
>> >
>> >The first bug you had
> CC: "Michal Hocko" , "Andrew Morton"
> , "David Rientjes" ,
> "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> , linux...@kvack.org,
> cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> linux-kernel@vger.kernel.org
>Hi azur,
>
>On Thu, Sep 26, 2013 at 06:54:59PM +0200, azurIt w
Hi azur,
On Thu, Sep 26, 2013 at 06:54:59PM +0200, azurIt wrote:
> On Wed, Sep 18, 2013 at 02:19:46PM -0400, Johannes Weiner wrote:
> >Here is an update. Full replacement on top of 3.2 since we tried a
> >dead end and it would be more painful to revert individual changes.
> >
> >The first bug you
> CC: "Michal Hocko" , "Andrew Morton"
> , "David Rientjes" ,
> "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> , linux...@kvack.org,
> cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> linux-kernel@vger.kernel.org
>On Wed, Sep 18, 2013 at 02:19:46PM -0400, Johannes Weiner wrot
> CC: "Michal Hocko" , "Andrew Morton"
> , "David Rientjes" ,
> "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> , linux...@kvack.org,
> cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> linux-kernel@vger.kernel.org
>On Wed, Sep 18, 2013 at 02:19:46PM -0400, Johannes Weiner wrot
> CC: "Michal Hocko" , "Andrew Morton"
> , "David Rientjes" ,
> "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> , linux...@kvack.org,
> cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> linux-kernel@vger.kernel.org
>On Wed, Sep 18, 2013 at 02:19:46PM -0400, Johannes Weiner wrot
On Wed, Sep 18, 2013 at 02:19:46PM -0400, Johannes Weiner wrote:
> On Wed, Sep 18, 2013 at 02:04:55PM -0400, Johannes Weiner wrote:
> > On Wed, Sep 18, 2013 at 04:03:04PM +0200, azurIt wrote:
> > > > CC: "Johannes Weiner" , "Andrew Morton"
> > > > , "David Rientjes" ,
> > > > "KAMEZAWA Hiroyuki"
On Wed, Sep 18, 2013 at 02:04:55PM -0400, Johannes Weiner wrote:
> On Wed, Sep 18, 2013 at 04:03:04PM +0200, azurIt wrote:
> > > CC: "Johannes Weiner" , "Andrew Morton"
> > > , "David Rientjes" ,
> > > "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> > > , linux...@kvack.org,
> > > cgro...@vger.kernel
On Wed, Sep 18, 2013 at 04:03:04PM +0200, azurIt wrote:
> > CC: "Johannes Weiner" , "Andrew Morton"
> > , "David Rientjes" ,
> > "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> > , linux...@kvack.org,
> > cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> > linux-kernel@vger.ker
On Wed 18-09-13 20:02:39, azurIt wrote:
> > CC: "Johannes Weiner" , "Andrew Morton"
> > , "David Rientjes" ,
> > "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> > , linux...@kvack.org,
> > cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> > linux-kernel@vger.kernel.org
> >On We
> CC: "Johannes Weiner" , "Andrew Morton"
> , "David Rientjes" ,
> "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> , linux...@kvack.org,
> cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> linux-kernel@vger.kernel.org
>On Wed 18-09-13 16:33:06, azurIt wrote:
>> > CC: "Johannes
On Wed 18-09-13 16:33:06, azurIt wrote:
> > CC: "Johannes Weiner" , "Andrew Morton"
> > , "David Rientjes" ,
> > "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> > , linux...@kvack.org,
> > cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> > linux-kernel@vger.kernel.org
> >On We
> CC: "Johannes Weiner" , "Andrew Morton"
> , "David Rientjes" ,
> "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> , linux...@kvack.org,
> cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> linux-kernel@vger.kernel.org
>On Wed 18-09-13 16:03:04, azurIt wrote:
>[..]
>> I was fina
On Wed 18-09-13 16:03:04, azurIt wrote:
[..]
> I was finally able to get stack of problematic process :) I saved it
> two times from the same process, as Michal suggested (i wasn't able to
> take more). Here it is:
>
> First (doesn't look very helpfull):
> [] 0x
No it is not.
>
> CC: "Johannes Weiner" , "Andrew Morton"
> , "David Rientjes" ,
> "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> , linux...@kvack.org,
> cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> linux-kernel@vger.kernel.org
>On Tue 17-09-13 13:15:35, azurIt wrote:
>[...]
>> Is someth
On Tue 17-09-13 13:15:35, azurIt wrote:
[...]
> Is something unusual on this stack?
>
>
> [] dump_header+0x7e/0x1e0
> [] ? find_lock_task_mm+0x2f/0x70
> [] oom_kill_process+0x85/0x2a0
> [] mem_cgroup_out_of_memory+0xa8/0xf0
> [] mem_cgroup_oom_synchronize+0x2e6/0x310
> [] ? mem_cgroup_uncharge_pa
> CC: "Michal Hocko" , "Andrew Morton"
> , "David Rientjes" ,
> "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> , linux...@kvack.org,
> cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> linux-kernel@vger.kernel.org
>On Mon, Sep 16, 2013 at 10:52:46PM +0200, azurIt wrote:
>> > C
__
> Od: Johannes Weiner
> Komu: azurIt
> Dátum: 17.09.2013 02:02
> Predmet: Re: [patch 0/7] improve memcg oom killer robustness v2
>
> CC: "Michal Hocko" , "Andrew Morton"
> , "Davi
On Mon, Sep 16, 2013 at 10:52:46PM +0200, azurIt wrote:
> > CC: "Johannes Weiner" , "Andrew Morton"
> > , "David Rientjes" ,
> > "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> > , linux...@kvack.org,
> > cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> > linux-kernel@vger.ker
> CC: "Johannes Weiner" , "Andrew Morton"
> , "David Rientjes" ,
> "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> , linux...@kvack.org,
> cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> linux-kernel@vger.kernel.org
>On Mon 16-09-13 17:05:43, azurIt wrote:
>> > CC: "Johannes
> CC: "Johannes Weiner" , "Andrew Morton"
> , "David Rientjes" ,
> "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> , linux...@kvack.org,
> cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> linux-kernel@vger.kernel.org
>On Mon 16-09-13 17:05:43, azurIt wrote:
>> > CC: "Johannes
On Mon 16-09-13 17:05:43, azurIt wrote:
> > CC: "Johannes Weiner" , "Andrew Morton"
> > , "David Rientjes" ,
> > "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> > , linux...@kvack.org,
> > cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> > linux-kernel@vger.kernel.org
> >On Mo
> CC: "Michal Hocko" , "Andrew Morton"
> , "David Rientjes" ,
> "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> , linux...@kvack.org,
> cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> linux-kernel@vger.kernel.org
>On Mon, Sep 16, 2013 at 05:05:43PM +0200, azurIt wrote:
>> > C
On Mon, Sep 16, 2013 at 05:05:43PM +0200, azurIt wrote:
> > CC: "Johannes Weiner" , "Andrew Morton"
> > , "David Rientjes" ,
> > "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> > , linux...@kvack.org,
> > cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> > linux-kernel@vger.ker
> CC: "Johannes Weiner" , "Andrew Morton"
> , "David Rientjes" ,
> "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> , linux...@kvack.org,
> cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> linux-kernel@vger.kernel.org
>On Mon 16-09-13 16:13:16, azurIt wrote:
>[...]
>> >You can
On Mon 16-09-13 16:13:16, azurIt wrote:
[...]
> >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'.
I am using telnet for accessing my serial consoles exported by
the multiplicato
> CC: "Johannes Weiner" , "Andrew Morton"
> , "David Rientjes" ,
> "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> , linux...@kvack.org,
> cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> linux-kernel@vger.kernel.org
>On Mon 16-09-13 16:01:19, azurIt wrote:
>> > CC: "Johannes
On Mon 16-09-13 16:01:19, azurIt wrote:
> > CC: "Johannes Weiner" , "Andrew Morton"
> > , "David Rientjes" ,
> > "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> > , linux...@kvack.org,
> > cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> > linux-kernel@vger.kernel.org
> >On Sa
[Sorry for the late reply. I am in pre-long-vacation mode trying to
clean up my desk]
On Thu 12-09-13 08:59:38, Johannes Weiner wrote:
> On Mon, Sep 09, 2013 at 02:56:59PM +0200, Michal Hocko wrote:
[...]
> > Hmm, wait a second. I have completely forgot about the kmem charging
> > path during the
> CC: "Johannes Weiner" , "Andrew Morton"
> , "David Rientjes" ,
> "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> , 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 t
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 th
> CC: "Andrew Morton" , "Michal Hocko"
> , "David Rientjes" , "KAMEZAWA Hiroyuki"
> , "KOSAKI Motohiro"
> , linux...@kvack.org,
> cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> linux-kernel@vger.kernel.org
>On Wed, Sep 11, 2013 at 09:41:18PM +0200, azurIt wrote:
>> >On
> CC: "Andrew Morton" , "Michal Hocko"
> , "David Rientjes" , "KAMEZAWA Hiroyuki"
> , "KOSAKI Motohiro"
> , linux...@kvack.org,
> cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> linux-kernel@vger.kernel.org
>On Wed, Sep 11, 2013 at 09:41:18PM +0200, azurIt wrote:
>> >On
On Mon, Sep 09, 2013 at 02:56:59PM +0200, Michal Hocko wrote:
> [Adding Glauber - the full patch is here https://lkml.org/lkml/2013/9/5/319]
>
> On Mon 09-09-13 14:36:25, Michal Hocko wrote:
> > On Thu 05-09-13 12:18:17, Johannes Weiner wrote:
> > [...]
> > > From: Johannes Weiner
> > > Subject:
On Wed, Sep 11, 2013 at 09:41:18PM +0200, azurIt wrote:
> >On Wed, Sep 11, 2013 at 08:54:48PM +0200, azurIt wrote:
> >> >On Wed, Sep 11, 2013 at 02:33:05PM +0200, azurIt wrote:
> >> >> >On Tue, Sep 10, 2013 at 11:32:47PM +0200, azurIt wrote:
> >> >> >> >On Tue, Sep 10, 2013 at 11:08:53PM +0200, azu
>On Wed, Sep 11, 2013 at 08:54:48PM +0200, azurIt wrote:
>> >On Wed, Sep 11, 2013 at 02:33:05PM +0200, azurIt wrote:
>> >> >On Tue, Sep 10, 2013 at 11:32:47PM +0200, azurIt wrote:
>> >> >> >On Tue, Sep 10, 2013 at 11:08:53PM +0200, azurIt wrote:
>> >> >> >> >On Tue, Sep 10, 2013 at 09:32:53PM +0200
On Wed, Sep 11, 2013 at 08:54:48PM +0200, azurIt wrote:
> >On Wed, Sep 11, 2013 at 02:33:05PM +0200, azurIt wrote:
> >> >On Tue, Sep 10, 2013 at 11:32:47PM +0200, azurIt wrote:
> >> >> >On Tue, Sep 10, 2013 at 11:08:53PM +0200, azurIt wrote:
> >> >> >> >On Tue, Sep 10, 2013 at 09:32:53PM +0200, azu
>On Wed, Sep 11, 2013 at 02:33:05PM +0200, azurIt wrote:
>> >On Tue, Sep 10, 2013 at 11:32:47PM +0200, azurIt wrote:
>> >> >On Tue, Sep 10, 2013 at 11:08:53PM +0200, azurIt wrote:
>> >> >> >On Tue, Sep 10, 2013 at 09:32:53PM +0200, azurIt wrote:
>> >> >> >> Here is full kernel log between 6:00 and
On Wed, Sep 11, 2013 at 02:33:05PM +0200, azurIt wrote:
> >On Tue, Sep 10, 2013 at 11:32:47PM +0200, azurIt wrote:
> >> >On Tue, Sep 10, 2013 at 11:08:53PM +0200, azurIt wrote:
> >> >> >On Tue, Sep 10, 2013 at 09:32:53PM +0200, azurIt wrote:
> >> >> >> Here is full kernel log between 6:00 and 7:59:
>On Tue, Sep 10, 2013 at 11:32:47PM +0200, azurIt wrote:
>> >On Tue, Sep 10, 2013 at 11:08:53PM +0200, azurIt wrote:
>> >> >On Tue, Sep 10, 2013 at 09:32:53PM +0200, azurIt wrote:
>> >> >> Here is full kernel log between 6:00 and 7:59:
>> >> >> http://watchdog.sk/lkml/kern6.log
>> >> >
>> >> >Wow,
On Tue, Sep 10, 2013 at 11:32:47PM +0200, azurIt wrote:
> >On Tue, Sep 10, 2013 at 11:08:53PM +0200, azurIt wrote:
> >> >On Tue, Sep 10, 2013 at 09:32:53PM +0200, azurIt wrote:
> >> >> Here is full kernel log between 6:00 and 7:59:
> >> >> http://watchdog.sk/lkml/kern6.log
> >> >
> >> >Wow, your ap
>On Tue, Sep 10, 2013 at 11:08:53PM +0200, azurIt wrote:
>> >On Tue, Sep 10, 2013 at 09:32:53PM +0200, azurIt wrote:
>> >> >On Tue, Sep 10, 2013 at 08:13:59PM +0200, azurIt wrote:
>> >> >> >On Mon, Sep 09, 2013 at 09:59:17PM +0200, azurIt wrote:
>> >> >> >> >On Mon, Sep 09, 2013 at 03:10:10PM +0200
On Tue, Sep 10, 2013 at 11:08:53PM +0200, azurIt wrote:
> >On Tue, Sep 10, 2013 at 09:32:53PM +0200, azurIt wrote:
> >> >On Tue, Sep 10, 2013 at 08:13:59PM +0200, azurIt wrote:
> >> >> >On Mon, Sep 09, 2013 at 09:59:17PM +0200, azurIt wrote:
> >> >> >> >On Mon, Sep 09, 2013 at 03:10:10PM +0200, azu
>On Tue, Sep 10, 2013 at 09:32:53PM +0200, azurIt wrote:
>> >On Tue, Sep 10, 2013 at 08:13:59PM +0200, azurIt wrote:
>> >> >On Mon, Sep 09, 2013 at 09:59:17PM +0200, azurIt wrote:
>> >> >> >On Mon, Sep 09, 2013 at 03:10:10PM +0200, azurIt wrote:
>> >> >> >> >Hi azur,
>> >> >> >> >
>> >> >> >> >On W
>On Tue, Sep 10, 2013 at 08:13:59PM +0200, azurIt wrote:
>> >On Mon, Sep 09, 2013 at 09:59:17PM +0200, azurIt wrote:
>> >> >On Mon, Sep 09, 2013 at 03:10:10PM +0200, azurIt wrote:
>> >> >> >Hi azur,
>> >> >> >
>> >> >> >On Wed, Sep 04, 2013 at 10:18:52AM +0200, azurIt wrote:
>> >> >> >> > CC: "Andr
On Tue, Sep 10, 2013 at 09:32:53PM +0200, azurIt wrote:
> >On Tue, Sep 10, 2013 at 08:13:59PM +0200, azurIt wrote:
> >> >On Mon, Sep 09, 2013 at 09:59:17PM +0200, azurIt wrote:
> >> >> >On Mon, Sep 09, 2013 at 03:10:10PM +0200, azurIt wrote:
> >> >> >> >Hi azur,
> >> >> >> >
> >> >> >> >On Wed, Sep
On Tue, Sep 10, 2013 at 08:13:59PM +0200, azurIt wrote:
> >On Mon, Sep 09, 2013 at 09:59:17PM +0200, azurIt wrote:
> >> >On Mon, Sep 09, 2013 at 03:10:10PM +0200, azurIt wrote:
> >> >> >Hi azur,
> >> >> >
> >> >> >On Wed, Sep 04, 2013 at 10:18:52AM +0200, azurIt wrote:
> >> >> >> > CC: "Andrew Mort
>On Mon, Sep 09, 2013 at 09:59:17PM +0200, azurIt wrote:
>> >On Mon, Sep 09, 2013 at 03:10:10PM +0200, azurIt wrote:
>> >> >Hi azur,
>> >> >
>> >> >On Wed, Sep 04, 2013 at 10:18:52AM +0200, azurIt wrote:
>> >> >> > CC: "Andrew Morton" , "Michal Hocko"
>> >> >> > , "David Rientjes" , "KAMEZAWA
>>
>On Mon, Sep 09, 2013 at 09:59:17PM +0200, azurIt wrote:
>> >On Mon, Sep 09, 2013 at 03:10:10PM +0200, azurIt wrote:
>> >> >Hi azur,
>> >> >
>> >> >On Wed, Sep 04, 2013 at 10:18:52AM +0200, azurIt wrote:
>> >> >> > CC: "Andrew Morton" , "Michal Hocko"
>> >> >> > , "David Rientjes" , "KAMEZAWA
>>
>On Mon, Sep 09, 2013 at 09:59:17PM +0200, azurIt wrote:
>> >On Mon, Sep 09, 2013 at 03:10:10PM +0200, azurIt wrote:
>> >> >Hi azur,
>> >> >
>> >> >On Wed, Sep 04, 2013 at 10:18:52AM +0200, azurIt wrote:
>> >> >> > CC: "Andrew Morton" , "Michal Hocko"
>> >> >> > , "David Rientjes" , "KAMEZAWA
>>
On Mon, Sep 09, 2013 at 09:59:17PM +0200, azurIt wrote:
> >On Mon, Sep 09, 2013 at 03:10:10PM +0200, azurIt wrote:
> >> >Hi azur,
> >> >
> >> >On Wed, Sep 04, 2013 at 10:18:52AM +0200, azurIt wrote:
> >> >> > CC: "Andrew Morton" , "Michal Hocko"
> >> >> > , "David Rientjes" , "KAMEZAWA
> >> >> >
>On Mon, Sep 09, 2013 at 03:10:10PM +0200, azurIt wrote:
>> >Hi azur,
>> >
>> >On Wed, Sep 04, 2013 at 10:18:52AM +0200, azurIt wrote:
>> >> > CC: "Andrew Morton" , "Michal Hocko"
>> >> > , "David Rientjes" , "KAMEZAWA
>> >> > Hiroyuki" , "KOSAKI Motohiro"
>> >> > , linux...@kvack.org,
>> >> >
On Mon, Sep 09, 2013 at 03:10:10PM +0200, azurIt wrote:
> >Hi azur,
> >
> >On Wed, Sep 04, 2013 at 10:18:52AM +0200, azurIt wrote:
> >> > CC: "Andrew Morton" , "Michal Hocko"
> >> > , "David Rientjes" , "KAMEZAWA
> >> > Hiroyuki" , "KOSAKI Motohiro"
> >> > , linux...@kvack.org,
> >> > cgro...@v
>Hi azur,
>
>On Wed, Sep 04, 2013 at 10:18:52AM +0200, azurIt wrote:
>> > CC: "Andrew Morton" , "Michal Hocko"
>> > , "David Rientjes" , "KAMEZAWA
>> > Hiroyuki" , "KOSAKI Motohiro"
>> > , linux...@kvack.org,
>> > cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
>> > linux
[Adding Glauber - the full patch is here https://lkml.org/lkml/2013/9/5/319]
On Mon 09-09-13 14:36:25, Michal Hocko wrote:
> On Thu 05-09-13 12:18:17, Johannes Weiner wrote:
> [...]
> > From: Johannes Weiner
> > Subject: [patch] mm: memcg: do not trap chargers with full callstack on OOM
> >
> [.
On Thu 05-09-13 12:18:17, Johannes Weiner wrote:
[...]
> From: Johannes Weiner
> Subject: [patch] mm: memcg: do not trap chargers with full callstack on OOM
>
[...]
>
> To fix this, never do any OOM handling directly in the charge context.
> When an OOM situation is detected, let the task rememb
On Thu, Sep 05, 2013 at 02:43:52PM +0200, Michal Hocko wrote:
> On Thu 05-09-13 07:54:30, Johannes Weiner wrote:
> > There are a few more find_or_create() sites that do not propagate an
> > error and it's incredibly hard to find out whether they are even taken
> > during a page fault. It's not pra
On Thu 05-09-13 07:54:30, Johannes Weiner wrote:
[...]
> From: Johannes Weiner
> Subject: [patch] mm: memcg: handle non-error OOM situations more gracefully
>
> Many places that can trigger a memcg OOM situation return gracefully
> and don't propagate VM_FAULT_OOM up the fault stack.
>
> It's no
>On Thu 05-09-13 14:33:43, azurIt wrote:
>[...]
>> >Just to be sure I got you right. You have killed all the processes from
>> >the group you have sent stacks for, right? If that is the case I am
>> >really curious about processes sitting in sleep_on_page_killable because
>> >those are killable by
On Thu 05-09-13 14:33:43, azurIt wrote:
[...]
> >Just to be sure I got you right. You have killed all the processes from
> >the group you have sent stacks for, right? If that is the case I am
> >really curious about processes sitting in sleep_on_page_killable because
> >those are killable by defini
On Thu 05-09-13 07:54:30, Johannes Weiner wrote:
> On Wed, Sep 04, 2013 at 10:18:52AM +0200, azurIt wrote:
> > Ok, i see this message several times in my syslog logs, one of them
> > is also for this unremovable cgroup (but maybe all of them cannot
> > be removed, should i try?). Example of the log
>On Thu 05-09-13 13:47:02, azurIt wrote:
>> >On Thu 05-09-13 12:17:00, azurIt wrote:
>> >> >[...]
>> >> >> My script detected another freezed cgroup today, sending stacks. Is
>> >> >> there anything interesting?
>> >> >
>> >> >3 tasks are sleeping and waiting for somebody to take an action to
>> >>
On Thu 05-09-13 13:47:02, azurIt wrote:
> >On Thu 05-09-13 12:17:00, azurIt wrote:
> >> >[...]
> >> >> My script detected another freezed cgroup today, sending stacks. Is
> >> >> there anything interesting?
> >> >
> >> >3 tasks are sleeping and waiting for somebody to take an action to
> >> >resolv
Hi azur,
On Wed, Sep 04, 2013 at 10:18:52AM +0200, azurIt wrote:
> > CC: "Andrew Morton" , "Michal Hocko"
> > , "David Rientjes" , "KAMEZAWA
> > Hiroyuki" , "KOSAKI Motohiro"
> > , linux...@kvack.org,
> > cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> > linux-kernel@v
>On Thu 05-09-13 12:17:00, azurIt wrote:
>> >[...]
>> >> My script detected another freezed cgroup today, sending stacks. Is
>> >> there anything interesting?
>> >
>> >3 tasks are sleeping and waiting for somebody to take an action to
>> >resolve memcg OOM. The memcg oom killer is enabled for that
On Thu 05-09-13 12:17:00, azurIt wrote:
> >[...]
> >> My script detected another freezed cgroup today, sending stacks. Is
> >> there anything interesting?
> >
> >3 tasks are sleeping and waiting for somebody to take an action to
> >resolve memcg OOM. The memcg oom killer is enabled for that group?
>[...]
>> My script detected another freezed cgroup today, sending stacks. Is
>> there anything interesting?
>
>3 tasks are sleeping and waiting for somebody to take an action to
>resolve memcg OOM. The memcg oom killer is enabled for that group? If
>yes, which task has been selected to be killed?
On Thu 05-09-13 11:14:30, azurIt wrote:
[...]
> My script detected another freezed cgroup today, sending stacks. Is
> there anything interesting?
3 tasks are sleeping and waiting for somebody to take an action to
resolve memcg OOM. The memcg oom killer is enabled for that group? If
yes, which tas
>> >[...]
>> >> My script has just detected (and killed) another freezed cgroup. I
>> >> must say that i'm not 100% sure that cgroup was really freezed but it
>> >> has 99% or more memory usage for at least 30 seconds (well, or it has
>> >> 99% memory usage in both two cases the script was checking
>> >[...]
>> >> My script has just detected (and killed) another freezed cgroup. I
>> >> must say that i'm not 100% sure that cgroup was really freezed but it
>> >> has 99% or more memory usage for at least 30 seconds (well, or it has
>> >> 99% memory usage in both two cases the script was checking
On Wed 04-09-13 14:10:00, azurIt wrote:
> >[...]
> >> My script has just detected (and killed) another freezed cgroup. I
> >> must say that i'm not 100% sure that cgroup was really freezed but it
> >> has 99% or more memory usage for at least 30 seconds (well, or it has
> >> 99% memory usage in bot
>[...]
>> My script has just detected (and killed) another freezed cgroup. I
>> must say that i'm not 100% sure that cgroup was really freezed but it
>> has 99% or more memory usage for at least 30 seconds (well, or it has
>> 99% memory usage in both two cases the script was checking it). Here
>> a
On Wed 04-09-13 11:45:23, azurIt wrote:
[...]
> My script has just detected (and killed) another freezed cgroup. I
> must say that i'm not 100% sure that cgroup was really freezed but it
> has 99% or more memory usage for at least 30 seconds (well, or it has
> 99% memory usage in both two cases the
>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
>>
> CC: "Andrew Morton" , "Michal Hocko"
> , "David Rientjes" , "KAMEZAWA Hiroyuki"
> , "KOSAKI Motohiro"
> , linux...@kvack.org,
> cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> linux-kernel@vger.kernel.org
>Hello azur,
>
>On Mon, Sep 02, 2013 at 12:38:02PM +0200, azurI
>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
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'
>>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 an
>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
>Hi azur,
>
>here is the x86-only rollup of the series for 3.2.
>
>Thanks!
>Johannes
Hi Johannes,
i'm running kernel with this new patch for 1 day now without any problems! Will
report back in few weeks or months or in case of any problems occures. Thank
you!
azur
--
To unsubscribe from this
Hi azur,
here is the x86-only rollup of the series for 3.2.
Thanks!
Johannes
---
diff --git a/arch/x86/mm/fault.c b/arch/x86/mm/fault.c
index 5db0490..314fe53 100644
--- a/arch/x86/mm/fault.c
+++ b/arch/x86/mm/fault.c
@@ -842,30 +842,22 @@ do_sigbus(struct pt_regs *regs, unsigned long error_code
Changes in version 2:
o use user_mode() instead of open coding it on s390 (Heiko Carstens)
o clean up memcg OOM enable/disable toggling (Michal Hocko & KOSAKI
Motohiro)
o add a separate patch to rework and document OOM locking
o fix a problem with lost wakeups when sleeping on the OOM lock
o fix
86 matches
Mail list logo
