From: robin.murphy@arm.com (Robin Murphy)
To: linux-arm-kernel@lists.infradead.org
Subject: 4.5.0 on sun7i-a20-olinuxino-lime2: libphy: PHY stmmac-0:ffffffff not found (regression from rc7)
Date: Wed, 16 Mar 2016 12:09:24 +0000 [thread overview]
Message-ID: <56E94CF4.2060607@arm.com> (raw)
In-Reply-To: <56E945FF.6080005@arm.com>
On 16/03/16 11:39, Marc Zyngier wrote:
> On 16/03/16 11:19, Bert Lindner wrote:
>> Hi,
>>
>> Hopefully this is the correct place and way to report this.
>>
>> For the board sun7i-a20-olinuxino-lime2, there seems to be a problem
>> with the eth0 PHY in mainline kernel 4.5.0 that developed since
>> 4.5.0-rc7. Ethernet does not work, although eth0 is reported:
>>
>> root at lime2-079f:~# ip a l eth0
>> 2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
>> default qlen 1000
>> link/ether 02:c9:05:02:07:9f brd ff:ff:ff:ff:ff:ff
>>
>> Difference reported in dmesg:
>>
>> 4.5.0-rc7:
>> [ 9.379279] NET: Registered protocol family 10
>> [ 10.217148] RX IPC Checksum Offload disabled
>> [ 10.217195] No MAC Management Counters available
>> [ 10.217627] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>> [ 15.206250] sun7i-dwmac 1c50000.ethernet eth0: Link is Up -
>> 1Gbps/Full - flow control off
>> [ 15.206360] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
>>
>> 4.5.0:
>> [ 9.767125] NET: Registered protocol family 10
>> [ 10.357405] libphy: PHY stmmac-0:ffffffff not found
>> [ 10.362382] eth0: Could not attach to PHY
>> [ 10.366557] stmmac_open: Cannot attach to PHY (error: -19)
>>
>> .config is identical for both, also after make oldconfig, apart from
>> comment with version number. DTB file is also identical between the two
>> versions.
>>
>> Kernels are compiled on the board itself. /proc/version string:
>> Linux version 4.5.0-rc7 (root at lime2-079f) (gcc version 4.9.1
>> (Ubuntu/Linaro 4.9.1-16ubuntu6) ) #1 SMP Mon Mar 7 11:57:25 UTC 2016
>> Linux version 4.5.0 (root at lime2-079f) (gcc version 4.9.1 (Ubuntu/Linaro
>> 4.9.1-16ubuntu6) ) #1 SMP Tue Mar 15 11:39:01 UTC 2016
>>
>> Please let me know if more info is needed, if I should post complete
>> .config, test compile with a particular config or patch, etc. Part of
>> .config below.
>
> Can you please try reverting 88f8b1b ("stmmac: Fix 'eth0: No PHY found'
> regression") and report whether or not this changes anything? This seems
> to be the only stmac patch between -rc7 and release...
Sounds like the same thing as the giant ongoing discussion thread here:
http://thread.gmane.org/gmane.linux.drivers.devicetree/159007/focus=402830
Robin.
>
> Thanks,
>
> M.
>
next prev parent reply other threads:[~2016-03-16 12:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 11:19 4.5.0 on sun7i-a20-olinuxino-lime2: libphy: PHY stmmac-0:ffffffff not found (regression from rc7) Bert Lindner
2016-03-16 11:39 ` Marc Zyngier
2016-03-16 12:09 ` Robin Murphy [this message]
2016-03-16 13:06 ` Marc Zyngier
2016-03-16 13:10 ` Andreas Färber
2016-03-16 15:10 ` Bert Lindner
2016-03-16 17:42 ` Marc Zyngier
2016-03-16 23:56 ` Bert Lindner
2016-03-17 7:52 ` Marc Zyngier
2016-05-20 5:44 ` Andre Heider
2016-05-20 7:56 ` Marc Zyngier
2016-05-20 8:14 ` Giuseppe CAVALLARO
2016-05-20 10:30 ` Andre Heider
2016-05-20 10:36 ` Marc Zyngier
2016-05-20 10:43 ` Andre Heider
2016-05-21 15:47 ` Bert Lindner
2016-05-22 9:30 ` Marc Zyngier
2016-05-23 13:28 ` Giuseppe CAVALLARO
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=56E94CF4.2060607@arm.com \
--to=robin.murphy@arm.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 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).