<?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のトピックOccasional DHCP-Problems on i.MX53 Gingerbread Android</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Occasional-DHCP-Problems-on-i-MX53-Gingerbread-Android/m-p/449228#M69471</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On our i.MX53-based devices we're still supporting Freescale's Gingerbread Android (r10.4) and we're facing occasional Ethernet problems on these devices: when configured for DHCP, occasionally (i.e. ~1 or 2 times in 1000 boots of a device) the dhcpd_eth-service is stopped/killed immediately after it has just been started during system boot; even before the service sent the first DHCPDISCOVER package.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After several tests, adding lots of debugging messages and tracing the instruction flow it seems that this is caused by some kind of race-condition or timing problem in Freescale's EthernetStateTracker/-Monitor/-Manager-classes(in "fsl-android-r10.4\frameworks\base\core\java\android\net") or the libnetutils (in "fsl-android-r10.4\system\core\libnetutils") used by the Java-classes. Couldn't figure out the proper cause for this problem, yet, though.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anybody else noticed this problem and maybe has a fix for this issue?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Marc&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 11 Jun 2015 09:02:04 GMT</pubDate>
    <dc:creator>MOW</dc:creator>
    <dc:date>2015-06-11T09:02:04Z</dc:date>
    <item>
      <title>Occasional DHCP-Problems on i.MX53 Gingerbread Android</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Occasional-DHCP-Problems-on-i-MX53-Gingerbread-Android/m-p/449228#M69471</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On our i.MX53-based devices we're still supporting Freescale's Gingerbread Android (r10.4) and we're facing occasional Ethernet problems on these devices: when configured for DHCP, occasionally (i.e. ~1 or 2 times in 1000 boots of a device) the dhcpd_eth-service is stopped/killed immediately after it has just been started during system boot; even before the service sent the first DHCPDISCOVER package.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After several tests, adding lots of debugging messages and tracing the instruction flow it seems that this is caused by some kind of race-condition or timing problem in Freescale's EthernetStateTracker/-Monitor/-Manager-classes(in "fsl-android-r10.4\frameworks\base\core\java\android\net") or the libnetutils (in "fsl-android-r10.4\system\core\libnetutils") used by the Java-classes. Couldn't figure out the proper cause for this problem, yet, though.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anybody else noticed this problem and maybe has a fix for this issue?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Marc&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Jun 2015 09:02:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Occasional-DHCP-Problems-on-i-MX53-Gingerbread-Android/m-p/449228#M69471</guid>
      <dc:creator>MOW</dc:creator>
      <dc:date>2015-06-11T09:02:04Z</dc:date>
    </item>
  </channel>
</rss>

