public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: "David S. Miller" <davem@davemloft.net>,
	David Daney <ddaney@caviumnetworks.com>,
	netdev@vger.kernel.org
Subject: Re: [BISECTED] v4.9: OCTEON ethernet crash
Date: Wed, 14 Dec 2016 17:14:04 -0800	[thread overview]
Message-ID: <2c346015-958a-3f65-f877-8b6fc21165f6@gmail.com> (raw)
In-Reply-To: <20161215011203.nyyl5izlzkqtium5@raspberrypi-2.musicnaut.iki.fi>

On 12/14/2016 05:12 PM, Aaro Koskinen wrote:
> Hi,
> 
> On Wed, Dec 14, 2016 at 05:00:59PM -0800, Florian Fainelli wrote:
>> On 12/14/2016 04:57 PM, Aaro Koskinen wrote:
>>> On Wed, Dec 14, 2016 at 04:41:13PM -0800, Florian Fainelli wrote:
>>>> On 12/14/2016 04:32 PM, Aaro Koskinen wrote:
>>>>> Git bisect points to:
>>>>>
>>>>> commit ec988ad78ed6d184a7f4ca6b8e962b0e8f1de461
>>>>> Author: Florian Fainelli <f.fainelli@gmail.com>
>>>>> Date:   Tue Dec 6 20:54:43 2016 -0800
>>>>>
>>>>>     phy: Don't increment MDIO bus refcount unless it's a different owner
>>>>>
>>>>> Reverting this patch from v4.9 fixes the issue...
>>>>
>>>> This should help:
>>>>
>>>> diff --git a/drivers/staging/octeon/ethernet.c
>>>> b/drivers/staging/octeon/ethernet.c
>>>> index 8130dfe89745..12ebc4d800c3 100644
>>>> --- a/drivers/staging/octeon/ethernet.c
>>>> +++ b/drivers/staging/octeon/ethernet.c
>>>> @@ -770,6 +770,7 @@ static int cvm_oct_probe(struct platform_device *pdev)
>>>>                         /* Initialize the device private structure. */
>>>>                         struct octeon_ethernet *priv = netdev_priv(dev);
>>>>
>>>> +                       SET_NETDEV_DEV(dev, &pdev->dev);
>>>>                         dev->netdev_ops = &cvm_oct_pow_netdev_ops;
>>>>                         priv->imode = CVMX_HELPER_INTERFACE_MODE_DISABLED;
>>>>                         priv->port = CVMX_PIP_NUM_INPUT_PORTS;
>>>
>>> No, it's still crashing.
>>
>> How about this:
>>
>> diff --git a/drivers/staging/octeon/ethernet.c
>> b/drivers/staging/octeon/ethernet.c
>> index 12ebc4d800c3..4971aa54756a 100644
>> --- a/drivers/staging/octeon/ethernet.c
>> +++ b/drivers/staging/octeon/ethernet.c
>> @@ -817,6 +817,7 @@ static int cvm_oct_probe(struct platform_device *pdev)
>>                         }
>>
>>                         /* Initialize the device private structure. */
>> +                       SET_NETDEV_DEV(dev, &pdev->dev);
>>                         priv = netdev_priv(dev);
>>                         priv->netdev = dev;
>>                         priv->of_node = cvm_oct_node_for_port(pip,
>> interface,
> 
> Yeah, that seems to work - thanks! Could you send this to
> devel@driverdev.osuosl.org as a formal patch?

Sure thing, thanks for verifying it. Sent.
-- 
Florian

      reply	other threads:[~2016-12-15  1:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-15  0:32 [BISECTED] v4.9: OCTEON ethernet crash Aaro Koskinen
2016-12-15  0:41 ` Florian Fainelli
2016-12-15  0:57   ` Aaro Koskinen
2016-12-15  1:00     ` Florian Fainelli
2016-12-15  1:12       ` Aaro Koskinen
2016-12-15  1:14         ` Florian Fainelli [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=2c346015-958a-3f65-f877-8b6fc21165f6@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=davem@davemloft.net \
    --cc=ddaney@caviumnetworks.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