Subject: Re: Top kernel oopses/warnings this week
From: Jon Masters <jcm@redhat.com>
To: Dave Jones <davej@redhat.com>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
       Arjan van de Ven <arjan@linux.intel.com>, linux-kernel@vger.kernel.org,
       Andrew Morton <akpm@linux-foundation.org>,
       Linus Torvalds <torvalds@linux-foundation>, protasnb@gmail.com
In-Reply-To: <20071217025129.GA12815@redhat.com>
References: <4762CF8C.90808@linux.intel.com>
	 <4763F771.10105@s5r6.in-berlin.de>  <20071217025129.GA12815@redhat.com>
Content-Type: text/plain
Organization: Red Hat, Inc.
Date: Mon, 17 Dec 2007 07:33:34 -0500
Message-Id: <1197894814.18713.36.camel@perihelion>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 968
Lines: 26


On Sun, 2007-12-16 at 21:51 -0500, Dave Jones wrote:
> On Sat, Dec 15, 2007 at 04:49:05PM +0100, Stefan Richter wrote:
>  
>  > Reports about tainted kernels have arguably less value.  It would be
>  > good to hide such reports until a report of the same oops in an
>  > untainted kernel was found.
>  
> I disagree with this.  It's useful to have a "we've seen this before,
> and every time, it was tainted with xyz module" datapoint, especially
> if no untainted copies of that oops turn up.

+1

In fact, that's even more useful in many cases, if it helps demonstrate
that the oops is associated with a particular buggy binary driver. I can
see a lot of potentially interesting statistics coming from that too.

Jon.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/