netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Arjan van de Ven <arjan@linux.intel.com>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	Kevin Winchester <kjwinchester@gmail.com>,
	"J. Bruce Fields" <bfields@fieldses.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	NetDev <netdev@vger.kernel.org>
Subject: Re: Top 10 kernel oopses for the week ending January 5th, 2008
Date: Tue, 8 Jan 2008 23:56:27 +0100	[thread overview]
Message-ID: <200801082356.28258.rjw@sisk.pl> (raw)
In-Reply-To: <alpine.LFD.1.00.0801081126200.3148@woody.linux-foundation.org>

On Tuesday, 8 of January 2008, Linus Torvalds wrote:
> 
> On Tue, 8 Jan 2008, Arjan van de Ven wrote:
> > 
> > ok done; I had to fizzle a bit because some things aren't *exactly* a 
> > BUG() statement but I track them anyway (things like the "sleeping in 
> > invalid context" check), so I had to somewhat arbitrarily assign 
> > categories for those. I might fine tune these over time some; if you or 
> > someone else sees problems with categorization please let me know
> 
> Looking good. I wonder if we could also have some way to cross-ref these 
> things with the regression list (notably try to get pointers to them in 
> the regression list). 

I'm thinking about that, but haven't invented any automated solution yet.
I only can manually add references to kerneloops.org, for now.

Greetings,
Rafael

  reply	other threads:[~2008-01-08 22:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-05 21:06 Top 10 kernel oopses for the week ending January 5th, 2008 Arjan van de Ven
2008-01-05 21:26 ` Al Viro
2008-01-05 21:39 ` Al Viro
2008-01-07 17:44   ` J. Bruce Fields
2008-01-08  1:19     ` Kevin Winchester
2008-01-08  3:26       ` Linus Torvalds
2008-01-08  5:59         ` Al Viro
2008-01-08  7:33           ` Jarek Poplawski
2008-01-10  4:13           ` Neil Brown
2008-01-10  5:53             ` Al Viro
2008-01-14  1:36               ` Neil Brown
2008-01-08 16:14         ` Randy Dunlap
2008-01-08 17:42           ` Arjan van de Ven
2008-01-08 18:08             ` Linus Torvalds
2008-01-08 18:16               ` Arjan van de Ven
2008-01-08 18:27                 ` Linus Torvalds
2008-01-08 19:05                   ` Arjan van de Ven
2008-01-08 19:31                     ` Linus Torvalds
2008-01-08 22:56                       ` Rafael J. Wysocki [this message]
2008-01-08 17:08         ` Andi Kleen
2008-01-06  3:30 ` Andi Kleen
2008-01-06  3:31   ` Arjan van de Ven
2008-01-06  3:50     ` Andi Kleen
2008-01-09 14:12 ` Johannes Berg
2008-01-09 15:28   ` 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=200801082356.28258.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@linux.intel.com \
    --cc=bfields@fieldses.org \
    --cc=kjwinchester@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).