lkml.org 
[lkml]   [2006]   [Jul]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Automatic Kernel Bug Report
On 7/10/06, Pavel Machek <pavel@ucw.cz> wrote:
> Hi!

Hi ! =)

>
> Well, unless we have some volunteer to go through the bugreports and
> sort them/kill the invalid ones/etc... this is going to do more harm
> than good.

As I told before, I wouldn't care to do that, as long as I know that
it is actually being used (and useful). The system (at the server
side) could automatically route some reports (mark them as "tainted
modules detected", etc, that sort of mechanical stuff), and according
to the frequency of certain bugs, I could check if they are actually
real bugs. If so, they get reported here on LKML. Since we can expect,
maybe, dozens of thousands of reports per week, wouldn't be hard to
distinct between real bugs, etc (if we use frequency as a marker). For
example, if the number of reports on Suspend2 get risen up sensitively
on some just-released kernel, this means that something that was added
isn't working (so here comes the personal debug, where we can see if
it's a new bug or a regression)

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@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-07-10 19:43    [W:0.073 / U:1.844 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site