Netdev List
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Heiner Kallweit <hkallweit1@gmail.com>,
	Andrew Lunn <andrew@lunn.ch>, David Miller <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] net: phy: print error message in phy_error
Date: Sun, 16 Dec 2018 09:02:47 -0800	[thread overview]
Message-ID: <860777a9-4e51-e472-d376-f5758326c624@gmail.com> (raw)
In-Reply-To: <5b0ec181-0b51-6e4a-ca1a-097d44c2b7e9@gmail.com>

Le 12/16/18 à 7:52 AM, Heiner Kallweit a écrit :
> So far phy_error() silently stops the PHY state machine. If the network
> driver doesn't inform about a  MDIO error then the user may wonder why
> his network is down. So let's inform the user.
> 
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>

Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>

Kind of similar to the netdev watchdog on a TX timeout, I wonder if we
should not just put a WARN() here to get a complete stack trace to help
debug those events?

> ---
>  drivers/net/phy/phy.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/net/phy/phy.c b/drivers/net/phy/phy.c
> index 890ae1d73..a898fa411 100644
> --- a/drivers/net/phy/phy.c
> +++ b/drivers/net/phy/phy.c
> @@ -739,6 +739,8 @@ static void phy_error(struct phy_device *phydev)
>  	phydev->state = PHY_HALTED;
>  	mutex_unlock(&phydev->lock);
>  
> +	phydev_err(phydev, "stopping PHY state machine due to error\n");
> +
>  	phy_trigger_machine(phydev);
>  }
>  
> 


-- 
Florian

  parent reply	other threads:[~2018-12-16 17:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-16 15:52 [PATCH net-next] net: phy: print error message in phy_error Heiner Kallweit
2018-12-16 16:48 ` Andrew Lunn
2018-12-16 17:02 ` Florian Fainelli [this message]
2018-12-16 17:16   ` Heiner Kallweit
2018-12-16 17:55     ` Florian Fainelli
2018-12-16 18:11       ` Heiner Kallweit
2018-12-16 17:19   ` Heiner Kallweit

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=860777a9-4e51-e472-d376-f5758326c624@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=hkallweit1@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