[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: odroid-c1's awge0 on 9?
On Thu, 14 Nov 2019 at 05:14, Christoph Badura <bad%bsd.de@localhost> wrote:
> On Mon, Nov 04, 2019 at 02:05:20AM +0100, Christoph Badura wrote:
> > On Sat, Nov 02, 2019 at 12:55:16PM -0700, Jason Thorpe wrote:
> > > > On Nov 2, 2019, at 10:42 AM, Christoph Badura <bad%bsd.de@localhost> wrote:
> > > > Or maybe fix rgephy and back out the workarounds. Jarend pointed out that
> > > > phy address 0 is a broadcast address on RTL8211[EF].
> > >
> > > How is using the DT information to find the PHY a "workaround"? It
> > > certainly seems like it would in fact be preferred.
> > Because it doesn't fix the underlying bug.
> > In all the cases (Andrew Cagney's odroid-c1, tih's rock64, my bananapi m1)
> > we saw rgephy attaching at id 0 and 1:
> > rgephy0 at awge0 phy 0: RTL8211F 1000BASE-T media interface
> > rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, auto
> > rgephy1 at awge0 phy 1: RTL8211F 1000BASE-T media interface
> > rgephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, auto
> > awge0: interrupting on GIC irq 56
> Just to make sure I re-tested Nov 4th and I couldn't reproduce the problem
> anymore. Not even moving connecting the bananapi to same switch port and
> using LCD/USB keyboard (just in case). It always got GigE interface
> working immediately independend of wether rgephy attached at id 0 or not.
> I.e. with a kernel from before the change to sunxi_gmac.c and with a kernel
> from after the change. It was perfectly reproducible before the weekend.
Just re-tested (well Friday) and, alas, I've not had the same luck.
> I'm not sure what changed. The switch didn't reboot or reconfigure in
> that timeframe either.
Main Index |
Thread Index |