From: John Holland <jotihojr@gmail.com>
To: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: ARM: imx6q fec watchdog timeout with TX ring dump
Date: Fri, 22 Aug 2014 23:41:38 +0200 [thread overview]
Message-ID: <53F7B912.4050103@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1595 bytes --]
Hello everyone,
I've been playing around with a Utilite Pro recently. It features a
Freescale imx6q with SoC FEC as eth0 and a second ether Intel I211
interface on PCIE being mapped to eth1 amongst various other bits.
ATM, it's running debian jessie and kernel 3.16.1 with the recent three
patch sets from Russell King at
http://ftp.arm.linux.org.uk/cgit/linux-arm.git/log/?h=fec-testing; from
the tag imx-drm-fixes-urgent to fec-testing, minus the "clear IPV6
header CS".
During normal operation, I have had the occasional FEC Watchdog Timeout
(FWT). However, when eth0 und eth1 are bonded to balance-rr mode and two
independent iperfs cliented by different machines with each 4 threads
run free on the Utilite, it inevitably comes to FWTs. Raising
packets_per_slave to four seems to help somewhat.
The bond is routed through two aggregated (trunk) ports on a Netgear
JGS524E running to the iperf clients.
Drop me a line, if you need more information.
TIA,
John
[1] Patch set A:
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-July/270173.html
[2] Patch set B:
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-July/270373.html
[3] Patch set C:
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-July/270393.html
[4] Linux bonding documentation
https://www.kernel.org/doc/Documentation/networking/bonding.txt
[5] Utilite Pro product page
http://utilite-computer.com/web/utilite-pro-specifications
[6] Utilite Pro bonding configuration http://www.utilite-co
mputer.com/forum/viewtopic.php?f=73&t=1980&sid=31eb3a1273da28916d665112f8af2350
[-- Attachment #2: fec-watchdog.log.gz --]
[-- Type: application/gzip, Size: 7123 bytes --]
[-- Attachment #3: config.gz --]
[-- Type: application/gzip, Size: 26690 bytes --]
[-- Attachment #4: imx6q-cm-fx6.dtb --]
[-- Type: application/octet-stream, Size: 32093 bytes --]
reply other threads:[~2014-08-22 21:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=53F7B912.4050103@gmail.com \
--to=jotihojr@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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;
as well as URLs for NNTP newsgroup(s).