From: Florian Fainelli <f.fainelli@gmail.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
ptx kernel <kernel@pengutronix.de>,
Heiner Kallweit <hkallweit1@gmail.com>,
Andrew Lunn <andrew@lunn.ch>
Subject: Re: BUG: "13d0ab6750b2 net: phy: check return code when requesting PHY driver module" breaks NFS-Root
Date: Mon, 11 Mar 2019 11:11:11 -0700 [thread overview]
Message-ID: <39ce904c-91cd-e651-fe21-b13056e67ff8@gmail.com> (raw)
In-Reply-To: <9cd47d80-9e84-c72b-ae7f-e38934580390@pengutronix.de>
On 3/11/19 11:04 AM, Marc Kleine-Budde wrote:
> On 3/11/19 1:23 PM, Marc Kleine-Budde wrote:
>> Hello,
>>
>> I'm on next-next/master and noticed that the following patch:
>>
>> | 13d0ab6750b2 net: phy: check return code when requesting PHY
>> | driver module
>>
>> breaks NFS Root for my embedded device (riotboard). The kernel dhcp
>> fails to get an address and thus no NFS Root.
>
> Just noticed that problem was fixed by commit:
>
> | 21e194425abd net: phy: fix issue with loading PHY driver w/o initramfs
>
> I continued bisecting and found a bad commit in the riotboard's phy
> driver. I'll send a separate mail for this.
>
> | cd28d1d6e52e net: phy: at803x: Disable phy delay for RGMII mode
If your problem is with this driver, keep in mind that the at803x PHY
driver incorrectly acted on the 'phy-mode'/phy_interface_t type and you
may need DTS changes to be conforming. Of course, there is no way to
programmatically detect any of that, which adds to the fun.
--
Florian
next prev parent reply other threads:[~2019-03-11 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 12:23 BUG: "13d0ab6750b2 net: phy: check return code when requesting PHY driver module" breaks NFS-Root Marc Kleine-Budde
2019-03-11 18:04 ` Marc Kleine-Budde
2019-03-11 18:11 ` Florian Fainelli [this message]
2019-03-12 8:02 ` Marc Kleine-Budde
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=39ce904c-91cd-e651-fe21-b13056e67ff8@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
/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).