From: Johannes Berg <johannes@sipsolutions.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Arend van Spriel <arend@broadcom.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: unexpected taint message
Date: Fri, 16 Dec 2011 14:58:59 +0100 [thread overview]
Message-ID: <1324043939.3429.2.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4EEB4D61.80602@lwfinger.net> (sfid-20111216_145414_221850_EED1E4DE)
On Fri, 2011-12-16 at 07:53 -0600, Larry Finger wrote:
> On 12/16/2011 06:30 AM, Johannes Berg wrote:
> > On Fri, 2011-12-16 at 10:27 +0100, Arend van Spriel wrote:
> >> To whoever may know,
> >>
> >> Upon loading our driver module I get the following message:
> >>
> >> kernel: [ 344.805106] Disabling lock debugging due to kernel taint
> >>
> >> What exactly are the criteria for tainting? Our driver locking strategy
> >> is something we want to refactor and having lock debugging during that
> >> transition may be a life safer.
> >
> > cat /proc/sys/kernel/tainted
>
> Please note that Documentation/sysctl/kernel.txt is missing the explanation for
> two bits in the value printed:
>
> 2048 - The system is working around a severe firmware bug.
> 4096 - An out-of-tree module has been loaded.
>
> On my system, bit 4096 is set due to loading the VirtualBox module, which
> disables lock debugging lock debugging. I suspect that loading VMware would
> cause the same condition.
Hmm. I wish OOT didn't disable lockdep, we do a lot of development with
modules OOT because the turnaround is faster/easier (for not so
experienced developers). Worst case we can patch it out of the base
kernel I guess...
johannes
next prev parent reply other threads:[~2011-12-16 13:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 9:27 Arend van Spriel
2011-12-16 9:29 ` Daniel Baluta
2011-12-16 10:03 ` Arend van Spriel
2011-12-16 12:30 ` Johannes Berg
2011-12-16 13:53 ` Larry Finger
2011-12-16 13:58 ` Johannes Berg [this message]
2011-12-16 14:13 ` Larry Finger
2011-12-16 14:20 ` Johannes Berg
2011-12-16 14:49 ` Larry Finger
2011-12-16 14:51 ` Johannes Berg
2011-12-16 14:48 ` Nick Bowler
2011-12-16 14:57 ` Larry Finger
2011-12-16 14:58 ` Johannes Berg
2011-12-16 14:00 ` Arend van Spriel
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=1324043939.3429.2.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Larry.Finger@lwfinger.net \
--cc=arend@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.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
Powered by JetHome