From: Neil Armstrong <narmstrong@baylibre.com>
To: Piero <ottuzzi@gmail.com>
Cc: linux-amlogic@lists.infradead.org
Subject: Re: odroidc1 eth0 problem with 250HZ
Date: Tue, 12 Feb 2019 14:57:48 +0100 [thread overview]
Message-ID: <186a965b-043e-511f-aa84-980e4bac2388@baylibre.com> (raw)
In-Reply-To: <CAPo5REGnr=c=6OGm=b5Bmu7mDravAfMJ0f=OAD=iLS=21ZM+kg@mail.gmail.com>
Hi Piero,
On 12/02/2019 14:21, Piero wrote:
> Hi,
>
> in an old thread[1] there is this sentence: " - enable Ethernet on
> the Odroid-C1 (according to your last thest a TX delay of 4ns is
> required to make it work properly)".
This delay is a setting in HW, and it not correlated at all with the HZ setting.
> So it looks that timing is important to make eth0 of odroidc1
> functional and this correlate well with my observations on kernel HZ.
> I just tested with 200hz (simply only this change...nothing more) and
> odroidc1 eth0 is not working again.
You mean *is working* again ?
You should test a whole range of values, up to 1000Hz.
Neil
>
> *Ciao
> Piero
>
> [1]https://lists.infradead.org/pipermail/linux-amlogic/2018-January/006164.html
>
> Il giorno lun 28 gen 2019 alle ore 11:08 Neil Armstrong
> <narmstrong@baylibre.com> ha scritto:
>>
>> 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
next prev parent reply other threads:[~2019-02-12 13:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 14:22 Piero
2019-01-28 10:08 ` Neil Armstrong
2019-02-12 13:21 ` Piero
2019-02-12 13:57 ` Neil Armstrong [this message]
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=186a965b-043e-511f-aa84-980e4bac2388@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
all inboxes | Powered by JetHome®