<?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中的主题 random mmc error</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/random-mmc-error/m-p/382587#M55188</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Every once in a while we are starting our custom board and we are getting this panic (&lt;SPAN style="font-size: 13.3333330154419px;"&gt;mmcblk0: error -84 transferring data...&lt;/SPAN&gt;) reading the EMMC memory, any idea of what could be? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.091481] Waiting for root device /dev/mmcblk0p2...&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.124622] mmc1: new DDR MMC card at address 0001&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.130853] mmcblk0: mmc1:0001 SEM08G 7.39 GiB&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.135739] mmcblk0boot0: mmc1:0001 SEM08G partition 1 1.00 MiB&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.141926] mmcblk0boot1: mmc1:0001 SEM08G partition 2 1.00 MiB&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.148078] mmcblk0rpmb: mmc1:0001 SEM08G partition 3 128 KiB&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.160665] mmcblk0: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0xb00&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.170093] mmcblk0: retrying using single block read&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.175813] mmcblk0: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.185118] blk_update_request: I/O error, dev mmcblk0, sector 0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.192554] mmcblk0: error -84 transferring data, sector 1, nr 7, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.201820] blk_update_request: I/O error, dev mmcblk0, sector 1&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.208486] mmcblk0: error -84 transferring data, sector 2, nr 6, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.217744] blk_update_request: I/O error, dev mmcblk0, sector 2&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.224426] mmcblk0: error -84 transferring data, sector 3, nr 5, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.233683] blk_update_request: I/O error, dev mmcblk0, sector 3&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.240334] mmcblk0: error -84 transferring data, sector 4, nr 4, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.249594] blk_update_request: I/O error, dev mmcblk0, sector 4&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.256276] mmcblk0: error -84 transferring data, sector 5, nr 3, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.265533] blk_update_request: I/O error, dev mmcblk0, sector 5&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.272198] mmcblk0: error -84 transferring data, sector 6, nr 2, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.281431] blk_update_request: I/O error, dev mmcblk0, sector 6&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.288133] mmcblk0: error -84 transferring data, sector 7, nr 1, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.297398] blk_update_request: I/O error, dev mmcblk0, sector 7&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.303607] Buffer I/O error on dev mmcblk0, logical block 0, async page read&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.311805] mmcblk0: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0xb00&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.321205] mmcblk0: retrying using single block read&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.326917] mmcblk0: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.336166] blk_update_request: I/O error, dev mmcblk0, sector 0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.342823] mmcblk0: error -84 transferring data, sector 1, nr 7, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.352071] blk_update_request: I/O error, dev mmcblk0, sector 1&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.358705] mmcblk0: error -84 transferring data, sector 2, nr 6, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.368582] mmcblk0: error -84 transferring data, sector 3, nr 5, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.378457] mmcblk0: error -84 transferring data, sector 4, nr 4, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.388336] mmcblk0: error -84 transferring data, sector 5, nr 3, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.398203] mmcblk0: error -84 transferring data, sector 6, nr 2, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.408137] mmcblk0: error -84 transferring data, sector 7, nr 1, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.417390] Buffer I/O error on dev mmcblk0, logical block 0, async page read&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.424706]&amp;nbsp; mmcblk0: unable to read partition table&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.542241] VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2): error -6&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.550165] Please append a correct "root=" boot option; here are the available partitions:&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.558638] b300&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 7757824 mmcblk0&amp;nbsp; driver: mmcblk&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.564084] b318&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 128 mmcblk0rpmb&amp;nbsp; (driver?)&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.569370] b310&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1024 mmcblk0boot1&amp;nbsp; (driver?)&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.574795] b308&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1024 mmcblk0boot0&amp;nbsp; (driver?)&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.580274] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 12 Mar 2015 17:17:27 GMT</pubDate>
    <dc:creator>javiermarto</dc:creator>
    <dc:date>2015-03-12T17:17:27Z</dc:date>
    <item>
      <title>random mmc error</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/random-mmc-error/m-p/382587#M55188</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Every once in a while we are starting our custom board and we are getting this panic (&lt;SPAN style="font-size: 13.3333330154419px;"&gt;mmcblk0: error -84 transferring data...&lt;/SPAN&gt;) reading the EMMC memory, any idea of what could be? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.091481] Waiting for root device /dev/mmcblk0p2...&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.124622] mmc1: new DDR MMC card at address 0001&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.130853] mmcblk0: mmc1:0001 SEM08G 7.39 GiB&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.135739] mmcblk0boot0: mmc1:0001 SEM08G partition 1 1.00 MiB&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.141926] mmcblk0boot1: mmc1:0001 SEM08G partition 2 1.00 MiB&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.148078] mmcblk0rpmb: mmc1:0001 SEM08G partition 3 128 KiB&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.160665] mmcblk0: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0xb00&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.170093] mmcblk0: retrying using single block read&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.175813] mmcblk0: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.185118] blk_update_request: I/O error, dev mmcblk0, sector 0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.192554] mmcblk0: error -84 transferring data, sector 1, nr 7, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.201820] blk_update_request: I/O error, dev mmcblk0, sector 1&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.208486] mmcblk0: error -84 transferring data, sector 2, nr 6, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.217744] blk_update_request: I/O error, dev mmcblk0, sector 2&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.224426] mmcblk0: error -84 transferring data, sector 3, nr 5, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.233683] blk_update_request: I/O error, dev mmcblk0, sector 3&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.240334] mmcblk0: error -84 transferring data, sector 4, nr 4, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.249594] blk_update_request: I/O error, dev mmcblk0, sector 4&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.256276] mmcblk0: error -84 transferring data, sector 5, nr 3, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.265533] blk_update_request: I/O error, dev mmcblk0, sector 5&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.272198] mmcblk0: error -84 transferring data, sector 6, nr 2, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.281431] blk_update_request: I/O error, dev mmcblk0, sector 6&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.288133] mmcblk0: error -84 transferring data, sector 7, nr 1, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.297398] blk_update_request: I/O error, dev mmcblk0, sector 7&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.303607] Buffer I/O error on dev mmcblk0, logical block 0, async page read&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.311805] mmcblk0: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0xb00&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.321205] mmcblk0: retrying using single block read&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.326917] mmcblk0: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.336166] blk_update_request: I/O error, dev mmcblk0, sector 0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.342823] mmcblk0: error -84 transferring data, sector 1, nr 7, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.352071] blk_update_request: I/O error, dev mmcblk0, sector 1&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.358705] mmcblk0: error -84 transferring data, sector 2, nr 6, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.368582] mmcblk0: error -84 transferring data, sector 3, nr 5, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.378457] mmcblk0: error -84 transferring data, sector 4, nr 4, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.388336] mmcblk0: error -84 transferring data, sector 5, nr 3, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.398203] mmcblk0: error -84 transferring data, sector 6, nr 2, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.408137] mmcblk0: error -84 transferring data, sector 7, nr 1, cmd response 0x900, card status 0x0&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.417390] Buffer I/O error on dev mmcblk0, logical block 0, async page read&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.424706]&amp;nbsp; mmcblk0: unable to read partition table&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.542241] VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2): error -6&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.550165] Please append a correct "root=" boot option; here are the available partitions:&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.558638] b300&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 7757824 mmcblk0&amp;nbsp; driver: mmcblk&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.564084] b318&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 128 mmcblk0rpmb&amp;nbsp; (driver?)&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.569370] b310&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1024 mmcblk0boot1&amp;nbsp; (driver?)&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.574795] b308&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1024 mmcblk0boot0&amp;nbsp; (driver?)&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.580274] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Mar 2015 17:17:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/random-mmc-error/m-p/382587#M55188</guid>
      <dc:creator>javiermarto</dc:creator>
      <dc:date>2015-03-12T17:17:27Z</dc:date>
    </item>
    <item>
      <title>Re: random mmc error</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/random-mmc-error/m-p/382588#M55189</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Javier&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in general such errors may be caused by signal&lt;/P&gt;&lt;P&gt;integrity (poor signal shape), it may be recommended to&lt;/P&gt;&lt;P&gt;tweak driver strength of i.MX6 pads with IOMUXC_SW_PAD_CTL_PAD&lt;/P&gt;&lt;P&gt;SPEED,DSE,SRE settings and recheck board layout&lt;/P&gt;&lt;P&gt;sect.3.5.8 High speed signal routing recommendations &lt;A href="http://cache.freescale.com/files/32bit/doc/user_guide/IMX6DQ6SDLHDG.pdf?fasp=1&amp;amp;WT_TYPE=Users%20Guides&amp;amp;WT_VENDOR=FREESCALE&amp;amp;WT_FILE_FORMAT=pdf&amp;amp;WT_ASSET=Documentation&amp;amp;fileExt=.pdf"&gt;IMX6DQ6SDLHDG&lt;/A&gt; &lt;/P&gt;&lt;P&gt;for SD module interfaces. One can try to work with decreased operating frequency.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;igor&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Mar 2015 01:01:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/random-mmc-error/m-p/382588#M55189</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2015-03-13T01:01:31Z</dc:date>
    </item>
    <item>
      <title>Re: random mmc error</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/random-mmc-error/m-p/382589#M55190</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Javier,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;depending on the eMMC used and the kernel version this can also be a problem in the MMC driver stack. I remember we saw also these kind of errors in some situations on our i.MX base modules. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Background: there is a lot of fixing in handling timout and recover from failed commands in the mainline kernels. If you currently use an SDK kernel, could you try current mainline?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Markus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Mar 2015 08:08:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/random-mmc-error/m-p/382589#M55190</guid>
      <dc:creator>markusniebel</dc:creator>
      <dc:date>2015-03-13T08:08:56Z</dc:date>
    </item>
  </channel>
</rss>

