<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>i.MX ProcessorsのトピックIP-Config: Failed to open eth0</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/IP-Config-Failed-to-open-eth0/m-p/169495#M5250</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to get some perspectives from embedded engineers with considerably more experience (than me) looking at kernel boot logs. I am relatively new to embedded Linux. My i.MX53 board's boot environment is in the context of kernel via tftp and root over nfs.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I see:&amp;nbsp;&lt;/P&gt;&lt;P&gt;IP-Config: Failed to open eth0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I wonder, what are the possible conditions for this error to be reported. Perhaps I should be reading linux source code to be sure. But that could take awhile! cscope here I come! :) &amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible for this error message to appear when network conditions cause a problem for the network driver (e.g. not a problem associated to the ethernet driver failing due to wrong driver or bug in driver).&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could any previously failed dhcp-options negotiation with the DHCP server, at an earlier stage of the boot process, cause this error later after the kernel has booted?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is one of those "this was working fine last week" problems. I think nothing was changed; certainly checking for change.&lt;/P&gt;&lt;P&gt;Today, having intermittent success in getting completely booted. Kernel transfers OK over network. I am seeing about 1 out of 8 attempts booting all the way to init. I see this error after&amp;nbsp;kernel&amp;nbsp;loads and just before the attempt to get the root fs. I would not be persisting with the same configuration if I was not seeing an&amp;nbsp;occasional&amp;nbsp;successful boot of root fs over nfs and the command prompt of my Linux distribution (hosted on the NFS box).&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BTW, my lab's network was reconfigured and it is considerably more complex than it was before... so I am suspicious of the network. (new routers and managed switches, new subnets&amp;nbsp;and new fiber links; hosts are on same logical network but way WAY different physical network. lol!; hence more complex and more opportunity for failures, me thinks!). That's why I ask if an external problem (network&amp;nbsp;environment) could generate the "Failed to open eth0"&amp;nbsp;error.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://pastie.org/4134253" target="_blank"&gt;Full Console Log is here&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For comparison, on a successful boot of&amp;nbsp;another i.MX53 board, I see the following in the same spot in the logs:&lt;/P&gt;&lt;P&gt;&lt;A href="http://pastie.org/4134333" target="_blank"&gt;Successful boot log snippet&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR class="Apple-interchange-newline" /&gt;Thx in advance for any and all comments!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 22 Jun 2012 20:40:41 GMT</pubDate>
    <dc:creator>WalterSobchak</dc:creator>
    <dc:date>2012-06-22T20:40:41Z</dc:date>
    <item>
      <title>IP-Config: Failed to open eth0</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IP-Config-Failed-to-open-eth0/m-p/169495#M5250</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to get some perspectives from embedded engineers with considerably more experience (than me) looking at kernel boot logs. I am relatively new to embedded Linux. My i.MX53 board's boot environment is in the context of kernel via tftp and root over nfs.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I see:&amp;nbsp;&lt;/P&gt;&lt;P&gt;IP-Config: Failed to open eth0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I wonder, what are the possible conditions for this error to be reported. Perhaps I should be reading linux source code to be sure. But that could take awhile! cscope here I come! :) &amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible for this error message to appear when network conditions cause a problem for the network driver (e.g. not a problem associated to the ethernet driver failing due to wrong driver or bug in driver).&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could any previously failed dhcp-options negotiation with the DHCP server, at an earlier stage of the boot process, cause this error later after the kernel has booted?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is one of those "this was working fine last week" problems. I think nothing was changed; certainly checking for change.&lt;/P&gt;&lt;P&gt;Today, having intermittent success in getting completely booted. Kernel transfers OK over network. I am seeing about 1 out of 8 attempts booting all the way to init. I see this error after&amp;nbsp;kernel&amp;nbsp;loads and just before the attempt to get the root fs. I would not be persisting with the same configuration if I was not seeing an&amp;nbsp;occasional&amp;nbsp;successful boot of root fs over nfs and the command prompt of my Linux distribution (hosted on the NFS box).&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BTW, my lab's network was reconfigured and it is considerably more complex than it was before... so I am suspicious of the network. (new routers and managed switches, new subnets&amp;nbsp;and new fiber links; hosts are on same logical network but way WAY different physical network. lol!; hence more complex and more opportunity for failures, me thinks!). That's why I ask if an external problem (network&amp;nbsp;environment) could generate the "Failed to open eth0"&amp;nbsp;error.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://pastie.org/4134253" target="_blank"&gt;Full Console Log is here&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For comparison, on a successful boot of&amp;nbsp;another i.MX53 board, I see the following in the same spot in the logs:&lt;/P&gt;&lt;P&gt;&lt;A href="http://pastie.org/4134333" target="_blank"&gt;Successful boot log snippet&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR class="Apple-interchange-newline" /&gt;Thx in advance for any and all comments!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Jun 2012 20:40:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IP-Config-Failed-to-open-eth0/m-p/169495#M5250</guid>
      <dc:creator>WalterSobchak</dc:creator>
      <dc:date>2012-06-22T20:40:41Z</dc:date>
    </item>
  </channel>
</rss>

