<?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: IMX6Q Linux Kernel 4.14.336 Crash observed randomly in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/IMX6Q-Linux-Kernel-4-14-336-Crash-observed-randomly/m-p/1953930#M228402</link>
    <description>&lt;P&gt;we are seeing issues in 80-90% boards (6-7 boards) in Test Bed, Frequency vary from 1-2 days.&amp;nbsp; we did not do DDR Stress Test, As this product exist from couple of years, did not seen these issue. Earlier we had not noticed with previous kernel version,&amp;nbsp; we are reverifying with 4.14.327 with same test bed configuration. if you suggest DDR stress test will help to analyze issue,&amp;nbsp; we can perform.&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 13 Sep 2024 04:33:16 GMT</pubDate>
    <dc:creator>rajad</dc:creator>
    <dc:date>2024-09-13T04:33:16Z</dc:date>
    <item>
      <title>IMX6Q Linux Kernel 4.14.336 Crash observed randomly</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX6Q-Linux-Kernel-4-14-336-Crash-observed-randomly/m-p/1953477#M228379</link>
      <description>&lt;P&gt;we have custom board based on IMX6Q processor, we are observing kernel crash in version 4.14.336 randomly.&amp;nbsp; Following is crash dump&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Sep 10 09:39:52 user.emerg kernel: BUG: spinlock already unlocked on CPU#1, sh/8911&lt;BR /&gt;Sep 10 09:39:52 user.emerg kernel: lock: rcu_preempt_state+0x0/0x300, .magic: dead4ead, .owner: &amp;lt;none&amp;gt;/-1, .owner_cpu: -1&lt;BR /&gt;Sep 10 09:39:52 user.warn kernel: CPU: 1 PID: 8911 Comm: sh Tainted: G O 4.14.336 #1&lt;BR /&gt;Sep 10 09:39:52 user.warn kernel: Hardware name: Freescale i.MX6 Quad/DualLite (Device Tree)&lt;BR /&gt;Sep 10 09:39:52 user.warn kernel: [&amp;lt;8010ed8c&amp;gt;] (unwind_backtrace) from [&amp;lt;8010b598&amp;gt;] (show_stack+0x10/0x14)&lt;BR /&gt;Sep 10 09:39:52 user.warn kernel: [&amp;lt;8010b598&amp;gt;] (show_stack) from [&amp;lt;80610e84&amp;gt;] (dump_stack+0x84/0x98)&lt;BR /&gt;Sep 10 09:39:52 user.warn kernel: [&amp;lt;80610e84&amp;gt;] (dump_stack) from [&amp;lt;801663e0&amp;gt;] (do_raw_spin_unlock+0xc0/0x11c)&lt;BR /&gt;Sep 10 09:39:52 user.warn kernel: [&amp;lt;801663e0&amp;gt;] (do_raw_spin_unlock) from [&amp;lt;806175fc&amp;gt;] (_raw_spin_unlock_irqrestore+0xc/0x44)&lt;BR /&gt;Sep 10 09:39:52 user.warn kernel: [&amp;lt;806175fc&amp;gt;] (_raw_spin_unlock_irqrestore) from [&amp;lt;8017a2c0&amp;gt;] (note_gp_changes+0x70/0x98)&lt;BR /&gt;Sep 10 09:39:52 user.warn kernel: [&amp;lt;8017a2c0&amp;gt;] (note_gp_changes) from [&amp;lt;8017a610&amp;gt;] (rcu_process_callbacks+0xb4/0x4d4)&lt;BR /&gt;Sep 10 09:39:52 user.warn kernel: [&amp;lt;8017a610&amp;gt;] (rcu_process_callbacks) from [&amp;lt;801015f8&amp;gt;] (__do_softirq+0xd8/0x230)&lt;BR /&gt;Sep 10 09:39:52 user.warn kernel: [&amp;lt;801015f8&amp;gt;] (__do_softirq) from [&amp;lt;8012abe4&amp;gt;] (irq_exit+0xbc/0x104)&lt;BR /&gt;Sep 10 09:39:52 user.warn kernel: [&amp;lt;8012abe4&amp;gt;] (irq_exit) from [&amp;lt;8016b818&amp;gt;] (__handle_domain_irq+0x80/0xe8)&lt;BR /&gt;Sep 10 09:39:52 user.warn kernel: [&amp;lt;8016b818&amp;gt;] (__handle_domain_irq) from [&amp;lt;801014d8&amp;gt;] (gic_handle_irq+0x4c/0x90)&lt;BR /&gt;Sep 10 09:39:52 user.warn kernel: [&amp;lt;801014d8&amp;gt;] (gic_handle_irq) from [&amp;lt;8010bfcc&amp;gt;] (__irq_svc+0x6c/0xa8)&lt;BR /&gt;Sep 10 09:39:52 user.warn kernel: Exception stack(0xa8d81dd0 to 0xa8d81e18)&lt;BR /&gt;Sep 10 09:39:52 user.warn kernel: 1dc0: 00000001 bfb6a9e0 00000002 00000002&lt;BR /&gt;Sep 10 09:39:52 user.warn kernel: 1de0: 00000001 ffffe000 801dbca8 00000000 309cf75f 000000e2 a94bb388 a8d81e34&lt;BR /&gt;Sep 10 09:39:52 user.warn kernel: 1e00: 00000000 a8d81e20 801dbca8 80148594 800f0113 ffffffff&lt;BR /&gt;Sep 10 09:39:52 user.warn kernel: [&amp;lt;8010bfcc&amp;gt;] (__irq_svc) from [&amp;lt;80148594&amp;gt;] (preempt_count_add+0x64/0x14c)&lt;BR /&gt;Sep 10 09:39:52 user.warn kernel: [&amp;lt;80148594&amp;gt;] (preempt_count_add) from [&amp;lt;801dbca8&amp;gt;] (__lru_cache_add+0x10/0xd4)&lt;BR /&gt;Sep 10 09:39:52 user.warn kernel: [&amp;lt;801dbca8&amp;gt;] (__lru_cache_add) from [&amp;lt;801f91b4&amp;gt;] (handle_mm_fault+0x4d4/0xa18)&lt;BR /&gt;Sep 10 09:39:52 user.warn kernel: [&amp;lt;801f91b4&amp;gt;] (handle_mm_fault) from [&amp;lt;801130a0&amp;gt;] (do_page_fault+0x114/0x390)&lt;BR /&gt;Sep 10 09:39:52 user.warn kernel: [&amp;lt;801130a0&amp;gt;] (do_page_fault) from [&amp;lt;80101328&amp;gt;] (do_DataAbort+0x50/0xe8)&lt;BR /&gt;Sep 10 09:39:52 user.warn kernel: [&amp;lt;80101328&amp;gt;] (do_DataAbort) from [&amp;lt;8010c35c&amp;gt;] (__dabt_usr+0x3c/0x40)&lt;BR /&gt;Sep 10 09:39:52 user.warn kernel: Exception stack(0xa8d81fb0 to 0xa8d81ff8)&lt;BR /&gt;Sep 10 09:39:52 user.warn kernel: 1fa0: 004e2630 00000000 2e028c8c 50a73ffc&lt;BR /&gt;Sep 10 09:39:52 user.warn kernel: 1fc0: 004d9398 004da008 00000000 00000000 00000000 00000000 004d9398 00000000&lt;BR /&gt;Sep 10 09:39:52 user.warn kernel: 1fe0: 004e2630 7ea5b370 00430af9 76e3af06 600f0030 ffffffff'&lt;/P&gt;&lt;P&gt;any one else seen similar issues/need pointer to identify root cause.&lt;/P&gt;</description>
      <pubDate>Thu, 12 Sep 2024 12:33:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX6Q-Linux-Kernel-4-14-336-Crash-observed-randomly/m-p/1953477#M228379</guid>
      <dc:creator>rajad</dc:creator>
      <dc:date>2024-09-12T12:33:30Z</dc:date>
    </item>
    <item>
      <title>Re: IMX6Q Linux Kernel 4.14.336 Crash observed randomly</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX6Q-Linux-Kernel-4-14-336-Crash-observed-randomly/m-p/1953739#M228397</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;Is your board able to pass the DDR stress test? An over-night test could be helpful in this case.&lt;/P&gt;
