From mboxrd@z Thu Jan 1 00:00:00 1970 Sender: Michael Welling Date: Tue, 2 Feb 2016 19:36:15 -0600 From: Michael Welling Message-ID: <20160203013615.GG27804@deathstar> References: <20160202195355.GC27804@deathstar> <20160202200235.GB29937@hermes.click-hack.org> <20160202203539.GD27804@deathstar> <20160202205945.GC29937@hermes.click-hack.org> <20160203003212.GE27804@deathstar> <20160203004307.GA18030@hermes.click-hack.org> <20160203012135.GF27804@deathstar> <20160203013118.GC18030@hermes.click-hack.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160203013118.GC18030@hermes.click-hack.org> Subject: Re: [Xenomai] IMX6 Quad inconsistent lock state List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix Cc: xenomai@xenomai.org On Wed, Feb 03, 2016 at 02:31:18AM +0100, Gilles Chanteperdrix wrote: > On Tue, Feb 02, 2016 at 07:21:35PM -0600, Michael Welling wrote: > > On Wed, Feb 03, 2016 at 01:43:07AM +0100, Gilles Chanteperdrix wrote: > > > On Tue, Feb 02, 2016 at 06:32:12PM -0600, Michael Welling wrote: > > > > On Tue, Feb 02, 2016 at 09:59:45PM +0100, Gilles Chanteperdrix wrote: > > > > > On Tue, Feb 02, 2016 at 02:35:39PM -0600, Michael Welling wrote: > > > > > > On Tue, Feb 02, 2016 at 09:02:35PM +0100, Gilles Chanteperdrix wrote: > > > > > > > On Tue, Feb 02, 2016 at 01:53:55PM -0600, Michael Welling wrote: > > > > > > > > The kernel otherwise appears to be functional. > > > > > > > > How do I fix this? > > > > > > > > > > > > > > Disable CONFIG_TRACE_IRQFLAGS. This means disabling CONFIG_LOCKDEP too. > > > > > > > > > > > > Ah. I had to trace back the dependencies and found that I had CONFIG_PROVE_LOCKING > > > > > > and CONFIG_DEBUG_LOCK_ALLOC selected. > > > > > > > > > > > > Unselecting those made the warning go away. Good enough for me. > > > > > > > > > > > > Thanks! > > > > > > > > > > > > Next up is getting the rtdm driver modules to build. > > > > > > > > > > > > Here is the error output without the UART driver selected: > > > > > > ERROR: "__ipipe_smp_key" [drivers/xenomai/net/stack/rtmac/tdma/tdma.ko] undefined! > > > > > > ERROR: "__ipipe_smp_key" [drivers/xenomai/ipc/xeno_rtipc.ko] undefined! > > > > > > ERROR: "__ipipe_smp_key" [drivers/xenomai/can/xeno_can.ko] undefined! > > > > > > > > > > An EXPORT_SYMBOL is missing in arch/arm/kernel/ipipe.c. Or you can > > > > > disable CONFIG_SMP_ON_UP. > > > > > > > > Yeah I figured this one out. > > > > > > Ok. On my side I believe I figured why the build-test does not > > > reproduce this issue: it has CONFIG_JUMP_LABEL disabled, which does > > > not really make sense with CONFIG_SMP_ON_UP and Xenomai, so I > > > enabled the option, and next time the build-test runs, we should > > > observe the compilation error you got. > > > > My configuration also has CONFIG_JUMP_LABEL disabled. > > > > I am likely using a module for something you are not. > > the tested configuration has tdma enabled as a module. Maybe you are > not using I-pipe path version ipipe-core-3.18.20-arm-6 ? I am using the following: xenomai-3/kernel/cobalt/arch/arm/patches/ipipe-core-3.18.20-arm-6.patch > -- > Gilles. > https://click-hack.org