<?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 Re: iMX6 SabreSD Kernel panic in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/iMX6-SabreSD-Kernel-panic/m-p/1246428#M170918</link>
    <description>&lt;P&gt;In my case the main reason is systemd, I just changed to sysvinit.&lt;/P&gt;</description>
    <pubDate>Tue, 16 Mar 2021 12:24:12 GMT</pubDate>
    <dc:creator>leonardoprates</dc:creator>
    <dc:date>2021-03-16T12:24:12Z</dc:date>
    <item>
      <title>iMX6 SabreSD Kernel panic</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6-SabreSD-Kernel-panic/m-p/1076875#M158075</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm using an iMX6 sabreSD board, &lt;STRONG&gt;SCH-27516 Rev B5, 700-27516 Rev X5&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;sabreSD board boots fine with&amp;nbsp;&lt;STRONG&gt;&lt;EM&gt;NXP i.MX Release Distro 4.14-sumo (sumo)&lt;/EM&gt;&lt;/STRONG&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt;&lt;LI&gt;The issue is when loaded with Kernel v4.19 (warrior release) and the latest release, &lt;STRONG&gt;&lt;EM&gt;NXP i.MX Release Distro 5.4-zeus (zeus)!&lt;/EM&gt; &lt;/STRONG&gt;&lt;A href="https://www.nxp.com/webapp/Download?colCode=L5.4.3_1.0.0_MX6QDLSOLOX&amp;amp;appType=license" rel="nofollow noopener noreferrer" target="_blank"&gt;L5.4.3_1.0.0_MX6QDLSOLOX,&lt;/A&gt; the kernel goes to panic, see below logs.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Supposedly, this is a memory issue only appears on older sabreSD boards, kindly point to some solution to run the latest kernel on older board revisions, also mention board revisions which are currently supported by NXP to run the latest sources.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;[&amp;nbsp;&amp;nbsp; 10.659647] 8&amp;lt;--- cut here ---
