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 10:50:44 -0800 [thread overview]
Message-ID: <20081128105044.241d43c0@linux.intel.com> (raw)
In-Reply-To: <20081128123631.5209d0b8@osprey.hogchain.net>
>
> > 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.
>
> ...And that's what troubles me: the L1 chip isn't what I'd
> characterize as "popular" -- it's LOM only, and it's found in only
> about 25 mainboards that I know of (from voluntary user reports) --
> yet its prevalence in the tx timeout list seems to be quickly rising.
>
> Can you produce a list from your database for me that includes the
> kernel version for each of the 122 reported atl1 dev_watchdog
> warnings? I'd like to see if I can correlate an increase in the
> warnings with a particular change we made.
=> select count(version), version from oopses where guilty='dev_watchdog(atl1)' group by version order by version desc;
count | version
-------+-----------------
93 | 2.6.27.5
6 | 2.6.27.4
1 | 2.6.27.3
1 | 2.6.27.2
1 | 2.6.27-rc9
1 | 2.6.27-rc7-git1
1 | 2.6.27-rc7
1 | 2.6.27-rc6
6 | 2.6.27-rc3
7 | 2.6.27
4 | 2.6.26.6
(11 rows)
or in more detail:
=> select count(full_version), full_version from oopses where \
guilty='dev_watchdog(atl1)' group by full_version order by \
full_version desc;
count | full_version
-------+-----------------------------------
2 | 2.6.27.5-94.fc10.x86_64
26 | 2.6.27.5-41.fc9.x86_64
12 | 2.6.27.5-41.fc9.i686
15 | 2.6.27.5-37.fc9.x86_64
19 | 2.6.27.5-37.fc9.i686
11 | 2.6.27.5-117.fc10.x86_64
4 | 2.6.27.5-117.fc10.i686
1 | 2.6.27.5-109.fc10.x86_64
2 | 2.6.27.5-109.fc10.i686.PAE
1 | 2.6.27.5-109.fc10.i686
1 | 2.6.27.4-79.fc10.i686
1 | 2.6.27.4-68.fc10.x86_64
3 | 2.6.27.4-68.fc10.i686
1 | 2.6.27.4-26.fc9.x86_64
1 | 2.6.27.3-34.rc1.fc10.i686.PAE
1 | 2.6.27.2-23.rc1.fc10.x86_64
4 | 2.6.27-wl
1 | 2.6.27-rc7
1 | 2.6.27-rc6-wl-AUS32
6 | 2.6.27-rc3-wl-8KS-UVC
1 | 2.6.27-7-generic
1 | 2.6.27-0.398.rc9.fc10.x86_64
1 | 2.6.27-0.352.rc7.git1.fc10.x86_64
2 | 2.6.27
3 | 2.6.26.6-79.fc9.x86_64
1 | 2.6.26.6-79.fc9.i686
(26 rows)
--
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 18:49 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
2008-11-28 18:36 ` Jay Cliburn
2008-11-28 18:50 ` Arjan van de Ven [this message]
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=20081128105044.241d43c0@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 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.