This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Booting system with NFS file system takes too long to boot up



I have an TI EVM DM8168 and I m using tftp kernel and network file system as of now for the machine. While booting up the machine takes a lot of time even though the network connectivity is well established. Following is the boot log:

net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, id=282f014)
net eth1: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:02, id=282f014)
Sending DHCP requests .
PHY: 0:01 - Link is Up - 100/Full
.
DHCP/BOOTP: Ignoring delayed packet
.
DHCP/BOOTP: Ignoring delayed packet
.
DHCP/BOOTP: Ignoring delayed packet
.
DHCP/BOOTP: Ignoring delayed packet
.
DHCP/BOOTP: Ignoring delayed packet
timed out!
IP-Config: Retrying forever (NFS root)...
davinci_mdio davinci_mdio.0: resetting idled controller
net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, id=282f014)
net eth1: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:02, id=282f014)
Sending DHCP requests .
PHY: 0:01 - Link is Up - 100/Full
.
DHCP/BOOTP: Ignoring delayed packet
.
DHCP/BOOTP: Ignoring delayed packet
.
DHCP/BOOTP: Ignoring delayed packet
.
Sometimes, it takes more than 15 minutes just printing these messages. I don't know what is the issue. Earlier it has got an DHCP ip and downloaded tftp kernel but then the after it has loaded the kernel, this process it taking too long, Please give some pointer. 
Any guidance for solving this would be appreciated. 
-Rahul
  • Hi Rahul,

    This post might help you in resolving the issue.

    http://e2e.ti.com/support/embedded/linux/f/354/t/127289.aspx

    Regards

    AnilKumar

    Please mark this Forum post as answered via the Verify Answer button below if it helps answer your question.  Thanks!