Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936063AbdIYOyp (ORCPT ); Mon, 25 Sep 2017 10:54:45 -0400 Received: from muru.com ([72.249.23.125]:41650 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935296AbdIYOym (ORCPT ); Mon, 25 Sep 2017 10:54:42 -0400 Date: Mon, 25 Sep 2017 07:54:37 -0700 From: Tony Lindgren To: Joonsoo Kim Cc: Pavel Machek , pali.rohar@gmail.com, sre@kernel.org, kernel list , linux-arm-kernel , linux-omap@vger.kernel.org, khilman@kernel.org, aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com, patrikbachan@gmail.com, serge@hallyn.com, abcloriens@gmail.com, "Aneesh Kumar K.V" , Vlastimil Babka , Andrew Morton , Stephen Rothwell , Russell King Subject: Re: n900 in next-20170901 Message-ID: <20170925145437.GG4394@atomide.com> References: <20170905201314.GE5024@atomide.com> <20170905233241.GA19231@js1304-P5Q-DELUXE> <20170906133057.GH5024@atomide.com> <20170907073038.GA2111@js1304-P5Q-DELUXE> <20170907161650.GP5024@atomide.com> <20170913075516.GA25036@js1304-P5Q-DELUXE> <20170913163126.GS5024@atomide.com> <20170915065608.GA8567@js1304-P5Q-DELUXE> <20170921172811.GB4394@atomide.com> <20170925080806.GA9837@js1304-P5Q-DELUXE> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170925080806.GA9837@js1304-P5Q-DELUXE> User-Agent: Mutt/1.9.0 (2017-09-02) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2101 Lines: 54 * Joonsoo Kim [170925 01:06]: > On Thu, Sep 21, 2017 at 10:28:11AM -0700, Tony Lindgren wrote: > > * Joonsoo Kim [170914 23:55]: > > > On Wed, Sep 13, 2017 at 09:31:27AM -0700, Tony Lindgren wrote: > > > > Yes I disabled CONFIG_HIGHMEM and n900 boots. To disable it, > > > > you need to remove it from arch/arm/mach-omap2/Kconfig that > > > > selects it if ARCH_OMAP2PLUS_TYPICAL is selected. > > > > > > Okay. Problem would be related to address traslation. I'd like to > > > check address traslation more. Could you apply following patch and > > > test it? And, please send me the dmesg log and your kernel config. > > > Please test this with CONFIG_DEBUG_VIRTUAL = n and CONFIG_CMA_DEBUG=y and > > > CONFIG_HIGHMEM=y and with kernel bootparam 'ignore_loglevel'. > > > > > > It would be really appreciate if you send me two logs for before/after > > > commit 9caf25f996e8. > > > > Sorry for the delays, I finally got around testing this for you. > > No problem! I really appreciate your help! > > > Compile with your patch failed for modules with __virt_to_phys_debug > > being undefined so I added EXPORT_SYMBOL there. I also enabled DEBUG_LL > > and EARLYPRINTK to get output. > > > > Below is dmesg output for 9caf25f996e8 + your patch. I'll send you > > the full logs separately. > > Hmm...there is only one caller for the CMA memory, that is, atomic_pool_init(). > Could you test one more time with 9caf25f996e8 + following patch? I'd like to > know the actual user for the CMA memory. Hmm not getting any stack with that patch after manually applying it because of tabs to spaces mangling. Regards, Tony > -------------------------->8------------------------ > diff --git a/arch/arm/mm/dma-mapping.c b/arch/arm/mm/dma-mapping.c > index 519c294..c68f34a 100644 > --- a/arch/arm/mm/dma-mapping.c > +++ b/arch/arm/mm/dma-mapping.c > @@ -587,6 +587,8 @@ static void *__alloc_from_pool(size_t size, struct page **ret_page) > ptr = (void *)val; > } > > + dump_stack(); > + > return ptr; > } >