From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752700AbbE0IgY (ORCPT ); Wed, 27 May 2015 04:36:24 -0400 Received: from mail-wi0-f176.google.com ([209.85.212.176]:34628 "EHLO mail-wi0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752562AbbE0IgT (ORCPT ); Wed, 27 May 2015 04:36:19 -0400 Message-ID: <55658201.5090208@linaro.org> Date: Wed, 27 May 2015 09:36:17 +0100 From: Daniel Thompson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Maxime Coquelin CC: Mike Turquette , Stephen Boyd , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Russell King , Kamil Lulko , Andreas Farber , linux-clk@vger.kernel.org, "devicetree@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , patches@linaro.org, linaro-kernel@lists.linaro.org Subject: Re: [RFC PATCH 0/3] clk: stm32: Add clock driver for STM32F4[23]xxx devices References: <1432327273-6810-1-git-send-email-daniel.thompson@linaro.org> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 26/05/15 17:41, Maxime Coquelin wrote: >> 2. Allocating ~80 clock components appears to fragment memory enough >> to prevent busybox (.text is ~300K, non-XIP) from running getty. >> I have to use "init=/bin/sh" to avoid OOM problems. > > Yes, I reproduced the same issue while testing your work. > > Could you try with: > CONFIG_NOMMU_INITIAL_TRIM_EXCESS=0 > > It solves (hides) the problem on my side. > You can eventually setting it once booted to 1 via procfs. That works for me too. Thanks. Incidentally switching to SLOB also reduced the problem for me. It was OK whilst I had ~20 clocks (and debugfs) but not enough for me to run with all the clocks registered. Daniel. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Thompson Subject: Re: [RFC PATCH 0/3] clk: stm32: Add clock driver for STM32F4[23]xxx devices Date: Wed, 27 May 2015 09:36:17 +0100 Message-ID: <55658201.5090208@linaro.org> References: <1432327273-6810-1-git-send-email-daniel.thompson@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Maxime Coquelin Cc: Mike Turquette , Stephen Boyd , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Russell King , Kamil Lulko , Andreas Farber , linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , patches-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org, linaro-kernel-cunTk1MwBs8s++Sfvej+rw@public.gmane.org List-Id: devicetree@vger.kernel.org On 26/05/15 17:41, Maxime Coquelin wrote: >> 2. Allocating ~80 clock components appears to fragment memory enough >> to prevent busybox (.text is ~300K, non-XIP) from running getty. >> I have to use "init=/bin/sh" to avoid OOM problems. > > Yes, I reproduced the same issue while testing your work. > > Could you try with: > CONFIG_NOMMU_INITIAL_TRIM_EXCESS=0 > > It solves (hides) the problem on my side. > You can eventually setting it once booted to 1 via procfs. That works for me too. Thanks. Incidentally switching to SLOB also reduced the problem for me. It was OK whilst I had ~20 clocks (and debugfs) but not enough for me to run with all the clocks registered. Daniel. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Return-Path: Message-ID: <55658201.5090208@linaro.org> Date: Wed, 27 May 2015 09:36:17 +0100 From: Daniel Thompson MIME-Version: 1.0 To: Maxime Coquelin CC: Mike Turquette , Stephen Boyd , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Russell King , Kamil Lulko , Andreas Farber , linux-clk@vger.kernel.org, "devicetree@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , patches@linaro.org, linaro-kernel@lists.linaro.org Subject: Re: [RFC PATCH 0/3] clk: stm32: Add clock driver for STM32F4[23]xxx devices References: <1432327273-6810-1-git-send-email-daniel.thompson@linaro.org> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed List-ID: On 26/05/15 17:41, Maxime Coquelin wrote: >> 2. Allocating ~80 clock components appears to fragment memory enough >> to prevent busybox (.text is ~300K, non-XIP) from running getty. >> I have to use "init=/bin/sh" to avoid OOM problems. > > Yes, I reproduced the same issue while testing your work. > > Could you try with: > CONFIG_NOMMU_INITIAL_TRIM_EXCESS=0 > > It solves (hides) the problem on my side. > You can eventually setting it once booted to 1 via procfs. That works for me too. Thanks. Incidentally switching to SLOB also reduced the problem for me. It was OK whilst I had ~20 clocks (and debugfs) but not enough for me to run with all the clocks registered. Daniel. From mboxrd@z Thu Jan 1 00:00:00 1970 From: daniel.thompson@linaro.org (Daniel Thompson) Date: Wed, 27 May 2015 09:36:17 +0100 Subject: [RFC PATCH 0/3] clk: stm32: Add clock driver for STM32F4[23]xxx devices In-Reply-To: References: <1432327273-6810-1-git-send-email-daniel.thompson@linaro.org> Message-ID: <55658201.5090208@linaro.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 26/05/15 17:41, Maxime Coquelin wrote: >> 2. Allocating ~80 clock components appears to fragment memory enough >> to prevent busybox (.text is ~300K, non-XIP) from running getty. >> I have to use "init=/bin/sh" to avoid OOM problems. > > Yes, I reproduced the same issue while testing your work. > > Could you try with: > CONFIG_NOMMU_INITIAL_TRIM_EXCESS=0 > > It solves (hides) the problem on my side. > You can eventually setting it once booted to 1 via procfs. That works for me too. Thanks. Incidentally switching to SLOB also reduced the problem for me. It was OK whilst I had ~20 clocks (and debugfs) but not enough for me to run with all the clocks registered. Daniel.