From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation>,
protasnb@gmail.com
Subject: Re: Top kernel oopses/warnings this week
Date: Sat, 15 Dec 2007 16:49:05 +0100 [thread overview]
Message-ID: <4763F771.10105@s5r6.in-berlin.de> (raw)
In-Reply-To: <4762CF8C.90808@linux.intel.com>
Arjan van de Ven wrote:
> The http://www.kerneloops.org website collects kernel oops and warning
> reports from various mailing lists and bugzillas;
A few comments:
Report counts may be too high due to duplicate recognition of the very
same report.¹
Reports against 2.6.X-rcY-mmZ are listed in the same category as reports
against 2.6.X-rcY. To distinguish -mm reports from vanilla reports, one
has to look into the details of each bug entry.¹
A general weakness is that it is ultimately impossible to know whether a
report was against an unpatched kernel, unless one drills down to the
individual mailinglist threads.
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.
¹) example: http://www.kerneloops.org/oops.php?number=2335
--
Stefan Richter
-=====-=-=== ==-- -====
http://arcgraph.de/sr/
next prev parent reply other threads:[~2007-12-15 15:49 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 18:46 Top kernel oopses/warnings this week Arjan van de Ven
2007-12-14 18:58 ` Dave Jones
2007-12-14 21:57 ` Andrew Morton
2007-12-14 22:25 ` Natalie Protasevich
2007-12-15 0:38 ` Arjan van de Ven
2007-12-14 22:12 ` Jon Masters
2007-12-15 15:49 ` Stefan Richter [this message]
2007-12-15 18:21 ` Arjan van de Ven
2007-12-15 19:44 ` Stefan Richter
2007-12-17 18:25 ` Zach Brown
2007-12-17 18:41 ` Arjan van de Ven
2007-12-17 2:51 ` Dave Jones
2007-12-17 12:33 ` Jon Masters
2007-12-17 13:13 ` Stefan Richter
2007-12-17 16:40 ` Arjan van de Ven
2007-12-17 17:23 ` Ingo Molnar
2007-12-17 21:36 ` Arjan van de Ven
2007-12-17 21:58 ` Theodore Tso
2007-12-17 22:58 ` Tony Luck
2007-12-17 23:17 ` Arjan van de Ven
2007-12-17 23:26 ` Tony Luck
2007-12-17 23:47 ` Arjan van de Ven
2007-12-18 0:21 ` Linus Torvalds
2007-12-18 0:39 ` Arjan van de Ven
2007-12-18 2:31 ` Theodore Tso
2007-12-18 6:58 ` Arjan van de Ven
2007-12-18 17:53 ` Matt Mackall
2007-12-18 18:28 ` Theodore Tso
2007-12-18 18:45 ` Linus Torvalds
2007-12-18 10:11 ` Jon Masters
2007-12-18 18:06 ` Arjan van de Ven
2007-12-18 18:13 ` Matt Mackall
2007-12-18 18:19 ` Arjan van de Ven
2007-12-18 17:48 ` Matt Mackall
2007-12-18 23:37 ` Arjan van de Ven
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=4763F771.10105@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=protasnb@gmail.com \
--cc=torvalds@linux-foundation \
/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