mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: Aymeric <mulx@aplu.fr>
To: netdev@vger.kernel.org
Cc: "linux-amlogic@lists.infradead.org" <linux-amlogic@lists.infradead.org>
Subject: network unstable on odroid-c1/meson8b.
Date: Wed, 19 Jun 2019 22:18:37 +0200	[thread overview]
Message-ID: <ff9a72bf-7eeb-542b-6292-dd70abdc4e79@aplu.fr> (raw)


[-- Attachment #1.1.1: Type: text/plain, Size: 2032 bytes --]

Hello all,

I've an ODROID-C1 board (a meson8b/S805) and I've some network
unstablity with current mainline kernel; as time of writting, tested
5.0.y, 5.1.y, 5.2-rc4 and didn't try with any others versions.

After a few talks on linux-amlogic mailing list, I've been pointed here
to find and, hoppefully, fix the issue.
The whole thread on linux-amlogic is available here: [¹]

A short summary:
1. With Kernel 3.10.something made by Hardkernel (the one from the board
vendor), the network link is working at 1 gigabit and stay at 1 gigabit.
2. With Kernel 5.0.y, 5.1.y, mainline, the network link goes from up to
down every few seconds at 1 gigabit (making the board unusable) but is
working fine when forced at 100Mb (using ethtool command).
3. The ethernet cable is not the cause of the issue (see #4).
4. After a few more check, I was able to narrow the problem. It's only
present when the board is connected to my "internet box" (a Livebox
3/Sagemcom) but not with a "stupid" d-link switch (both have gigabit
capability).
5. With the help from Martin on linux-amlogic I've tried to disable EEE
in the dtb but it didn't change anything.
6. An extract of the dmesg output grepping ethernet and meson is here
when the issue is occuring: [²].


And the last comment from Martin and why I'm sending a mail here:
- the Amlogic SoCs use a DesignWare MAC (Ethernet controller, the driver
is called stmmac) with a Relatek RTL8211F Ethernet PHY.
- there's little Amlogic specific registers involved: they mostly
control the PHY interface (enabling RMII or RGMII) and the clocks so
it's very likely that someone on the netdev list has an idea how to
debug this because a large part of the Ethernet setup is not Amlogic SoC
specific

So if you've got any idea to fix this issue.. :)

Thanks in advance,

Aymeric.


[¹]:
http://lists.infradead.org/pipermail/linux-amlogic/2019-June/012341.html
[²]:
https://paste.aplu.fr/?b5eb6df48a9c95b6#sqHk8xhWGwRfagWNpL+u7mIsPGWVWFn2d7xBqika8Kc=




[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]

[-- Attachment #2: Type: text/plain, Size: 167 bytes --]

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

             reply	other threads:[~2019-06-19 20:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-19 20:18 Aymeric [this message]
2019-06-19 22:14 ` Heiner Kallweit
2019-06-20  7:55   ` Aymeric
2019-06-20 15:53     ` Heiner Kallweit
2019-06-20 20:54       ` Aymeric
2019-06-23 18:16         ` Aymeric

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=ff9a72bf-7eeb-542b-6292-dd70abdc4e79@aplu.fr \
    --to=mulx@aplu.fr \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=netdev@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

all inboxes | Powered by JetHome®