All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Dave Jones <davej@redhat.com>
Cc: "Antonino A. Daplas" <adaplas@gmail.com>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>,
	Pavel Emelianov <xemul@sw.ru>
Subject: Re: 2.6.21-rc7-mm1: Oops and Gnome desktop freezes
Date: Wed, 25 Apr 2007 12:54:06 -0700	[thread overview]
Message-ID: <20070425125406.9253bd49.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070425193511.GB3006@redhat.com>

On Wed, 25 Apr 2007 15:35:11 -0400 Dave Jones <davej@redhat.com> wrote:

> On Wed, Apr 25, 2007 at 12:12:42PM -0700, Andrew Morton wrote:
>   > > EIP:    0060:[<c014c469>]    Tainted: G      D VLI
>  > 
>  > For some reason all oopses (and boy there are a lot of them) are being
>  > described as tainted.
> 
> What's "D" though ?

Pretty flattering, if it's on a scale of A-F.

>  grep -i taint broken-out/* doesn't show
> -mm adding any new flags, and I don't see it present in mainline.

report-that-kernel-is-tainted-if-there-were-an-oops-before.patch:

+  8: 'D' if a kernel has died recently, i.e. there was an OOPS or BUG
+      before, ' ' otherwise. This is useful when seeing the calltrace
+      from SysRq-P output.

I suspect that patch has gone bad and it's reporting 'D' for the very first
oops, which it shouldn't do.

But I haven't checked that theory.

  parent reply	other threads:[~2007-04-25 19:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-25 14:49 2.6.21-rc7-mm1: Oops and Gnome desktop freezes Antonino A. Daplas
2007-04-25 19:12 ` Andrew Morton
2007-04-25 19:35   ` Dave Jones
2007-04-25 19:42     ` Dave Jones
2007-04-25 19:54     ` Andrew Morton [this message]
2007-04-25 20:05   ` Randy Dunlap
2007-04-25 23:29   ` Antonino A. Daplas
2007-04-26  3:34 ` Dan Kruchinin
2007-04-26  9:23   ` Antonino A. Daplas

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=20070425125406.9253bd49.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=adaplas@gmail.com \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xemul@sw.ru \
    /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.