[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200810072213.16103.rjw@sisk.pl>
Date: Tue, 7 Oct 2008 22:13:14 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Arjan van de Ven <arjan@...ux.intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>, NetDev <netdev@...r.kernel.org>,
"linux-acpi" <linux-acpi@...r.kernel.org>, tglx@...x.de,
"Theodore Ts'o" <tytso@....edu>, linux-ide@...r.kernel.org
Subject: Re: Top kernel oopses/warnings for the week of October 7th, 2008
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists