On Thu, Oct 19, 2017 at 11:30:34AM -0700, Tony Lindgren wrote: > * Joonsoo Kim <iamjoonsoo.kim@xxxxxxx> [171018 01:27]: > > On Mon, Sep 25, 2017 at 07:54:37AM -0700, Tony Lindgren wrote: > > > * Joonsoo Kim <iamjoonsoo.kim@xxxxxxx> [170925 01:06]: > > > > On Thu, Sep 21, 2017 at 10:28:11AM -0700, Tony Lindgren wrote: > > > > > * Joonsoo Kim <iamjoonsoo.kim@xxxxxxx> [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. > > > > Sorry for long delay. > > > > Seems like your system doesn't use any CMA memory by CMA API. > > > > Could you test one more thing? > > This one is to disable CMA memory allocation from the page allocator. > > With this, we can be sure that CMA memory isn't used at all. > > > > If there is no difference with this patch, that is, the system down, > > I think that some initialization step is broken. In this case, please > > test following patch. > > > > I make a branch in github that all these patch is applied. > > Feel free to use it. > > > > https://github.com/JoonsooKim/linux/tree/cma-debug4-next-20180901 > > Still not booting, dmesg output of your test branch below. Oops... I made a mistak. Could you test with reverting commit c977ee2803787363187d6aca9cebdabc793c6531 ("omap: forcibly call save_secure_ram_context() for test") in that branch? Without reverting it, it doesn't call 'smc' so it always cause a hang. Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
