On Thu, 1970-01-01 at 00:00 +0000, Madalin-cristian Bucur wrote: > > > -----Original Message----- > > From: Joakim Tjernlund [mailto:joakim.tjernl...@infinera.com] > > Sent: Tuesday, January 16, 2018 7:58 PM > > To: and...@lunn.ch > > Subject: Re: DPAA Ethernet traffice troubles with Linux kernel > > > > On Thu, 1970-01-01 at 00:00 +0000, Andrew Lunn wrote: > > > > > > Hi Joakim > > > > > > You appear to be using an old kernel. Take a look at: > > > > Not really, I am using 4.14.x and I don't think that is old. Seems like > > this > > patch hasn't been sent to 4.14.x. > > > > I wonder if I might be missing something else, we just moved to 4.14 and > > notic that all > > our fixed PHYs are non functioning: > > fsl_mac ffe4e2000.ethernet: FMan MEMAC > > fsl_mac ffe4e2000.ethernet: FMan MAC address: 00:06:9c:0b:06:20 > > fsl_mac dpaa-ethernet.0: __devm_request_mem_region(mac) failed > > fsl_mac: probe of dpaa-ethernet.0 failed with error -16 > > fsl_mac ffe4e4000.ethernet: FMan MEMAC > > fsl_mac ffe4e4000.ethernet: FMan MAC address: 00:06:9c:0b:06:21 > > fsl_mac dpaa-ethernet.1: __devm_request_mem_region(mac) failed > > fsl_mac: probe of dpaa-ethernet.1 failed with error -16 > > fsl_mac ffe4e6000.ethernet: FMan MEMAC > > fsl_mac ffe4e6000.ethernet: FMan MAC address: 00:06:9c:0b:06:22 > > fsl_mac dpaa-ethernet.2: __devm_request_mem_region(mac) failed > > fsl_mac: probe of dpaa-ethernet.2 failed with error -16 > > fsl_mac ffe4e8000.ethernet: FMan MEMAC > > fsl_mac ffe4e8000.ethernet: FMan MAC address: 00:06:9c:0b:06:23 > > fsl_mac dpaa-ethernet.3: __devm_request_mem_region(mac) failed > > fsl_mac: probe of dpaa-ethernet.3 failed with error -16 > > > > Feels like FMAN still think there are real PHYs there ? > > Hi Joakim, > > These errors are issued when trying to probe the second time the same > MAC node. The issue was introduced by this commit: > > commit 4d8ee1935bcd666360311dfdadeee235d682d69a > Author: Florian Fainelli <f.faine...@gmail.com> > Date: Tue Aug 22 15:24:47 2017 -0700 > fsl/man: Inherit parent device and of_node > > and was later addressed by this patch set: > > http://patchwork.ozlabs.org/project/netdev/list/?series=8462&state=* > > Even with these errors printed, all is working fine, it's just the > second probing that fails. Adding the latter patches or reverting > the one above makes the errors prints dissapear.
Looking at the above patch seriers I see it is in state Accepted and has been there since 2017-10-16 That seems like a awful long to wait in before getting into Linux, is there something holding these patches back ? Jocke
