From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: davej@redhat.com, netdev@vger.kernel.org
Subject: Re: sch_generic warn_on (timed out)
Date: Mon, 11 Jul 2011 23:20:04 +0200 [thread overview]
Message-ID: <1310419204.2860.11.camel@edumazet-laptop> (raw)
In-Reply-To: <20110711.141701.1453197953333902027.davem@davemloft.net>
Le lundi 11 juillet 2011 à 14:17 -0700, David Miller a écrit :
> From: Dave Jones <davej@redhat.com>
> Date: Mon, 11 Jul 2011 16:48:34 -0400
>
> > We've recieved quite a few bug reports in Fedora recently concerning this warning in
> > sch_generic..
> >
> > WARN_ONCE(1, KERN_INFO "NETDEV WATCHDOG: %s (%s): transmit queue %u timed out\n",
> > dev->name, netdev_drivername(dev, drivername, 64), i);
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=702723 is our 'master bug' that we're
> > duping all others against. It seems to be showing up on a variety of different
> > hardware (r8169, atl1c, ipheth, e1000e, 8139too). Do all these drivers need
> > fixing ? or is it just 'crap hardware' ?
> >
> > note that I've only been looking through fedora 15 bugs so far (which is still on 2.6.38),
> > but looking at the commit log for sch_generic, it doesn't seem that there's anything
> > obvious that needs backporting.
>
> It means the transmitter stopped sending packets for several seconds.
>
> I would track this on a per-device basis if I were you, instead of
> combining them all into one super-bug.
Last time I took a look (on one r8169 NIC), it wasnt clear if this could
be a PAUSE problem.
next prev parent reply other threads:[~2011-07-11 21:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 20:48 sch_generic warn_on (timed out) Dave Jones
2011-07-11 21:17 ` David Miller
2011-07-11 21:20 ` Eric Dumazet [this message]
2011-07-20 21:53 ` Francois Romieu
2011-07-20 16:38 ` Brandeburg, Jesse
2011-07-21 18:56 ` Dave Jones
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=1310419204.2860.11.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davej@redhat.com \
--cc=davem@davemloft.net \
--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