From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: imx6 wand board lockdep warnings on boot
Date: Wed, 29 Jan 2014 22:17:08 +0000 [thread overview]
Message-ID: <20140129221708.GV15937@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAOesGMiP2nzrACVr4xy5NTfKFOEwkyGdCU2_ZFYRNhv8B_ncPA@mail.gmail.com>
On Wed, Jan 29, 2014 at 01:58:51PM -0800, Olof Johansson wrote:
> On Wed, Jan 29, 2014 at 1:52 PM, Kevin Hilman <khilman@linaro.org> wrote:
> > For awhile now, the wand boards have had some noisy lockdep warnings
> > during boot, but I'm not sure if anyone is looking into them. I see
> > it on the wand-solo and wand-quad, but not the dual. Full boot logs
> > for all three are attached from v3.13.
>
> Yeah, this one is known -- Russell has mentioned it in the past too.
>
> This reminds me, I've been meaning to turn on lockdep on all defconfig
> builds so that we get coverage on more platforms, but I haven't done
> it yet.
It's really worth considering that - as well as building the defconfigs -
that the defconfigs are built with the kernel debugging options forced on
so that things like locking problems are found. Obviously, debug info is
one option you wouldn't want to turn on, because for a build+boot test
system, it just makes the objects unnecessarily larger and wastes disk
space (unless of course you intend to use the debug info.)
I've just modified all my oldconfig builds to have many of the debug
stuff enabled.
--
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation
in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
Estimate before purchase was "up to 13.2Mbit".
next prev parent reply other threads:[~2014-01-29 22:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 21:52 imx6 wand board lockdep warnings on boot Kevin Hilman
2014-01-29 21:58 ` Olof Johansson
2014-01-29 22:17 ` Russell King - ARM Linux [this message]
2014-01-29 22:20 ` Fabio Estevam
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=20140129221708.GV15937@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox