From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751323AbdB1GIr (ORCPT ); Tue, 28 Feb 2017 01:08:47 -0500 Received: from vps01.wiesinger.com ([46.36.37.179]:52994 "EHLO vps01.wiesinger.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750957AbdB1GIq (ORCPT ); Tue, 28 Feb 2017 01:08:46 -0500 DKIM-Filter: OpenDKIM Filter v2.11.0 wiesinger.com v1S66fOd025073 Subject: Re: Still OOM problems with 4.9er/4.10er kernels To: Michal Hocko References: <20161209134025.GB4342@dhcp22.suse.cz> <20161223025505.GA30876@bbox> <20170104091120.GD25453@dhcp22.suse.cz> <82bce413-1bd7-7f66-1c3d-0d890bbaf6f1@wiesinger.com> <20170227082734.GB14029@dhcp22.suse.cz> Cc: Minchan Kim , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Linus Torvalds From: Gerhard Wiesinger Message-ID: <73c9ee73-6981-2597-5692-ad49a41770aa@wiesinger.com> Date: Tue, 28 Feb 2017 07:06:41 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 In-Reply-To: <20170227082734.GB14029@dhcp22.suse.cz> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 27.02.2017 09:27, Michal Hocko wrote: > On Sun 26-02-17 09:40:42, Gerhard Wiesinger wrote: >> On 04.01.2017 10:11, Michal Hocko wrote: >>>> The VM stops working (e.g. not pingable) after around 8h (will be restarted >>>> automatically), happened serveral times. >>>> >>>> Had also further OOMs which I sent to Mincham. >>> Could you post them to the mailing list as well, please? >> Still OOMs on dnf update procedure with kernel 4.10: 4.10.0-1.fc26.x86_64 as >> well on 4.9.9-200.fc25.x86_64 >> >> On 4.10er kernels: > [...] >> kernel: Node 0 DMA32 free:5012kB min:2264kB low:2828kB high:3392kB >> active_anon:143580kB inactive_anon:143300kB active_file:2576kB >> inactive_file:2560kB unevictable:0kB writepending:0kB present:376688kB >> managed:353968kB mlocked:0kB slab_reclaimable:13708kB >> slab_unreclaimable:18064kB kernel_stack:2352kB pagetables:12888kB bounce:0kB >> free_pcp:412kB local_pcp:88kB free_cma:0kB > [...] > >> On 4.9er kernels: > [...] >> kernel: Node 0 DMA32 free:3356kB min:2668kB low:3332kB high:3996kB >> active_anon:122148kB inactive_anon:112068kB active_file:81324kB >> inactive_file:101972kB unevictable:0kB writepending:4648kB present:507760kB >> managed:484384kB mlocked:0kB slab_reclaimable:17660kB >> slab_unreclaimable:21404kB kernel_stack:2432kB pagetables:10124kB bounce:0kB >> free_pcp:120kB local_pcp:0kB free_cma:0kB > In both cases the amount if free memory is above the min watermark, so > we shouldn't be hitting the oom. We might have somebody freeing memory > after the last attempt, though... > > [...] >> Should be very easy to reproduce with a low mem VM (e.g. 192MB) under KVM >> with ext4 and Fedora 25 and some memory load and updating the VM. >> >> Any further progress? > The linux-next (resp. mmotm tree) has new tracepoints which should help > to tell us more about what is going on here. Could you try to enable > oom/reclaim_retry_zone and vmscan/mm_vmscan_direct_reclaim_{begin,end} Is this available in this version? https://koji.fedoraproject.org/koji/buildinfo?buildID=862775 kernel-4.11.0-0.rc0.git5.1.fc26 How to enable? Thnx. Ciao, gerhard