&lt;P&gt;How often do you see this crash in your boards? How many boards presents this issue?&lt;/P&gt;
&lt;P&gt;Best regards.&lt;/P&gt;</description>
      <pubDate>Thu, 12 Sep 2024 22:10:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX6Q-Linux-Kernel-4-14-336-Crash-observed-randomly/m-p/1953739#M228397</guid>
      <dc:creator>JorgeCas</dc:creator>
      <dc:date>2024-09-12T22:10:05Z</dc:date>
    </item>
    <item>
      <title>Re: IMX6Q Linux Kernel 4.14.336 Crash observed randomly</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX6Q-Linux-Kernel-4-14-336-Crash-observed-randomly/m-p/1953930#M228402</link>
      <description>&lt;P&gt;we are seeing issues in 80-90% boards (6-7 boards) in Test Bed, Frequency vary from 1-2 days.&amp;nbsp; we did not do DDR Stress Test, As this product exist from couple of years, did not seen these issue. Earlier we had not noticed with previous kernel version,&amp;nbsp; we are reverifying with 4.14.327 with same test bed configuration. if you suggest DDR stress test will help to analyze issue,&amp;nbsp; we can perform.&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 04:33:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX6Q-Linux-Kernel-4-14-336-Crash-observed-randomly/m-p/1953930#M228402</guid>
      <dc:creator>rajad</dc:creator>
      <dc:date>2024-09-13T04:33:16Z</dc:date>
    </item>
  </channel>
</rss>

