netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@linux.intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	netdev@vger.kernel.org
Subject: Re: Top 9 kernel oopses/warnings for the week of December 29th, 2007
Date: Sat, 29 Dec 2007 20:31:08 +0100	[thread overview]
Message-ID: <4776A07C.5090806@linux.intel.com> (raw)
In-Reply-To: <alpine.LFD.0.9999.0712291116190.2778@woody.linux-foundation.org>

Linus Torvalds wrote:
> 
> On Sat, 29 Dec 2007, Arjan van de Ven wrote:
>> It has been a quiet week due to the holidays, only 55 oops traces
>> have been collected.
> 
> This would be more useful if it was more readable. As it is, you seem to 
> have some formatting errors in your automation, where the things are 
> incorrectly grouped:

this is manual made; I'll blame thunderbird for now

let me see if I can send it again without corruption

> 
>> Rank 1: sysctl_head_finish
>> 	sysctl table check failed
>> 	Reported 7 times
>> 	Only reported for the proprietary madwifi driver
>> 	More info: http://www.kerneloops.org/search.php?search=sysctl_head_finish
>> 	Rank 2: __ieee80211_rx
>> 	Warning at net/mac80211/rx.c:1672
> 
> ie notice how that "Rank 2" got reported as if it was part of the "Rank 1" 
> issue. 
> 
> 		Linus


  reply	other threads:[~2007-12-29 19:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-29 11:34 Top 9 kernel oopses/warnings for the week of December 29th, 2007 Arjan van de Ven
2007-12-29 13:17 ` Ingo Molnar
2007-12-29 19:18 ` Linus Torvalds
2007-12-29 19:31   ` Arjan van de Ven [this message]
2007-12-29 19:34   ` Arjan van de Ven
2007-12-29 19:52     ` Linus Torvalds
2007-12-29 21:53       ` Martin Josefsson
2007-12-29 22:21       ` Geert Uytterhoeven
2007-12-29 19:36   ` Björn Steinbrink

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=4776A07C.5090806@linux.intel.com \
    --to=arjan@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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).