From: Arjan van de Ven <arjan@linux.intel.com>
To: Jay Cliburn <jcliburn@gmail.com>
Cc: NetDev <netdev@vger.kernel.org>
Subject: Re: oops/warning report for the week of November 26, 2008
Date: Fri, 28 Nov 2008 09:32:17 -0800 [thread overview]
Message-ID: <20081128093217.3888fb46@linux.intel.com> (raw)
In-Reply-To: <20081128111827.79b12739@osprey.hogchain.net>
On Fri, 28 Nov 2008 11:18:27 -0600
Jay Cliburn <jcliburn@gmail.com> wrote:
> [trimmed the cc list down to netdev only]
>
> > Rank 12: dev_watchdog(atl1) (oops)
> > Reported 56 times (109 total reports)
> > This oops was last seen in version 2.6.27.5, and first seen
> > in 2.6.26.6. More info:
> > http://www.kerneloops.org/searchweek.php?search=dev_watchdog(atl1)
>
> The tx timeout reports at kerneloops.org appear to be happening on a
> startling variety of network drivers (startling to me, anyway): r8169,
> atl1, atl2, sis900, cdc_ether, orinoco_cs, tg3, ne2k-pci, via-rhine,
> 8139too, ath_pci, e1000, gl620a, sky2, hso, fealnx, forcedeth;
> probably others, but I quit looking.
to be specific in counts, the data I have so far is:
count | guilty
-------+----------------------------
1599 | dev_watchdog(sis900)
1501 | dev_watchdog(r8169)
280 | dev_watchdog(via-rhine)
264 | dev_watchdog(cdc_ether)
213 | dev_watchdog(usbnet)
192 | dev_watchdog(8139too)
164 | dev_watchdog(8390)
158 | dev_watchdog(via_rhine)
129 | dev_watchdog(ne2k-pci)
122 | dev_watchdog(atl1)
102 | dev_watchdog(atl2)
101 | dev_watchdog(orinoco)
and then a long tail of sub-100, omitted to keep this mail not too
long; if anyone wants data on his/her driver not in the list, let me
know.
(please don't read too much in the word "guilty"; it's just the name of
the column in the kerneloops.org database used for identifing which
function was the prime suspect of a backtrace)
>
> Is it correct to assume all these drivers are showing symptoms of the
> poor timeout handling you mentioned in your r8169 comment, or is the
> occasional tx timeout to be expected, and the leaders in this category
> (r8169, sis900, atl1) are the only ones suffering from deficient
> timeout handling?
For me, sis900 and r8169 stand out; if you look at the data in the
table above, both of these are an order of magnitude more frequent than
the rest of the pack. ATL1 isn't doing all that bad in this regard,
although your driver is still a little higher than other popular cards
like tg3, e1000, e1000e etc. (those are all sub-50).
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2008-11-28 17:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 23:11 oops/warning report for the week of November 26, 2008 Arjan van de Ven
2008-11-27 0:05 ` Jesse Barnes
2008-11-27 11:48 ` Ingo Molnar
2008-11-27 19:42 ` Alex Chiang
2008-11-27 19:49 ` Arjan van de Ven
2008-11-27 11:52 ` Ingo Molnar
2008-11-27 17:02 ` Jesse Barnes
2008-11-27 18:01 ` Arjan van de Ven
2008-11-27 20:18 ` Ingo Molnar
2008-11-27 20:28 ` Arjan van de Ven
2008-11-27 20:47 ` Ingo Molnar
2008-11-27 20:53 ` Arjan van de Ven
2008-11-28 8:34 ` Ingo Molnar
2008-11-27 21:18 ` H. Peter Anvin
2008-11-27 21:18 ` Yinghai Lu
2008-11-27 21:42 ` H. Peter Anvin
2008-11-28 17:18 ` Jay Cliburn
2008-11-28 17:32 ` Arjan van de Ven [this message]
2008-11-28 18:36 ` Jay Cliburn
2008-11-28 18:50 ` Arjan van de Ven
2008-11-28 21:12 ` atl1 transmit timeout Was: " Jay Cliburn
2008-11-28 21:22 ` Arjan van de Ven
2008-11-28 19:50 ` Francois Romieu
2008-11-28 20:12 ` Arjan van de Ven
2008-11-30 8:58 ` Roger Luethi
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=20081128093217.3888fb46@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=jcliburn@gmail.com \
--cc=netdev@vger.kernel.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).