All of lore.kernel.org
 help / color / mirror / Atom feed
From: troy.kisky@boundarydevices.com (Troy Kisky)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG]: imx6q (wandboard): Very unstable ethernet since kernel 3.16
Date: Fri, 08 Aug 2014 15:02:03 -0700	[thread overview]
Message-ID: <53E548DB.90905@boundarydevices.com> (raw)
In-Reply-To: <1407509932.19455.7.camel@sharkbay.at>

On 8/8/2014 7:58 AM, Thomas Scheiblauer wrote:
> 
> 
> Indeed, commenting out these 2 lines in
> arch/arm/boot/dts/imx6qdl-wandboard.dtsi fixes my problem without having
> to increase TX_RING_SIZE.
> Thank you very much!
> 
Could you also please checkout commit

commit 9fc77821b17155c6e0ab50b1e1dd80c2b0e63e98
Author: Sascha Silbe <x-linux@infra-silbe.de>
Date:   Thu Feb 6 23:24:13 2014 +0100

    ARM: dts: imx6qdl-wandboard: use GPIO_6 for FEC interrupt


and see if it also shows ethernet instabilities?


Thanks
Troy

  parent reply	other threads:[~2014-08-08 22:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-08 13:15 [BUG]: imx6q (wandboard): Very unstable ethernet since kernel 3.16 Thomas Scheiblauer
2014-08-08 13:27 ` Russell King - ARM Linux
2014-08-08 14:10   ` Thomas Scheiblauer
2014-08-08 14:17     ` Fabio Estevam
2014-08-08 14:37       ` Thomas Scheiblauer
2014-08-08 14:30     ` Russell King - ARM Linux
2014-08-08 14:58       ` Thomas Scheiblauer
2014-08-08 15:46         ` Fabio Estevam
2014-08-08 16:33           ` [PATCH 1/1] undo workaround for i.mx6 silicon errata ERR006687 which resulted in an unstable ethernet connection (lost interrupts?) Thomas Scheiblauer
2014-08-08 17:01             ` Fabio Estevam
2014-08-08 22:02         ` Troy Kisky [this message]
     [not found]           ` <CAHKv19Cky2+vEOirwwd8xhix_V0Vivn_6BbuYq+D_k0o8o4Gsg@mail.gmail.com>
2014-08-09  0:33             ` [BUG]: imx6q (wandboard): Very unstable ethernet since kernel 3.16 Troy Kisky
2014-08-09  0:41               ` George Joseph
2014-08-10 22:36               ` Iain Paton
2014-08-11  5:24                 ` Thomas Scheiblauer
2014-08-17 17:14                   ` Alexander Holler

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=53E548DB.90905@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.