From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: Freescale FEC packet loss
Date: Sun, 26 Jan 2014 20:12:12 +0100 [thread overview]
Message-ID: <201401262012.13051.marex@denx.de> (raw)
In-Reply-To: <1390762590.2735.39.camel@deadeye.wl.decadent.org.uk>
On Sunday, January 26, 2014 at 07:56:30 PM, Ben Hutchings wrote:
> On Wed, 2014-01-22 at 22:55 +0100, Marek Vasut wrote:
> > Hi guys,
> >
> > I am running stock Linux 3.13 on i.MX6Q SabreLite board. The CPU is
> > i.MX6Q TO 1.0 .
> >
> > I am hitting a WARNING when I use the FEC ethernet to transfer data, thus
> > I started investigating this problem. TL;DR I am not able to figure this
> > problem out, so I am not attaching a patch :-(
> >
> > Steps to reproduce:
> > -------------------
> > 1) Boot stock Linux 3.13 on i.MX6Q SabreLite board
> > 2) Plug in an SD card into one of the SD slots (I use the full-size one)
> > 3) Plug in an USB stick into one of the USB ports (I use the upper one)
> > 4) Plug in an ethernet cable into the board
> >
> > -> Connect the other side into a gigabit-capable PC
>
> [...]
>
> I think there are known problems with 1000BASE-T on the Sabre Lite
> board.
This is MX6-wide thing, not sabrelite specific actually.
> Two possible workarounds are to limit the PHY to 100BASE-TX
> (should be doable with ethtool) or force it to be clock master for
> 1000BASE-T (requires a driver patch).
Can you please elaborate on the later ? I don't quite understand that.
> The vendor kernel apparently does both!
More like the vendor kernel papers over this bug.
> Matthew Garrett has been trying to implement a workaround in a
> clean way.
Do you have any pointers about this please ?
Best regards,
Marek Vasut
WARNING: multiple messages have this Message-ID (diff)
From: Marek Vasut <marex@denx.de>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Frank Li <Frank.Li@freescale.com>,
fugang.duan@freescale.com,
"fabio.estevam@freescale.com" <fabio.estevam@freescale.com>,
Hector Palacios <hector.palacios@digi.com>,
linux-arm-kernel@lists.infradead.org, Detlev Zundel <dzu@denx.de>,
Eric Nelson <eric.nelson@boundarydevices.com>,
Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: Freescale FEC packet loss
Date: Sun, 26 Jan 2014 20:12:12 +0100 [thread overview]
Message-ID: <201401262012.13051.marex@denx.de> (raw)
In-Reply-To: <1390762590.2735.39.camel@deadeye.wl.decadent.org.uk>
On Sunday, January 26, 2014 at 07:56:30 PM, Ben Hutchings wrote:
> On Wed, 2014-01-22 at 22:55 +0100, Marek Vasut wrote:
> > Hi guys,
> >
> > I am running stock Linux 3.13 on i.MX6Q SabreLite board. The CPU is
> > i.MX6Q TO 1.0 .
> >
> > I am hitting a WARNING when I use the FEC ethernet to transfer data, thus
> > I started investigating this problem. TL;DR I am not able to figure this
> > problem out, so I am not attaching a patch :-(
> >
> > Steps to reproduce:
> > -------------------
> > 1) Boot stock Linux 3.13 on i.MX6Q SabreLite board
> > 2) Plug in an SD card into one of the SD slots (I use the full-size one)
> > 3) Plug in an USB stick into one of the USB ports (I use the upper one)
> > 4) Plug in an ethernet cable into the board
> >
> > -> Connect the other side into a gigabit-capable PC
>
> [...]
>
> I think there are known problems with 1000BASE-T on the Sabre Lite
> board.
This is MX6-wide thing, not sabrelite specific actually.
> Two possible workarounds are to limit the PHY to 100BASE-TX
> (should be doable with ethtool) or force it to be clock master for
> 1000BASE-T (requires a driver patch).
Can you please elaborate on the later ? I don't quite understand that.
> The vendor kernel apparently does both!
More like the vendor kernel papers over this bug.
> Matthew Garrett has been trying to implement a workaround in a
> clean way.
Do you have any pointers about this please ?
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-01-26 19:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 21:55 Freescale FEC packet loss Marek Vasut
2014-01-22 21:55 ` Marek Vasut
2014-01-23 1:49 ` fugang.duan at freescale.com
2014-01-23 1:49 ` fugang.duan
2014-01-23 14:20 ` Marek Vasut
2014-01-23 14:20 ` Marek Vasut
2014-01-24 1:28 ` fugang.duan at freescale.com
2014-01-24 1:28 ` fugang.duan
2014-01-26 18:56 ` Ben Hutchings
2014-01-26 18:56 ` Ben Hutchings
2014-01-26 19:12 ` Marek Vasut [this message]
2014-01-26 19:12 ` Marek Vasut
2014-01-26 21:33 ` Ben Hutchings
2014-01-26 21:33 ` Ben Hutchings
2014-01-28 1:01 ` Marek Vasut
2014-01-28 1:01 ` Marek Vasut
2014-02-06 9:42 ` Christian Gmeiner
2014-02-06 9:42 ` Christian Gmeiner
2014-02-06 13:41 ` Marek Vasut
2014-02-06 13:41 ` Marek Vasut
-- strict thread matches above, loose matches on Subject: below --
2014-02-06 5:30 Christian Ege
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=201401262012.13051.marex@denx.de \
--to=marex@denx.de \
--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.