All of lore.kernel.org
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How can I know what is tainting my kernel
Date: Tue, 15 Nov 2011 16:24:34 -0800	[thread overview]
Message-ID: <20111116002434.GB9274@kroah.com> (raw)
In-Reply-To: <20111113184711.GA1630@debian.debian>

On Sun, Nov 13, 2011 at 07:47:11PM +0100, Jonathan Neusch?fer wrote:
> On Sat, Nov 12, 2011 at 04:39:59PM -0800, Greg KH wrote:
> > On Sun, Nov 13, 2011 at 01:18:47AM +0100, Jonathan Neusch?fer wrote:
> > > On Sat, Nov 12, 2011 at 03:49:53PM -0800, Greg KH wrote:
> > > > On Sat, Nov 12, 2011 at 08:23:32PM -0200, Daniel Hilst Selli wrote:
> > > > > Two questions about taint system..
> > > > > 
> > > > > 1. I have a installation of archlinux with kernel 3.0, just after boot I 
> > > > > cat /proc/sys/kenrel/tainted and receives 1024, but cat 
> > > > > /var/log/messages | grep -i taint gives me no output. How can I know 
> > > > > what is tainting my kernel?
> > > > 
> > > > Look for the "BIOS is broken..." message, 1024 is
> > > > TAINT_FIRMWARE_WORKAROUND.
> > > 
> > > No, it's TAINT_CRAP.
> > 
> > Really?  As the person who added TAINT_CRAP to the kernel, for some
> > foolish reason I thought that was the 10th bit, not the 11th bit, which
> > would be 1024, right?
> 
> It's defined as 10 in kernel.h, which makes it actually the 11th bit,
> and it's documented as 1024 in Documentation/sysctl/kernel.txt.

Doh, you are right, I was thinking that set_bit() started with 1 as the
rightmost bit, when that would be 0.

greg k-h

      reply	other threads:[~2011-11-16  0:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-12 22:23 How can I know what is tainting my kernel Daniel Hilst Selli
2011-11-12 23:49 ` Greg KH
2011-11-13  0:18   ` Jonathan Neuschäfer
2011-11-13  0:39     ` Greg KH
2011-11-13 18:47       ` Jonathan Neuschäfer
2011-11-16  0:24         ` Greg KH [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=20111116002434.GB9274@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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.