Re: Automatic Kernel Bug Report

[Daniel Bonekeeper]

On 7/10/06, Lee Revell <rlrevell@xxxxxxxxxxx> wrote:
> On Mon, 2006-07-10 at 18:05 -0400, Daniel Bonekeeper wrote:
> > That's a good example. Another example: a little while ago
> > (http://lkml.org/lkml/2006/7/1/70) Daniel Drake from Gentoo was
> > reporting a problem where page_mapcount(page) was getting negative. As
> > it turned out, it was related with a nVidia proprietary driver that
> > the machine was running. With the system, we just needed to search for
> > "Eeek! page_mapcount(page) went negative! (-1)" on kernels 2.6.16.19
> > (maybe too generic), and he would see that lots of people reporting
> > that has, between other things, nVidia drivers running. It's already a
> > clue on where to start looking for. The same applies for lots of other
> > stuff.
>
> That sounds backwards to me - any kernel bug reporting system should
> immediately discard bug reports with the nvidia driver loaded, as such a
> kernel is not debuggable.

Our job is to do kernel, and anything related to it should not be discarded.
The system has to have the flexibility to provide the same information
ignoring tainted configurations, if it's that what you need. ("provide
mechanism, not policy")

Daniel

--
What this world needs is a good five-dollar plasma weapon.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/