From: Jay Cliburn <jcliburn@gmail.com>
To: Sitsofe Wheeler <sitsofe@yahoo.com>
Cc: linux-kernel@vger.kernel.org, Chris Snook <csnook@redhat.com>,
jie.yang@atheros.com, atl1-devel@lists.sourceforge.net,
netdev@vger.kernel.org
Subject: Re: [atl2] warn_slowpath in dev_watchdog
Date: Sat, 17 Jan 2009 19:40:45 -0600 [thread overview]
Message-ID: <20090117194045.649f55a0@osprey.hogchain.net> (raw)
In-Reply-To: <gkt97e$ti0$1@ger.gmane.org>
[Modifying subject line and cc'ing netdev]
On Sat, 17 Jan 2009 18:49:18 +0000 (UTC)
Sitsofe Wheeler <sitsofe@yahoo.com> wrote:
> On an ever so slightly modified 2.6.28. I think this only happens
> when the upstream router/switch goes out to lunch and packets are
> being sent. It is reproducible but only appears on a home network...
>
> [ 204.704065] ------------[ cut here ]------------
> [ 204.704074] WARNING: at net/sched/sch_generic.c:226 dev_watchdog
> +0x22b/0x240()
> [ 204.704080] NETDEV WATCHDOG: eth0 (atl2): transmit timed out
Please provide your complete dmesg output.
What do you do to reproduce this?
Can you briefly describe the device immediately upstream of the system producing
the warning?
Thanks,
Jay
next parent reply other threads:[~2009-01-18 1:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gkt97e$ti0$1@ger.gmane.org>
2009-01-18 1:40 ` Jay Cliburn [this message]
2009-01-18 10:18 ` [atl2] warn_slowpath in dev_watchdog Sitsofe Wheeler
2009-01-18 15:52 ` Jay Cliburn
2009-01-18 17:40 ` Sitsofe Wheeler
2009-01-18 17:58 ` Jay Cliburn
2009-01-25 16:17 ` Sitsofe Wheeler
2009-01-26 3:00 ` Jay Cliburn
2009-01-27 9:30 ` Sitsofe Wheeler
2009-01-18 17:46 ` Sitsofe Wheeler
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=20090117194045.649f55a0@osprey.hogchain.net \
--to=jcliburn@gmail.com \
--cc=atl1-devel@lists.sourceforge.net \
--cc=csnook@redhat.com \
--cc=jie.yang@atheros.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sitsofe@yahoo.com \
/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).