netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@linux.intel.com>
To: linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	netdev@vger.kernel.org
Subject: Top 9 kernel oopses/warnings for the week of December 29th, 2007
Date: Sat, 29 Dec 2007 12:34:39 +0100	[thread overview]
Message-ID: <477630CF.5070609@linux.intel.com> (raw)

The http://www.kerneloops.org website collects kernel oops and
warning reports from various mailing lists and bugzillas as well as
with a client users can install to auto-submit oopses.
Below is a top 10 list of the oopses collected in the last 7 days.
(Reports prior to 2.6.23 have been omitted in collecting the top 10)

It has been a quiet week due to the holidays, only 55 oops traces
have been collected.

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
	Reported 5 times
	Only seen in 2.6.24-rc6 so far
	Johannes has diagnosed this as a driver bug in the iwlwifi drivers
	More info: http://www.kerneloops.org/search.php?search=__ieee80211_rx
	
Rank 3: rb_erase
	Null pointer dereference
	Reported 4 times
	Only seen in 2.6.24-rc6 so far
	(Note: the reported removed the oops end marker manually; may be duplicate reports)
	More info: http://www.kerneloops.org/guilty.php?version=2.6.24-rc6&guilty=rb_erase&start=1574400&end=1574400

Rank 4: remove_proc_entry
	Warning at fs/proc/generic.c:736
	Reported 4 times for 2.6.24-rc4 and rc5 (Mandrake)
	Seems to be a module unload issue
	More info: http://www.kerneloops.org/search.php?search=remove_proc_entry
	
Rank 5: aes_encrypt
	Invalid kernel pointer oops
	Reported 2 times for 2.6.23.11
	More info: http://www.kerneloops.org/search.php?search=aes_encrypt
	
Rank 6: cascade
	BUG statement at kernel/timer.c:606
	Reported 2 times for 2.6.23 (Gentoo)
	More info: http://www.kerneloops.org/search.php?search=cascade
	
Rank 7: kref_put
	Kernel paging request
	Reported 2 times, only for 2.6.24-rc6-mm1
	Diagnosed as a bug in the md-subsystem, patch available
	More info: http://www.kerneloops.org/search.php?search=kref_put
	More info: http://article.gmane.org/gmane.linux.kernel/618056
	
Rank 8: device_release
	Warning at drivers/base/core.c:107
	Reported 2 times last week, 6 incidents total
	Seems to be a bug in the MTD physmap driver and the hgafb driver
	More info: http://article.gmane.org/gmane.linux.kernel/618076
	More info: http://article.gmane.org/gmane.linux.kernel/618076
	
Rank 9: mutex_lock
	Null pointer dereference
	Reported 2 times, of which one was a duplicate report
	Seems to be related to running PPP over a bluetooth link
	More info: http://www.kerneloops.org/guilty.php?version=2.6.24-rc6&guilty=mutex_lock&start=1574400&end=1574400
	

kerneloops.org news:
* As of 2.6.24-rc6, oopses have a unique identifier which makes it possible to filter out duplicate
   reports of (and replies to) the same oops. Unfortunately some reporters remove this line from
   their reports to lkml.

             reply	other threads:[~2007-12-29 11:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-29 11:34 Arjan van de Ven [this message]
2007-12-29 13:17 ` Top 9 kernel oopses/warnings for the week of December 29th, 2007 Ingo Molnar
2007-12-29 19:18 ` Linus Torvalds
2007-12-29 19:31   ` Arjan van de Ven
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=477630CF.5070609@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).