From: Marc Ballarin <Ballarin.Marc@gmx.de>
To: Antoine Martin <antoine@nagafix.co.uk>
Cc: jmorris@namei.org, linux-kernel@vger.kernel.org, sds@epoch.ncsc.mil
Subject: Re: preempt with selinux NULL pointer dereference
Date: Fri, 5 Aug 2005 20:09:45 +0200 [thread overview]
Message-ID: <20050805200945.2bc1f57e.Ballarin.Marc@gmx.de> (raw)
In-Reply-To: <1123260373.4471.8.camel@dhcp-192-168-22-217.internal>
On Fri, 05 Aug 2005 17:46:13 +0100
Antoine Martin <antoine@nagafix.co.uk> wrote:
> > > [ 4788.218995] Pid: 19002, comm: ssh Tainted: G M 2.6.13-rc5
> >
> > Which of your modules is non-GPL and can you please remove them and see if
> > there's still a problem?
> Hmm. I occasionally use out-of-tree drivers (wlan cards mainly) so I
> thought these could be the culprit, but all the above are in the source
> tree (I keep the others out):
>From Documentation/oops-tracing.txt:
'G' if all modules loaded have a GPL or compatible license, 'P' if
any proprietary module has been loaded.
...
In other words, your kernel is tainted, but all modules are GPL.
See also the check in panic.c:
...
tainted & TAINT_PROPRIETARY_MODULE ? 'P' : 'G',
...
It seems that yout kernel was tainted by a machine check exception (MCE).
This should be visible in dmesg somewhere, and might indicate a hardware
problem.
Regards
prev parent reply other threads:[~2005-08-05 19:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 9:39 preempt with selinux NULL pointer dereference antoine
2005-08-05 14:25 ` James Morris
2005-08-05 16:46 ` Antoine Martin
2005-08-05 17:10 ` James Morris
2005-08-05 17:19 ` linux-os (Dick Johnson)
2005-08-05 18:50 ` Dave Jones
2005-08-05 19:30 ` linux-os (Dick Johnson)
2005-08-05 18:09 ` Marc Ballarin [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=20050805200945.2bc1f57e.Ballarin.Marc@gmx.de \
--to=ballarin.marc@gmx.de \
--cc=antoine@nagafix.co.uk \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sds@epoch.ncsc.mil \
/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