From: Troy Kisky <troy.kisky@boundarydevices.com>
To: Vikram Narayanan <vikram186@gmail.com>
Cc: netdev@vger.kernel.org,
LAK <linux-arm-kernel@lists.infradead.org>,
Fabio Estevam <festevam@gmail.com>
Subject: Re: i.Mx6Quad - eth0: tx queue full!
Date: Wed, 30 Jan 2013 14:04:36 -0700 [thread overview]
Message-ID: <51098AE4.5030305@boundarydevices.com> (raw)
In-Reply-To: <51093882.2060700@gmail.com>
On 1/30/2013 8:13 AM, Vikram Narayanan wrote:
> On 1/30/2013 12:16 AM, Troy Kisky wrote:
>> I have fixed this bug (and more) on Freescale's kernel
>> (imx-3.0.35_1.1.0). I created a branch you can try.
>> Feel free to port to mainline.
> Thanks a lot for the branch. I saw a lot of differences between
> your driver and the mainline. I should spend some time If I had
> to port this to mainline.
>
>> This is the patch that should fix your problem
>> fec: clear TX_FULL in fec_restart
>>
>>
>> Please let me know results.
> When NAPI is disabled I saw a severe packet loss
> (around 40% in a flood ping) which spitted out this,
>
> [ 470.390928] net eth0: missed rxf 2000000 1c000000 0
> [ 470.419098] net eth0: missed rxf 2000000 1c000000 0
> [ 470.443800] net eth0: missed rxf 2000000 1c000000 0
> [ 470.450315] net eth0: missed rxf 2000000 1c000000 0
>
> When NAPI is enabled, it was working good. Though it
> resulted in the same error, it recovered by itself,
> which is perfectly fine for me. :)
>
You'll also have better performance if you pass "enable_wait_mode=off"
in bootargs.
next prev parent reply other threads:[~2013-01-30 21:04 UTC|newest]
Thread overview: 13+ 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 19:47 ` Troy Kisky
2013-01-29 16:33 ` Vikram Narayanan
2013-01-29 16:45 ` Fabio Estevam
2013-01-29 16:55 ` Vikram Narayanan
2013-01-29 16:34 ` Vikram Narayanan
2013-01-29 18:46 ` Troy Kisky
2013-01-30 8:37 ` Duan Fugang-B38611
2013-01-30 15:18 ` Vikram Narayanan
2013-01-30 15:13 ` Vikram Narayanan
2013-01-30 21:04 ` Troy Kisky [this message]
2013-02-18 7:29 ` Frank Li
2013-02-21 17:20 ` Vikram Narayanan
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=51098AE4.5030305@boundarydevices.com \
--to=troy.kisky@boundarydevices.com \
--cc=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=vikram186@gmail.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).