NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: port-arm/53216: sunxi awge is unreliable at gigabit speed



The following reply was made to PR port-arm/53216; it has been noted by GNATS.

From: Manuel Bouyer <bouyer%antioche.eu.org@localhost>
To: Martin Husemann <martin%duskware.de@localhost>
Cc: gnats-bugs%NetBSD.org@localhost, port-arm-maintainer%netbsd.org@localhost,
        gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
Subject: Re: port-arm/53216: sunxi awge is unreliable at gigabit speed
Date: Thu, 26 Apr 2018 19:46:32 +0200

 On Thu, Apr 26, 2018 at 11:46:38AM +0200, Manuel Bouyer wrote:
 > > Yes, there are two phys in the soc, only one is connected on the cubietruck
 > > (AFAIK).
 > > 
 > > awge0 at fdt1: GMAC
 > > awge0: interrupting on GIC irq 117
 > > awge0: Ethernet address: 02:0e:03:41:63:14
 > > rgephy0 at awge0 phy 0: RTL8169S/8110S/8211 1000BASE-T media interface, rev. 5
 > > rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
 > > rgephy1 at awge0 phy 1: RTL8169S/8110S/8211 1000BASE-T media interface, rev. 5
 > > rgephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
 > 
 > Actually I don't think there are 2 PHYs, in the cubietruck schematics, as
 > well as the lime2 schematic, and by board inspection, there is only one
 > PHY. I think the same PHY is responding on 2 different addresses.
 > 
 > Also, it looks like the lim2 resision I have and the cubietruck have
 > the same 8211 variant.
 > 
 > I'll have to investigate some more on my side then
 
 Could be some uninitialized register problem.
 I tried to apply the no-rx-delay property for my board in sunxi_platform.c,
 this made the problem worse (more packet loss with ping, I couldn't
 even connect via ssh, link led on the board off but still on on the switch).
 rebooting with a known-good kernel didn't get me a working ethernet.
 I had to power cycle to get back to the previous working state.
 
 Now to find what appropriate "no-rx-delay" values would work for this
 board ...
 
 -- 
 Manuel Bouyer <bouyer%antioche.eu.org@localhost>
      NetBSD: 26 ans d'experience feront toujours la difference
 --
 


Home | Main Index | Thread Index | Old Index