All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vikram Narayanan <vikram186@gmail.com>
To: Frank Li <lznuaa@gmail.com>
Cc: Troy Kisky <troy.kisky@boundarydevices.com>,
	netdev@vger.kernel.org, Fabio Estevam <festevam@gmail.com>
Subject: Re: i.Mx6Quad - eth0: tx queue full!
Date: Thu, 21 Feb 2013 22:50:31 +0530	[thread overview]
Message-ID: <5126575F.5080400@gmail.com> (raw)
In-Reply-To: <CAHrpEqQc8QGV0UNgY_+-JVVQ8Tfq8gGfy6LfKFeaFNxf7hN7sA@mail.gmail.com>

On 2/18/2013 12:59 PM, Frank Li wrote:
> Do you have a way to duplicate this issue consistently?

I think you meant "reproduce".

Yes. Almost everytime in my hardware.
Any network load would trigger this.

On the NFS, I did something like
for i in {1..10000};do;ls -lR *;done

and did a flood ping to the target as well.

Hope this helps,
Vikram

      reply	other threads:[~2013-02-21 17:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-28 17:39 i.Mx6Quad - eth0: tx queue full! Vikram Narayanan
2013-01-28 17:39 ` Vikram Narayanan
2013-01-28 19:47 ` Troy Kisky
2013-01-28 19:47   ` Troy Kisky
2013-01-29 16:33   ` Vikram Narayanan
2013-01-29 16:33     ` Vikram Narayanan
2013-01-29 16:45     ` Fabio Estevam
2013-01-29 16:45       ` Fabio Estevam
2013-01-29 16:55       ` Vikram Narayanan
2013-01-29 16:34   ` Vikram Narayanan
2013-01-29 16:34     ` Vikram Narayanan
2013-01-29 18:46     ` Troy Kisky
2013-01-29 18:46       ` Troy Kisky
2013-01-30  8:37       ` Duan Fugang-B38611
2013-01-30  8:37         ` Duan Fugang-B38611
2013-01-30 15:18         ` Vikram Narayanan
2013-01-30 15:18           ` Vikram Narayanan
2013-01-30 15:13       ` Vikram Narayanan
2013-01-30 15:13         ` Vikram Narayanan
2013-01-30 21:04         ` Troy Kisky
2013-01-30 21:04           ` Troy Kisky
2013-02-18  7:29           ` Frank Li
2013-02-18  7:29             ` Frank Li
2013-02-21 17:20             ` Vikram Narayanan [this message]

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=5126575F.5080400@gmail.com \
    --to=vikram186@gmail.com \
    --cc=festevam@gmail.com \
    --cc=lznuaa@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=troy.kisky@boundarydevices.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 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.