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>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Kernel Warning/Oops report for the week of April 4th, 2008
Date: Fri, 04 Apr 2008 10:13:44 -0700 [thread overview]
Message-ID: <47F661C8.6000604@linux.intel.com> (raw)
As a general note, the hottest issues from last week got fixed, most of the
remaining issues are from the Fedora 9 (beta) kernels, specifically from various patches
that will otherwise go into the next merge window.
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 881 oopses and warnings have been reported,
compared to 455 reports in the previous week.
Rank 1: input_release_device
Reported 245 times (489 total reports)
This issue got fixed just before the 2.6.25-rc8 release; no sightings have been seen after that.
More info: http://www.kerneloops.org/searchweek.php?search=input_release_device
Rank 2: radeon_vblank_crtc_set
Reported 45 times (70 total reports)
This issue seems to be specific to the radeon driver in Fedora 9 (beta)
More info: http://www.kerneloops.org/searchweek.php?search=radeon_vblank_crtc_set
Rank 3: __ieee80211_rx (rt2x00)
Reported 44 times (117 total reports)
This issue is specific to the rt2x00 driver in wireless.git; it'll be important to get
this driver fixed before the 2.6.26 merge window
(The Fedora 9 beta kernels currently include wireless.git)
More info: http://www.kerneloops.org/search.php?search=__ieee80211_rx
Rank 4: sysctl_check_lookup (parport driver)
Reported 44 times (99 total reports)
This is only for 2.6.24 kernels and got fixed for 2.6.25
More info: http://www.kerneloops.org/search.php?search=sysctl_check_lookup
Rank 5: rt2x00usb_vendor_request_buff
Reported 42 times
This issue is specific to the rt2x00 driver in wireless.git; it'll be important to get
this driver fixed before the 2.6.26 merge window
More info: http://www.kerneloops.org/search.php?search=rt2x00usb_vendor_request_buff
Rank 6: rtnetlink_rcv
Reported 28 times
This issue is specific to the rt2x00 driver in wireless.git; it'll be important to get
this driver fixed before the 2.6.26 merge window
More info: http://www.kerneloops.org/search.php?search=rtnetlink_rcv
Rank 7: do_sys_open
Reported 26 times (65 total reports)
This issue is specific to the nouveau driver in Fedora 9 (beta) which returns
1 and not -1 for a few error conditions, confusing IS_ERR / PTR_ERR
More info: http://www.kerneloops.org/search.php?search=do_sys_open
Rank 8: schedule_timeout (rt2x00usb_vendor_request)
Reported 25 times (28 total reports)
This issue is specific to the rt2x00 driver in wireless.git; it'll be important to get
this driver fixed before the 2.6.26 merge window
More info: http://www.kerneloops.org/search.php?search=schedule_timeout
Rank 9: uvc_get_video_ctrl
Reported 24 times (105 total reports)
This is an out of tree driver added to the Fedora 9 (beta) kernel; this seems to be
a 64 bit specific bug
More info: http://www.kerneloops.org/search.php?search=uvc_get_video_ctrl
More info: https://bugzilla.redhat.com/show_bug.cgi?id=439643
Rank 10: set_dentry_child_flags
Reported 24 times (511 total reports)
This bug is specific to 2.6.24 and earlier and got fixed by Nick Piggin for 2.6.25
More info: http://www.kerneloops.org/search.php?search=set_dentry_child_flags
Rank 11: snd_es1968_ac97_read
Reported 24 times (38 total reports)
This is a sleeping-while-holding-a-spinlock bug;
Fix at: http://www.spinics.net/lists/kernel/msg709389.html (included in -mm)
More info: http://www.kerneloops.org/search.php?search=snd_es1968_ac97_read
reply other threads:[~2008-04-04 17:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=47F661C8.6000604@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@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