From: Andrew Lunn <andrew@lunn.ch>
To: Stefan Wahren <wahrenst@gmx.net>
Cc: Daniel Wagner <dwagner@suse.de>,
Woojung Huh <woojung.huh@microchip.com>,
netdev@vger.kernel.org, UNGLinuxDriver@microchip.com,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: lan78xx and phy_state_machine
Date: Thu, 17 Oct 2019 20:25:21 +0200 [thread overview]
Message-ID: <20191017182521.GU17013@lunn.ch> (raw)
In-Reply-To: <388beb72-c7e6-745a-ad39-cfbde201f373@gmx.net>
On Thu, Oct 17, 2019 at 07:52:32PM +0200, Stefan Wahren wrote:
> Hi Daniel,
>
> Am 17.10.19 um 19:41 schrieb Daniel Wagner:
> > Hi Stefan,
> >
> > On Thu, Oct 17, 2019 at 07:05:32PM +0200, Stefan Wahren wrote:
> >> Am 17.10.19 um 08:52 schrieb Daniel Wagner:
> >>> On Wed, Oct 16, 2019 at 05:51:07PM +0200, Andrew Lunn wrote:
> >>>> Please could you give this a go. It is totally untested, not even
> >>>> compile tested...
> >>> Sure. The system boots but ther is one splat:
> >>>
> >> this is a known issues since 4.20 [1], [2]. So not related to the crash.
> > Oh, I see.
> >
> >> 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?
Hi Stefan
I would say i fixed a real issue with my patch. I will submit it to
David for stable. The problem has come to light because Danial is
using the kernel ipconfig and NFS root. That makes the race condition
hit every time. But the issue could happen under other conditions as
well.
Andrew
prev parent reply other threads:[~2019-10-17 18:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191014140604.iddhmg5ckqhzlbkw@beryllium.lan>
[not found] ` <20191014163004.GP25745@shell.armlinux.org.uk>
[not found] ` <20191014192529.z7c5x6hzixxeplvw@beryllium.lan>
2019-10-14 19:51 ` lan78xx and phy_state_machine Stefan Wahren
2019-10-14 20:20 ` Heiner Kallweit
2019-10-14 22:12 ` Russell King - ARM Linux admin
2019-10-15 19:38 ` Heiner Kallweit
2019-10-15 22:09 ` Russell King - ARM Linux admin
2019-10-16 15:36 ` Andrew Lunn
2019-10-16 5:48 ` Stefan Wahren
[not found] ` <20191015005327.GJ19861@lunn.ch>
2019-10-15 17:16 ` Daniel Wagner
2019-10-16 14:25 ` Daniel Wagner
2019-10-16 15:51 ` Andrew Lunn
2019-10-17 6:52 ` Daniel Wagner
2019-10-17 13:15 ` Andrew Lunn
2019-10-17 17:05 ` Stefan Wahren
2019-10-17 17:41 ` Daniel Wagner
2019-10-17 17:52 ` Stefan Wahren
2019-10-17 18:14 ` Daniel Wagner
2019-10-17 18:25 ` Andrew Lunn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191017182521.GU17013@lunn.ch \
--to=andrew@lunn.ch \
--cc=UNGLinuxDriver@microchip.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dwagner@suse.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=wahrenst@gmx.net \
--cc=woojung.huh@microchip.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).