All of lore.kernel.org
 help / color / mirror / Atom feed
From: "George Spelvin" <linux@horizon.com>
To: davej@redhat.com, linux@horizon.com
Cc: kernel-team@fedoraproject.org, netdev@vger.kernel.org
Subject: Re: NETDEV WATCHDOG: %s (%s): transmit queue %u timed out
Date: 22 May 2012 21:53:12 -0400	[thread overview]
Message-ID: <20120523015312.14731.qmail@science.horizon.com> (raw)
In-Reply-To: <20120523012640.GB15255@redhat.com>

> We seem to be seeing more and more of these (across a range of different NICs)
> https://bugzilla.redhat.com/showdependencytree.cgi?id=702723&hide_resolved=1
> has a bunch of duplicated bugs sorted into per-nic reports.

Thank yoou for rhe response.

Unfortunately, the last reboot was on Feb. 26, and the kernel logs don't go back that far,
so I'm not sure if 3.3-rc5 reported this priblem or not.

  reply	other threads:[~2012-05-23  1:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-23  1:03 NETDEV WATCHDOG: %s (%s): transmit queue %u timed out George Spelvin
2012-05-23  1:26 ` Dave Jones
2012-05-23  1:53   ` George Spelvin [this message]
2012-05-23 22:32     ` Francois Romieu
2012-05-24  1:39       ` George Spelvin
2012-05-24 12:46       ` George Spelvin

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=20120523015312.14731.qmail@science.horizon.com \
    --to=linux@horizon.com \
    --cc=davej@redhat.com \
    --cc=kernel-team@fedoraproject.org \
    --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.