From: troy.kisky@boundarydevices.com (Troy Kisky)
To: linux-arm-kernel@lists.infradead.org
Subject: i.Mx6Quad - eth0: tx queue full!
Date: Tue, 29 Jan 2013 11:46:40 -0700 [thread overview]
Message-ID: <51081910.4030707@boundarydevices.com> (raw)
In-Reply-To: <5107FA00.2010809@gmail.com>
On 1/29/2013 9:34 AM, Vikram Narayanan wrote:
> On 1/29/2013 1:17 AM, Troy Kisky wrote:
>> On 1/28/2013 10:39 AM, Vikram Narayanan wrote:
>>> Running the latest head <linux-2.6.git> on an i.Mx6Quad based platform
>>> gives me the below error when flooded with ping requests.
>>>
>>> == Start log ==
>>> [ 2555.004031] ------------[ cut here ]------------
>>> [ 2555.009740] WARNING: at net/sched/sch_generic.c:254
>>> dev_watchdog+0x298/0x2b8()
>>> [ 2555.018721] NETDEV WATCHDOG: eth0 (fec): transmit queue 0 timed out
>>
>> I think the tx interrupt status bit was lost. The packets were
>> transmitted, but the interrupt never
>> happened. The controller should have been reset here, but perhaps a bug
>> with the reset code.
>> Are you using the mainline kernel, or a version Freescale's kernel.
>
> I tried with both the kernels. Freescale's and mainline results in the
> same error.
>
>> mainline fec_restart does not reset tx_full
>>
>> You can try adding
>> fep->tx_full = 0;
>
> With this there was no improvement.
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.
This is the patch that should fix your problem
fec: clear TX_FULL in fec_restart
git://github.com/boundarydevices/linux-imx6.git ethernet_test
Please let me know results.
Thanks
Troy
WARNING: multiple messages have this Message-ID (diff)
From: Troy Kisky <troy.kisky@boundarydevices.com>
To: Vikram Narayanan <vikram186@gmail.com>
Cc: netdev@vger.kernel.org,
"Greg Ungerer" <gregungerer@westnet.com.au>,
shawn.guo@linaro.org, LAK <linux-arm-kernel@lists.infradead.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>
Subject: Re: i.Mx6Quad - eth0: tx queue full!
Date: Tue, 29 Jan 2013 11:46:40 -0700 [thread overview]
Message-ID: <51081910.4030707@boundarydevices.com> (raw)
In-Reply-To: <5107FA00.2010809@gmail.com>
On 1/29/2013 9:34 AM, Vikram Narayanan wrote:
> On 1/29/2013 1:17 AM, Troy Kisky wrote:
>> On 1/28/2013 10:39 AM, Vikram Narayanan wrote:
>>> Running the latest head <linux-2.6.git> on an i.Mx6Quad based platform
>>> gives me the below error when flooded with ping requests.
>>>
>>> == Start log ==
>>> [ 2555.004031] ------------[ cut here ]------------
>>> [ 2555.009740] WARNING: at net/sched/sch_generic.c:254
>>> dev_watchdog+0x298/0x2b8()
>>> [ 2555.018721] NETDEV WATCHDOG: eth0 (fec): transmit queue 0 timed out
>>
>> I think the tx interrupt status bit was lost. The packets were
>> transmitted, but the interrupt never
>> happened. The controller should have been reset here, but perhaps a bug
>> with the reset code.
>> Are you using the mainline kernel, or a version Freescale's kernel.
>
> I tried with both the kernels. Freescale's and mainline results in the
> same error.
>
>> mainline fec_restart does not reset tx_full
>>
>> You can try adding
>> fep->tx_full = 0;
>
> With this there was no improvement.
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.
This is the patch that should fix your problem
fec: clear TX_FULL in fec_restart
git://github.com/boundarydevices/linux-imx6.git ethernet_test
Please let me know results.
Thanks
Troy
next prev parent reply other threads:[~2013-01-29 18:46 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 [this message]
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
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=51081910.4030707@boundarydevices.com \
--to=troy.kisky@boundarydevices.com \
--cc=linux-arm-kernel@lists.infradead.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.