From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Michael Welling <mwelling@ieee.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] IMX6 Quad inconsistent lock state
Date: Tue, 2 Feb 2016 23:08:48 +0100 [thread overview]
Message-ID: <20160202220848.GD29937@hermes.click-hack.org> (raw)
In-Reply-To: <20160202203539.GD27804@deathstar>
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!
>
What version of the I-pipe are you using? The case SMP_ON_UP + rtnet
tdma on imx6 is build-tested here:
https://xenomai.org//build-test-stable/imx_v6_v7/3.18-arm-linux-gnueabihf-gcc-4.9.3/log.html
and does not seem to produce any error with ipipe-core-3.18.20-arm-6
If that is indeed the version of the patch you are testing, can you
provide your .config ?
Regards.
--
Gilles.
https://click-hack.org
prev parent reply other threads:[~2016-02-02 22:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 19:53 [Xenomai] IMX6 Quad inconsistent lock state Michael Welling
2016-02-02 20:02 ` Gilles Chanteperdrix
2016-02-02 20:35 ` Michael Welling
2016-02-02 20:59 ` Gilles Chanteperdrix
2016-02-03 0:32 ` Michael Welling
2016-02-03 0:43 ` Gilles Chanteperdrix
2016-02-03 1:21 ` Michael Welling
2016-02-03 1:31 ` Gilles Chanteperdrix
2016-02-03 1:36 ` Michael Welling
2016-02-03 1:37 ` Gilles Chanteperdrix
2016-02-03 1:42 ` Michael Welling
2016-02-03 1:51 ` Gilles Chanteperdrix
2016-02-03 14:47 ` Michael Welling
2016-02-03 14:53 ` Gilles Chanteperdrix
2016-02-08 20:42 ` Gilles Chanteperdrix
2016-02-02 22:08 ` Gilles Chanteperdrix [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160202220848.GD29937@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=mwelling@ieee.org \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.