netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Ruehl <chris.ruehl@gtsys.com.hk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: f.fainelli@gmail.com, netdev@vger.kernel.org
Subject: Re: [Regression] net/phy/micrel.c v4.9.94
Date: Thu, 19 Apr 2018 09:21:05 +0800	[thread overview]
Message-ID: <28e69b2b-e948-ab0e-d0c4-5f78994cfd98@gtsys.com.hk> (raw)
In-Reply-To: <20180418130203.GG31643@lunn.ch>

On Wednesday, April 18, 2018 09:02 PM, Andrew Lunn wrote:
> On Wed, Apr 18, 2018 at 02:56:01PM +0200, Andrew Lunn wrote:
>> On Wed, Apr 18, 2018 at 09:34:16AM +0800, Chris Ruehl wrote:
>>> Hello,
>>>
>>> I like to get your heads up at a regression introduced in 4.9.94
>>> commitment lead to a kernel ops and make the network unusable on my MX6DL
>>> customized board.
>>>
>>> Race condition resume is called on startup and the phy not yet initialized.
>>
>> Hi Chris
>>
>> Please could you try
>>
>> bfe72442578b ("net: phy: micrel: fix crash when statistic requested for KSZ9031 phy")
> 
> I don't think it is a complete fix. I suspect "Micrel KSZ8795",
> "Micrel KSZ886X Switch", "Micrel KSZ8061", and "Micrel KS8737" will
> still have problems.
> 
> Those four probably need a:
> 
>          .probe          = kszphy_probe,
> 
> 	Andrew
> 

Indeed I have the
[    7.385851] Micrel KSZ9031 Gigabit PHY 2188000.ethernet-1:05: attached PHY 
driver [Micrel KSZ9031 Gigabit PHY] (mii_bus:phy_addr=2188000.ethernet-1:05, irq=-1)

first I rollback to a non crashing stable kernel.

As "bfe72442578b" gonna fix it I check with the next update and verify its works 
for me.

Thanks
Chris

  reply	other threads:[~2018-04-19  1:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-18  1:34 [Regression] net/phy/micrel.c v4.9.94 Chris Ruehl
2018-04-18  5:09 ` Chris Ruehl
2018-04-18 12:43   ` Andrew Lunn
2018-04-18 12:56 ` Andrew Lunn
2018-04-18 13:02   ` Andrew Lunn
2018-04-19  1:21     ` Chris Ruehl [this message]
2018-04-19  1:34       ` Chris Ruehl
2018-04-19  2:34         ` Chris Ruehl

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=28e69b2b-e948-ab0e-d0c4-5f78994cfd98@gtsys.com.hk \
    --to=chris.ruehl@gtsys.com.hk \
    --cc=andrew@lunn.ch \
    --cc=f.fainelli@gmail.com \
    --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).