<?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>topic LS1046a - Linux Kernel Panic (EDAC FSL_DDR MC0: Err Detect Register: 0x80000018) in Layerscape</title>
    <link>https://community.nxp.com/t5/Layerscape/LS1046a-Linux-Kernel-Panic-EDAC-FSL-DDR-MC0-Err-Detect-Register/m-p/1710175#M13155</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are encountering the following kernel panic caused by the following errors during boot up:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[  129.454177] EDAC FSL_DDR MC0: Err Detect Register: 0x80000018
[  129.454239] SError Interrupt on CPU2, code 0xbf000002 -- SError&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It seems that when we enable &lt;A href="https://cateee.net/lkddb/web-lkddb/ARM64_ERRATUM_843419.html" target="_blank" rel="noopener"&gt;ARM64_ERRATUM_843419&lt;/A&gt;, the kernel panic goes away. This seems odd, since erratum 843419 is specifically for the A53 architecture, but the LS1046a uses the A72 architecture. Even though&amp;nbsp;843419 stops the kernel panic, it causes other software issues (specifically this&amp;nbsp;&lt;A href="http://blog.chinaunix.net/uid-13889805-id-5787750.html" target="_blank" rel="noopener"&gt;http://blog.chinaunix.net/uid-13889805-id-5787750.html&lt;/A&gt;)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is the memory module we are using:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;---=== Manufacturing Information ===---
Manufacturer                                     Fairchild
Manufacturing Location Code                      0x03
Part Number                                      NLY2G7241G071ID32Z
Revision Code                                    0x4845
Manufacturing Date                               2000-W80
Assembly Serial Number                           0xADFF0000&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has the above error been encountered before for LS1046a? Also, what is the relationship between erratum 843419 and the a72 processor? Should we have this option enabled?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for your help.&lt;/P&gt;</description>
    <pubDate>Thu, 24 Aug 2023 01:49:29 GMT</pubDate>
    <dc:creator>james_browning</dc:creator>
    <dc:date>2023-08-24T01:49:29Z</dc:date>
    <item>
      <title>LS1046a - Linux Kernel Panic (EDAC FSL_DDR MC0: Err Detect Register: 0x80000018)</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1046a-Linux-Kernel-Panic-EDAC-FSL-DDR-MC0-Err-Detect-Register/m-p/1710175#M13155</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are encountering the following kernel panic caused by the following errors during boot up:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[  129.454177] EDAC FSL_DDR MC0: Err Detect Register: 0x80000018
[  129.454239] SError Interrupt on CPU2, code 0xbf000002 -- SError&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It seems that when we enable &lt;A href="https://cateee.net/lkddb/web-lkddb/ARM64_ERRATUM_843419.html" target="_blank" rel="noopener"&gt;ARM64_ERRATUM_843419&lt;/A&gt;, the kernel panic goes away. This seems odd, since erratum 843419 is specifically for the A53 architecture, but the LS1046a uses the A72 architecture. Even though&amp;nbsp;843419 stops the kernel panic, it causes other software issues (specifically this&amp;nbsp;&lt;A href="http://blog.chinaunix.net/uid-13889805-id-5787750.html" target="_blank" rel="noopener"&gt;http://blog.chinaunix.net/uid-13889805-id-5787750.html&lt;/A&gt;)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is the memory module we are using:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;---=== Manufacturing Information ===---
Manufacturer                                     Fairchild
Manufacturing Location Code                      0x03
Part Number                                      NLY2G7241G071ID32Z
Revision Code                                    0x4845
Manufacturing Date                               2000-W80
Assembly Serial Number                           0xADFF0000&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has the above error been encountered before for LS1046a? Also, what is the relationship between erratum 843419 and the a72 processor? Should we have this option enabled?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for your help.&lt;/P&gt;</description>
      <pubDate>Thu, 24 Aug 2023 01:49:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1046a-Linux-Kernel-Panic-EDAC-FSL-DDR-MC0-Err-Detect-Register/m-p/1710175#M13155</guid>
      <dc:creator>james_browning</dc:creator>
      <dc:date>2023-08-24T01:49:29Z</dc:date>
    </item>
    <item>
      <title>Re: LS1046a - Linux Kernel Panic (EDAC FSL_DDR MC0: Err Detect Register: 0x80000018)</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1046a-Linux-Kernel-Panic-EDAC-FSL-DDR-MC0-Err-Detect-Register/m-p/1715662#M13209</link>
      <description>&lt;P&gt;&lt;SPAN&gt;ARM64_ERRATUM_843419 is enalbed by default in arch/arm64/Kconfig for all ARM64 platforms (including Cortex-A53,&amp;nbsp; Cortex-A72, etc)&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;user can see the following options are enabled in .config CONFIG_ARM64_ERRATUM_843419=y CONFIG_ARM64_LD_HAS_FIX_ERRATUM_843419=y&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;User should not disable ARM64_ERRATUM_843419.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;we didn't see this issue on our LS1046A boards.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 01 Sep 2023 08:40:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1046a-Linux-Kernel-Panic-EDAC-FSL-DDR-MC0-Err-Detect-Register/m-p/1715662#M13209</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2023-09-01T08:40:26Z</dc:date>
    </item>
    <item>
      <title>Re: LS1046a - Linux Kernel Panic (EDAC FSL_DDR MC0: Err Detect Register: 0x80000018)</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1046a-Linux-Kernel-Panic-EDAC-FSL-DDR-MC0-Err-Detect-Register/m-p/1721659#M13284</link>
      <description>&lt;P&gt;Apologies for the late reply. I have enabled&amp;nbsp;&lt;SPAN&gt;843419, however the same panic is still occurring&amp;nbsp;(I was mistaken when I said the panic goes away previously).&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;If my interpretation of the panic is correct, it seems like the ddr controller is getting an eec error when it tries to read from address&amp;nbsp;0x00020000. Is my understanding correct? If so, is there any suggestion for identifying where the faulty memory access is happening?&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[  148.440201] EDAC FSL_DDR MC0: Captured Data / ECC:   0xffffffff_ffffffff / 0xff
[  148.447336] EDAC FSL_DDR MC0: Err addr: 0x00020000
[  148.452123] EDAC FSL_DDR MC0: PFN: 0x00000020
[  148.456479] EDAC MC0: 1 UE fsl_mc_err on mc#0csrow#0channel#0 (csrow:0 channel:0 page:0x20 offset:0x0 grain:8)&lt;/LI-CODE&gt;</description>
      <pubDate>Wed, 13 Sep 2023 05:25:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1046a-Linux-Kernel-Panic-EDAC-FSL-DDR-MC0-Err-Detect-Register/m-p/1721659#M13284</guid>
      <dc:creator>james_browning</dc:creator>
      <dc:date>2023-09-13T05:25:05Z</dc:date>
    </item>
    <item>
      <title>Re: LS1046a - Linux Kernel Panic (EDAC FSL_DDR MC0: Err Detect Register: 0x80000018)</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1046a-Linux-Kernel-Panic-EDAC-FSL-DDR-MC0-Err-Detect-Register/m-p/1721711#M13286</link>
      <description>&lt;P&gt;You could use "mtest" command provided in u-boot to do DDR memory read and write testing.&lt;/P&gt;
&lt;P&gt;If it fails, please use QCVS DDRv tool provided in CodeWarrior to do DDR validation and optimization, then refine the DDR controller configuration parameters in ATF.&lt;/P&gt;</description>
      <pubDate>Wed, 13 Sep 2023 06:23:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1046a-Linux-Kernel-Panic-EDAC-FSL-DDR-MC0-Err-Detect-Register/m-p/1721711#M13286</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2023-09-13T06:23:16Z</dc:date>
    </item>
    <item>
      <title>Re: LS1046a - Linux Kernel Panic (EDAC FSL_DDR MC0: Err Detect Register: 0x80000018)</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1046a-Linux-Kernel-Panic-EDAC-FSL-DDR-MC0-Err-Detect-Register/m-p/1726650#M13350</link>
      <description>&lt;P&gt;After further testing we found that a region of ddr contains bad ECCs after a warm reboot. We feel confident our issue is the same as described in this ticket: &lt;A href="https://community.nxp.com/t5/Layerscape/How-to-fix-ECC-of-DDR4-training-address-after-warm-boot/td-p/1007485" target="_blank" rel="noopener"&gt;https://community.nxp.com/t5/Layerscape/How-to-fix-ECC-of-DDR4-training-address-after-warm-boot/td-p/1007485&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;We have implemented the same warm/cold boot logic as described in the above link in our u-boot as well as atf code. After a warm reboot (when we bypass memory initialization), we find that the range 0x80020000 - 0x8002007f contains bad ECCs. It seems the solution may be to disable ECC checking and then re-initialize the effected region.&lt;BR /&gt;&lt;BR /&gt;Our question then is this, why is the are 0x80020000 being used for DDR training? We have DDR_INIT_ADDR and DDR_INIT_EXT_ADDR both set to 0. Is 0x80020000 just the default calibration address?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please find our ddr controller dump attached&lt;/P&gt;</description>
      <pubDate>Thu, 21 Sep 2023 05:04:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1046a-Linux-Kernel-Panic-EDAC-FSL-DDR-MC0-Err-Detect-Register/m-p/1726650#M13350</guid>
      <dc:creator>james_browning</dc:creator>
      <dc:date>2023-09-21T05:04:11Z</dc:date>
    </item>
    <item>
      <title>Re: LS1046a - Linux Kernel Panic (EDAC FSL_DDR MC0: Err Detect Register: 0x80000018)</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1046a-Linux-Kernel-Panic-EDAC-FSL-DDR-MC0-Err-Detect-Register/m-p/1727011#M13359</link>
      <description>&lt;P&gt;On LS1046A processor, DDR memory address is at 0x80000000.&lt;/P&gt;
&lt;P&gt;I still suggest you use QCVS DDRv tool to do optimization, then refine DDR controller initialization parameters in ATF source code.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Sep 2023 09:08:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1046a-Linux-Kernel-Panic-EDAC-FSL-DDR-MC0-Err-Detect-Register/m-p/1727011#M13359</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2023-09-21T09:08:10Z</dc:date>
    </item>
  </channel>
</rss>

