Message-ID: <20191016120158.718e4c25@hermes.lan>
Date:   Wed, 16 Oct 2019 12:01:58 -0700
From:   Stephen Hemminger <stephen@...workplumber.org>
To:     Madalin Bucur <madalin.bucur@....com>
Cc:     netdev@...r.kernel.org
Subject: Fw: [Bug 205215] New: Amiga X5000 Cyrus board DPAA network driver
 issue



Begin forwarded message:

Date: Wed, 16 Oct 2019 18:57:44 +0000
From: bugzilla-daemon@...zilla.kernel.org
To: stephen@...workplumber.org
Subject: [Bug 205215] New: Amiga X5000 Cyrus board DPAA network driver issue


https://bugzilla.kernel.org/show_bug.cgi?id=205215

            Bug ID: 205215
           Summary: Amiga X5000 Cyrus board DPAA network driver issue
           Product: Networking
           Version: 2.5
    Kernel Version: 5.4
          Hardware: PPC-32
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: IPV4
          Assignee: stephen@...workplumber.org
          Reporter: madskateman@...il.com
        Regression: No

Hi all,

It might or might not be a bug, but help would be very welcome. 

Me and all other AmigaOne X5000 users (Cyrus mainboard with Freescale P5020
cpu) are not able to use the DPAA onboard Ethernet adapter with the linux
kernels since the last two years (AFAIK)
(link to the board: http://wiki.amiga.org/index.php?title=X5000 )

So what is happening,

First of all the hardware is functional. When using AmigaOS4.1FE the Ethernet
adapter is fine. When using the adapter within U-boot (ping for example) it is
also working as expected.

When booted into linux the ethernet adapter does not get up. 
The output of DMESG is:

skateman@...00LNX:~$ dmesg | grep eth
[ 4.740603] fsl_dpaa_mac ffe4e6000.ethernet: FMan dTSEC version: 0x08240101
[ 4.741026] fsl_dpaa_mac ffe4e6000.ethernet: FMan MAC address:
00:04:a3:6b:41:7c
[ 4.741387] fsl_dpaa_mac ffe4e8000.ethernet: FMan dTSEC version: 0x08240101
[ 4.741740] fsl_dpaa_mac ffe4e8000.ethernet: FMan MAC address:
00:1e:c0:f8:31:b5
[ 4.742001] fsl_dpaa_mac ffe4e0000.ethernet:
of_get_mac_address(/soc@...000000/fman@...000/ethernet@...00) failed
[ 4.742203] fsl_dpaa_mac: probe of ffe4e0000.ethernet failed with error -22
[ 4.742382] fsl_dpaa_mac ffe4e2000.ethernet:
of_get_mac_address(/soc@...000000/fman@...000/ethernet@...00) failed
[ 4.742568] fsl_dpaa_mac: probe of ffe4e2000.ethernet failed with error -22
[ 4.742749] fsl_dpaa_mac ffe4e4000.ethernet:
of_get_mac_address(/soc@...000000/fman@...000/ethernet@...00) failed
[ 4.747328] fsl_dpaa_mac: probe of ffe4e4000.ethernet failed with error -22
[ 4.751918] fsl_dpaa_mac ffe4f0000.ethernet:
of_get_mac_address(/soc@...000000/fman@...000/ethernet@...00) failed
[ 4.756660] fsl_dpaa_mac: probe of ffe4f0000.ethernet failed with error -22
[ 4.763988] fsl_dpaa_mac ffe4e6000.ethernet eth0: Probed interface eth0
[ 4.771622] fsl_dpaa_mac ffe4e8000.ethernet eth1: Probed interface eth1

There has been already spend time and effort but the issues still remains..
(
http://linuxppc.10917.n7.nabble.com/DPAA-Ethernet-traffice-troubles-with-Linux-kernel-td132277.html
)

I might have found something that could point into the right direction.

The last few days regarding another issue i stumbled upon this post from Russel
King. It had to do with coherent DMA
(http://forum.hyperion-entertainment.com/viewtopic.php?f=58&t=4349&start=70)

"Hmm, so it looks like PowerPC doesn't mark devices that are dma
coherent with a property that describes them as such.

I think this opens a wider question - what should of_dma_is_coherent()
return for PowerPC? It seems right now that it returns false for
devices that are DMA coherent, which seems to me to be a recipe for
future mistakes.

Any ideas from the PPC maintainers?"

I started to dig around regarding DPAA ethernet and Coherent DMA and stumbled
upon this document. 

http://cache.freescale.com/files/training/doc/ftf/2014/FTF-NET-F0246.pdf

In this troubleshooting document similar issues and errors are being shown with
possible troubleshooting steps. 

It would be great if someone could point us into the right direction and has a
clue what could be changed within the kernel to get the Ethernet adapter
working.

Dave

-- 
You are receiving this mail because:
You are the assignee for the bug.

Powered by blists - more mailing lists