linux-amlogic.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Neil Armstrong <narmstrong@baylibre.com>
To: Piero <ottuzzi@gmail.com>, linux-amlogic@lists.infradead.org
Subject: Re: odroidc1 eth0 problem with 250HZ
Date: Mon, 28 Jan 2019 11:08:53 +0100	[thread overview]
Message-ID: <d017efc7-e5ba-ea5f-4218-0f05ed86bbec@baylibre.com> (raw)
In-Reply-To: <CAPo5REEKkqctyS2+X8xjn8YgH93RrtAqBu4nELxzgSo0TCgeAQ@mail.gmail.com>

Hi,

On 24/01/2019 15:22, Piero wrote:
> Hi,
> 
>     I tested armbian distribution on my odroid C1+ using kernel
> 4.19.17 and later.
> I observed that with 250HZ kernel eth0 is non-functional giving the
> following error:
> 
> [   14.853086] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> [   14.853367] meson8b-dwmac c9410000.ethernet eth0: device MAC
> address b6:e8:26:b6:da:4a
> [   14.853378] meson8b-dwmac c9410000.ethernet eth0: Could not attach to PHY
> [   14.853386] meson8b-dwmac c9410000.ethernet eth0: stmmac_open:
> Cannot attach to PHY (error: -19)
> [   15.064433] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> [   15.084471] meson8b-dwmac c9410000.ethernet eth0: Could not attach to PHY
> [   15.084486] meson8b-dwmac c9410000.ethernet eth0: stmmac_open:
> Cannot attach to PHY (error: -19)
> [   15.193033] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> [   15.225926] meson8b-dwmac c9410000.ethernet eth0: Could not attach to PHY
> [   15.225958] meson8b-dwmac c9410000.ethernet eth0: stmmac_open:
> Cannot attach to PHY (error: -19)
> [   15.239227] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> [   15.293190] meson8b-dwmac c9410000.ethernet eth0: Could not attach to PHY
> [   15.293213] meson8b-dwmac c9410000.ethernet eth0: stmmac_open:
> Cannot attach to PHY (error: -19)
> [   15.306038] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> [   15.352091] meson8b-dwmac c9410000.ethernet eth0: Could not attach to PHY
> [   15.352111] meson8b-dwmac c9410000.ethernet eth0: stmmac_open:
> Cannot attach to PHY (error: -19)
> [   15.370056] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> 
> Only changing 250HZ to 100HZ is enough to fix this problem.
> Some more details on armbian forum[1].
> Can you check it please?
> I can provide more logs and details if requested. If needed I can test fixes.

This is weird, it could be a sleep not long enough with the changed HZ, can you test other values ?

Do you have other failures ?

Neil

> 
> Thanks in advance
> **Bye
> Piero
> [1]https://forum.armbian.com/topic/9138-odroid-c0c1c1-please-update-the-mainline-kernel-version/
> 
> _______________________________________________
> linux-amlogic mailing list
> linux-amlogic@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-amlogic
> 



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

  reply	other threads:[~2019-01-28 10:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-24 14:22 odroidc1 eth0 problem with 250HZ Piero
2019-01-28 10:08 ` Neil Armstrong [this message]
2019-02-12 13:21   ` Piero
2019-02-12 13:57     ` Neil Armstrong
2019-02-12 15:07       ` Piero

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=d017efc7-e5ba-ea5f-4218-0f05ed86bbec@baylibre.com \
    --to=narmstrong@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=ottuzzi@gmail.com \
    /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).