From: Arjan van de Ven <arjan@linux.intel.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
NetDev <netdev@vger.kernel.org>
Subject: Oops/Warning report for the week of March 28th 2008
Date: Fri, 28 Mar 2008 11:55:22 -0700 [thread overview]
Message-ID: <47ED3F1A.1090101@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)
This week, a total of 538 oopses and warnings have been reported,
compared to 169 reports in the previous week.
Rank 1: input_release_device
This appears to be a regression in 2.6.25; the first reports show up in 2.6.25-rc2
Often a warning at kernel/mutex.c:134 (mutex_lock_nested), but some oopses too
Reported 161 times (261 total reports)... this is 30% of the total reports this week!
The reports are all in the fput() path via ev_release
More info: http://www.kerneloops.org/searchweek.php?search=input_release_device
Rank 2: set_dentry_child_flags
The standard inotify warning... only seen upto 2.6.24
Assumed fixed in 2.6.25
Reported 49 times (493 total reports)
More info: http://www.kerneloops.org/searchweek.php?search=set_dentry_child_flags
Rank 3: __ieee80211_rx
Warning at net/mac80211/rx.c:2184 __ieee80211_rx (newer-than-mainline mac80211)
Reported 29 times (73 total reports)
More info: http://www.kerneloops.org/searchweek.php?search=__ieee80211_rx
Rank 4: radeon_vblank_crtc_set
This is probably a Fedora-special experimental Radeon driver
Reported 23 times (28 total reports)
More info: http://www.kerneloops.org/searchweek.php?search=radeon_vblank_crtc_set
Rank 5: do_sys_open
Oops because a driver returns "1" and not "-1" as error code
Seen with the nouveau driver, not in mainline yet.
Reported 21 times (39 total reports)
More info: http://www.kerneloops.org/searchweek.php?search=do_sys_open
Rank 6: uvc_get_video_ctrl
The uvc driver is not in mainline
Reported 19 times (84 total reports)
More info: http://www.kerneloops.org/searchweek.php?search=uvc_get_video_ctrl
Rank 7: __register_sysctl_paths
Seen with proprietary drivers only
Reported 16 times (186 total reports)
More info: http://www.kerneloops.org/searchweek.php?search=__register_sysctl_paths
Rank 8: tcp_ack
Warning at net/ipv4/tcp_input.c:2532 tcp_ack
Reported 15 times (87 total reports)
More info: http://www.kerneloops.org/searchweek.php?search=tcp_ack
Rank 9: sysctl_check_lookup
This seems to be a bug in parport_device_proc_register()
Reported 14 times (62 total reports)
More info: http://www.kerneloops.org/searchweek.php?search=sysctl_check_lookup
Rank 10: mark_buffer_dirty
This is an old friend, started in 2.6.24 and is still with us today.
Often but not exclusively during unmounting of a filesystem
Reported 12 times (39 total reports)
More info: http://www.kerneloops.org/searchweek.php?search=mark_buffer_dirty
next reply other threads:[~2008-03-28 18:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 18:55 Arjan van de Ven [this message]
2008-03-28 20:21 ` Oops/Warning report for the week of March 28th 2008 Linus Torvalds
2008-03-28 20:51 ` Linus Torvalds
2008-03-28 21:01 ` Johannes Berg
2008-03-28 21:24 ` Linus Torvalds
2008-03-28 21:43 ` Johannes Berg
2008-03-28 22:01 ` Linus Torvalds
2008-03-28 22:14 ` Jiri Kosina
2008-03-28 22:14 ` Johannes Berg
2008-03-28 21:16 ` Dmitry Torokhov
2008-03-29 12:20 ` Björn Steinbrink
2008-03-28 20:57 ` Björn Steinbrink
2008-03-28 22:33 ` Arjan van de Ven
2008-03-28 22:58 ` 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=47ED3F1A.1090101@linux.intel.com \
--to=arjan@linux.intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.