From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, NetDev <netdev@vger.kernel.org>,
linux-acpi <linux-acpi@vger.kernel.org>,
tglx@tglx.de, Theodore Ts'o <tytso@mit.edu>,
linux-ide@vger.kernel.org
Subject: Re: Top kernel oopses/warnings for the week of October 7th, 2008
Date: Tue, 7 Oct 2008 22:13:14 +0200 [thread overview]
Message-ID: <200810072213.16103.rjw@sisk.pl> (raw)
In-Reply-To: <48EBBE15.9030905@linux.intel.com>
On Tuesday, 7 of October 2008, Arjan van de Ven wrote:
>
> This week, a total of 3340 oopses and warnings have been reported,
> compared to 3022 reports in the previous week.
> As with last week, this report only covers kernels 2.6.26 and later.
>
>
>
> Per file statistics
> 722 net/sched/sch_generic.c
> 206 fs/jbd/journal.c
> 178 external/utrace
> 131 drivers/base/power/main.c
> 104 drivers/ata/libata-sff.c
> 104 include/linux/pagemap.h
> 96 kernel/timer.c
> 62 fs/ext3/super.c
> 61 external/fireglx/binary (P)
> 61 drivers/usb/serial/usb-serial.c
> 61 net/core/dev.c
>
>
> Unsolved issues
> ===============
>
> Rank 1: dev_watchdog (warning)
> Reported 431 times (1363 total reports)
> Network TX watchdog timeouts for unidentified NICs. 2.6.27-rc7+ will identify the NIC.
> More info: http://www.kerneloops.org/searchweek.php?search=dev_watchdog
> The general top 10 distribution over the identified cases is like this:
>
> count | guilty
> -------+---------------------------
> 390 | dev_watchdog(sis900)
> 114 | dev_watchdog(usbnet)
> 102 | dev_watchdog(via-rhine)
> 99 | dev_watchdog(8390)
> 47 | dev_watchdog(8139too)
> 44 | dev_watchdog(orinoco)
> 40 | dev_watchdog(r8169)
> 26 | dev_watchdog(3c59x)
> 17 | dev_watchdog(forcedeth)
> 15 | dev_watchdog(fealnx)
>
>
> Rank 3: journal_update_superblock (warning)
> Reported 202 times (4509 total reports)
> Likely caused by the user removing a USB stick while mounted
> Ted has a patch to fix this; queued for 2.6.28
> This warning was last seen in version 2.6.27-rc8-git4, and first seen in 2.6.24-rc6-git1.
> More info: http://www.kerneloops.org/searchweek.php?search=journal_update_superblock
>
> Rank 4: utrace_control (oops)
> Reported 166 times (1001 total reports)
> [fedora] Fedora merged a broken utrace patch
> This oops was last seen in version 2.6.26.5, and first seen in 2.6.26.1.
> More info: http://www.kerneloops.org/searchweek.php?search=utrace_control
>
> Rank 5: dev_watchdog(sis900) (warning)
> Reported 135 times (390 total reports)
> This warning was last seen in version 2.6.27-rc8-git4, and first seen in 2.6.26-rc4-git2.
> More info: http://www.kerneloops.org/searchweek.php?search=dev_watchdog(sis900)
>
> Rank 7: lock_page (warning)
> Reported 104 times (150 total reports)
> The hwclock program disables interrupts from userspace, and then hits a pagefault.
> The new diagnostics do a WARN_ON for faults-with-interrupts-off, and trap this.
> This warning was last seen in version 2.6.27-rc8-git7, and first seen in 2.6.27-rc1-git2.
> More info: http://www.kerneloops.org/searchweek.php?search=lock_page
>
> Rank 8: run_timer_softirq (oops)
> Reported 83 times (301 total reports)
> softlockup; likely fixed by the timer cleanups done by Thomas
> This oops was last seen in version 2.6.27-rc1-git4, and first seen in 2.6.25.
> More info: http://www.kerneloops.org/searchweek.php?search=run_timer_softirq
>
> Rank 9: device_pm_add (warning)
> Reported 81 times (323 total reports)
> Drivers with suspect suspend/resume logic; a patch is queued for 2.6.28 to identify
> which drivers are involved.
> This warning was last seen in version 2.6.27-rc4, and first seen in 2.6.26-rc5.
> More info: http://www.kerneloops.org/searchweek.php?search=device_pm_add
This should have been fixed by:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=f5a6d958b5d0a10e7e7a9dee1862fb31d08c6d26
Thanks,
Rafael
next prev parent reply other threads:[~2008-10-07 20:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 19:52 Top kernel oopses/warnings for the week of October 7th, 2008 Arjan van de Ven
2008-10-07 20:13 ` Rafael J. Wysocki [this message]
2008-10-07 20:16 ` Ingo Molnar
2008-10-07 20:37 ` Rafael J. Wysocki
2008-10-07 22:58 ` Alan Cox
2008-10-07 23:08 ` David Miller
2008-10-08 9:06 ` Rafael J. Wysocki
2008-10-08 9:21 ` Ingo Molnar
2008-10-08 12:43 ` Rafael J. Wysocki
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=200810072213.16103.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=tglx@tglx.de \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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).