[&amp;nbsp;&amp;nbsp; 10.666423] Unable to handle kernel NULL pointer dereference at virtual address 00000001
[&amp;nbsp;&amp;nbsp; 10.682163] pgd = (ptrval)
[&amp;nbsp;&amp;nbsp; 10.690018] [00000001] *pgd=38ea9831, *pte=00000000, *ppte=00000000
[&amp;nbsp; OK&amp;nbsp; ] Started Network Time S[&amp;nbsp;&amp;nbsp; 10.711515] Internal error: Oops: 17 [#1] PREEMPT SMP ARM
&amp;nbsp;nchronization.[
&amp;nbsp;&amp;nbsp; 10.717929] Modules linked in: galcore(O)
[&amp;nbsp;&amp;nbsp; 10.723793] CPU: 1 PID: 305 Comm: udevadm Tainted: G&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; O&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 5.4.3-lts-lf-5.4.y+gf8118585ee3c #1
[&amp;nbsp;&amp;nbsp; 10.733388] Hardware name: Freescale i.MX6 Quad/DualLite (Device Tree)
[&amp;nbsp;&amp;nbsp; 10.740000] PC is at lookup_fast+0x17c/0x2bc
[&amp;nbsp;&amp;nbsp; 10.744300] LR is at kernfs_dop_revalidate+0xb4/0xc4
[&amp;nbsp;&amp;nbsp; 10.749269] pc : [&amp;lt;802386b0&amp;gt;]&amp;nbsp;&amp;nbsp;&amp;nbsp; lr : [&amp;lt;802a7284&amp;gt;]&amp;nbsp;&amp;nbsp;&amp;nbsp; psr: 20010013
[&amp;nbsp;&amp;nbsp; 10.755539] sp : a8f1fd98&amp;nbsp; ip : a8910000&amp;nbsp; fp : d0d0d0d0
[&amp;nbsp;&amp;nbsp; 10.760796] r10: a8f1fdd0&amp;nbsp; r9 : a80379d0&amp;nbsp; r8 : a62deaa0
[&amp;nbsp;&amp;nbsp; 10.760805] r7 : a8f1fdcc&amp;nbsp; r6 : d0d0d0d0&amp;nbsp; r5 : 00000001&amp;nbsp; r4 : a80379d0
[&amp;nbsp;&amp;nbsp; 10.760813] r3 : a8910000&amp;nbsp; r2 : 00000000&amp;nbsp; r1 : 00000000&amp;nbsp; r0 : 00000001
[&amp;nbsp;&amp;nbsp; 10.760826] Flags: nzCv&amp;nbsp; IRQs on&amp;nbsp; FIQs on&amp;nbsp; Mode SVC_32&amp;nbsp; ISA ARM&amp;nbsp; Segment none
[&amp;nbsp;&amp;nbsp; 10.760836] Control: 10c5787d&amp;nbsp; Table: 3905004a&amp;nbsp; DAC: 00000051
[&amp;nbsp;&amp;nbsp; 10.760854] Process udevadm (pid: 305, stack limit = 0x(ptrval))
[&amp;nbsp; OK&amp;nbsp; ] Created slice system-systemd\x2dbacklight.slice.

&lt;/PRE&gt;&lt;P&gt;Error log attached, &lt;/P&gt;&lt;P&gt;-Sajjad Ahmed&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Jun 2020 14:36:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6-SabreSD-Kernel-panic/m-p/1076875#M158075</guid>
      <dc:creator>sajjadahmed</dc:creator>
      <dc:date>2020-06-22T14:36:11Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6 SabreSD Kernel panic</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6-SabreSD-Kernel-panic/m-p/1076876#M158076</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Helo Sajjad Ahmed,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I couldn’t find reports on the latest BSPs not working on that specific version of the SABRE board. I will open an internal escalation to see if the settings and patches on the latest BSPs only support certain revisions of the board and what information we have on which changes would be required. I will let you know as soon as I have more information.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt; Regards,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Jun 2020 22:18:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6-SabreSD-Kernel-panic/m-p/1076876#M158076</guid>
      <dc:creator>gusarambula</dc:creator>
      <dc:date>2020-06-25T22:18:17Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6 SabreSD Kernel panic</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6-SabreSD-Kernel-panic/m-p/1076877#M158077</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Sajjad Ahmed,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I received have two suggestions from our experts. Firstly, they have found two patches that differ on the two releases which may help. Would you please apply them and do some testing to see if it helps?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; 9afc6429e1e6 MLK-23997 arm: dts: imx6qdl: increase the PAD drive strength for usdhc2&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;A href="https://source.codeaurora.org/external/imx/linux-imx/commit/?h=imx_5.4.24_2.1.0&amp;amp;id=9afc6429e1e60c4158eaf2472e05365d4a7ac2a0" target="test_blank"&gt;https://source.codeaurora.org/external/imx/linux-imx/commit/?h=imx_5.4.24_2.1.0&amp;amp;id=9afc6429e1e60c4158eaf2472e05365d4a7ac2a0&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 42f457848d07 ARM: dts: imx6qdl-sabresd: Remove incorrect power supply assignment&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;A href="https://source.codeaurora.org/external/imx/linux-imx/commit/?h=imx_5.4.24_2.1.0&amp;amp;id=42f457848d07be1586e0fd10e7cae2be264ee599" target="test_blank"&gt;https://source.codeaurora.org/external/imx/linux-imx/commit/?h=imx_5.4.24_2.1.0&amp;amp;id=42f457848d07be1586e0fd10e7cae2be264ee599&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The second suggestion is using the zImage type of Kenrel. From the log it seems that you may be using an uImage type of kernel and loading it to address 0x20000000. If you could try loading the zImage kernel in the default address that U-Boot provides, that’s also worth looking at. (Albeit it wouldn’t explain why the same exact variables work on the newer boards).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps!&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 Jul 2020 22:56:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6-SabreSD-Kernel-panic/m-p/1076877#M158077</guid>
      <dc:creator>gusarambula</dc:creator>
      <dc:date>2020-07-31T22:56:32Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6 SabreSD Kernel panic</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6-SabreSD-Kernel-panic/m-p/1237374#M170089</link>
      <description>&lt;P&gt;Did you find a solution? I have got the same issue at same releases.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Feb 2021 17:16:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6-SabreSD-Kernel-panic/m-p/1237374#M170089</guid>
      <dc:creator>leonardoprates</dc:creator>
      <dc:date>2021-02-26T17:16:28Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6 SabreSD Kernel panic</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6-SabreSD-Kernel-panic/m-p/1246428#M170918</link>
      <description>&lt;P&gt;In my case the main reason is systemd, I just changed to sysvinit.&lt;/P&gt;</description>
      <pubDate>Tue, 16 Mar 2021 12:24:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6-SabreSD-Kernel-panic/m-p/1246428#M170918</guid>
      <dc:creator>leonardoprates</dc:creator>
      <dc:date>2021-03-16T12:24:12Z</dc:date>
    </item>
  </channel>
</rss>

