[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191017181446.llylehcpu66bpqcn@beryllium.lan>
Date: Thu, 17 Oct 2019 20:14:46 +0200
From: Daniel Wagner <dwagner@...e.de>
To: Stefan Wahren <wahrenst@....net>
Cc: Woojung Huh <woojung.huh@...rochip.com>,
Andrew Lunn <andrew@...n.ch>, netdev@...r.kernel.org,
UNGLinuxDriver@...rochip.com,
bcm-kernel-feedback-list@...adcom.com,
linux-rpi-kernel@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: lan78xx and phy_state_machine
> >> Unfortunately, you didn't wrote which kernel version works for you
> >> (except of this splat). Only 5.3 or 5.4-rc3 too?
> > With v5.2.20 I was able to boot the system. But after this discussion
> > I would say that was just luck. The race seems to exist for longer and
> > only with my 'special' config I am able to reproduce it.
> okay, let me rephrase my question. You said that 5.4-rc3 didn't even
> boot in your setup. After applying Andrew's patch, does it boot or is it
> a different issue?
Yes, with Andrew's patch the initial problem is gone.
> >> [1] - https://marc.info/?l=linux-netdev&m=154604180927252&w=2
> >> [2] - https://patchwork.kernel.org/patch/10888797/
> > Indeed, the irq domain code looks suspicious and Marc pointed out that
> > is dead wrong. Could we just go with [2] and fix this up?
>
> Sorry, i cannot answer this question.
Sure, I just trying to lobbying :)
Powered by blists - more mailing lists