From mboxrd@z Thu Jan 1 00:00:00 1970 From: tony@atomide.com (Tony Lindgren) Date: Wed, 8 Nov 2017 16:11:13 -0800 Subject: n900 in next-20170901 In-Reply-To: <20171109000801.GA23982@js1304-P5Q-DELUXE> References: <20171020173146.GN4394@atomide.com> <20171023045342.GA23082@js1304-P5Q-DELUXE> <20171025173137.GQ4394@atomide.com> <20171026044829.GB11791@js1304-P5Q-DELUXE> <20171026141627.GD21504@atomide.com> <20171107053313.GA12447@js1304-P5Q-DELUXE> <20171107154842.GP28152@atomide.com> <20171108074645.GA18747@js1304-P5Q-DELUXE> <20171108163413.GU28152@atomide.com> <20171109000801.GA23982@js1304-P5Q-DELUXE> Message-ID: <20171109001113.GZ28152@atomide.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org * Joonsoo Kim [171109 00:05]: > On Wed, Nov 08, 2017 at 08:34:13AM -0800, Tony Lindgren wrote: > > * Joonsoo Kim [171108 07:43]: > > > On Tue, Nov 07, 2017 at 07:48:42AM -0800, Tony Lindgren wrote: > > > > So it seems the issue is currently at the atomic_pool_init() > > > > related code? > > > > > > Yes, your test showed it although I can't find any clue in > > > atomic_pool_init(). > > > > > > Could you test updated branch? > > > > > > https://github.com/JoonsooKim/linux/tree/cma-debug4-next-20180901 > > > > > > There are two relevant commits. > > > > > > arm/dma: stop dma allocation before __dma_alloc_remap() > > > arm/dma: disable atomic pool after dma allocation > > > > > > atomic pool initialization will be done partially to check > > > exact point of failure. These are brain-dead commits however I have no > > > idea what's going on here until now. :/ > > > > OK that booted, dmesg output below. Hopefully that provides > > you with some more clues. > > Thanks! > > Could you let me know which one is booted? Both of them? or just top > commit ("arm/dma: stop dma allocation before __dma_alloc_remap()")? Oh OK. Only the top commit boots. Regards, Tony