Fw: [Bug 64081] New: mdiobus_read fail and return -110 when called from get_phy_id r6040: 0000:00:08.0 failed to register MII bus

* Fw: [Bug 64081] New: mdiobus_read fail and return -110 when called from get_phy_id  r6040: 0000:00:08.0 failed to register MII bus
@ 2013-10-30 18:23 Stephen Hemminger
  2013-10-30 18:33 ` Florian Fainelli
  0 siblings, 1 reply; 2+ messages in thread
From: Stephen Hemminger @ 2013-10-30 18:23 UTC (permalink / raw)
  To: netdev

Begin forwarded message:

Date: Wed, 30 Oct 2013 11:10:47 -0700
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "stephen@networkplumber.org" <stephen@networkplumber.org>
Subject: [Bug 64081] New: mdiobus_read fail and return -110 when called from get_phy_id  r6040: 0000:00:08.0 failed to register MII bus

https://bugzilla.kernel.org/show_bug.cgi?id=64081

            Bug ID: 64081
           Summary: mdiobus_read fail and return -110 when called from
                    get_phy_id  r6040: 0000:00:08.0 failed to register MII
                    bus
           Product: Networking
           Version: 2.5
    Kernel Version: 3.10.17
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: Other
          Assignee: shemminger@linux-foundation.org
          Reporter: nils.koehler@ibt-interfaces.de
        Regression: No

I have tracked down an issue I have to get the device driver r6040.c to run on
Kernel 3.10.17.

It fails called get_phy_id.
In fails sometimes randomly on a phy id between 0 and 31.

the chance to get the error is 50% in my case after insmod r6040.ko

The error is caused by the following function:

int mdiobus_read(struct mii_bus *bus, int addr, u32 regnum)
{
    int retval;

    BUG_ON(in_interrupt());

    mutex_lock(&bus->mdio_lock);
    retval = bus->read(bus, addr, regnum);
    mutex_unlock(&bus->mdio_lock);

printk(KERN_INFO "IBT Debug 1 mdiobus_read retval:%d addr:%d
regnum:%d\n",retval,addr,regnum);

    return retval;
}
EXPORT_SYMBOL(mdiobus_read);

I have added a debug trace and in case of failure retval returns -110

This cause a break in get_phy_id flow and driver init fully fails because it
returns the an -EIO 

I saw that the real existing phy id 1 in my case always was propper detected
but the feeding loop try to init up to 31 Phy's and mostly one of them fail.

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 2+ messages in thread