<?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: Linux kernel 2.6 panic/crash [@high temperature] in Qonverge</title>
    <link>https://community.nxp.com/t5/Qonverge/Linux-kernel-2-6-panic-crash-high-temperature/m-p/925986#M424</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt;"&gt;Usually DDR SDRAM operations produce similar error message.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt;"&gt;Test memory on your boar at high temperature.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt;"&gt;NXP CodeWarrior 10.5.1 supports QCVS tools. This tool supports DDR validation:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt;"&gt;&lt;A href="https://www.nxp.com/docs/en/user-guide/QCVS_DDR_User_Guide.pdf"&gt;https://www.nxp.com/docs/en/user-guide/QCVS_DDR_User_Guide.pdf&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt;"&gt;Use this tools for testing DDR setting on your board.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a great day,&lt;BR /&gt;Pavel Chubakov&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "Mark Correct" button. Thank you!&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt; Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 06 Aug 2019 06:29:49 GMT</pubDate>
    <dc:creator>Pavel</dc:creator>
    <dc:date>2019-08-06T06:29:49Z</dc:date>
    <item>
      <title>Linux kernel 2.6 panic/crash [@high temperature]</title>
      <link>https://community.nxp.com/t5/Qonverge/Linux-kernel-2-6-panic-crash-high-temperature/m-p/925985#M423</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 11.5pt; color: #3d3d3d;"&gt;Hi,&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 11.5pt; color: #3d3d3d;"&gt;&amp;nbsp; &amp;nbsp; board details: - BSC 9131 propietary board.&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 11.5pt; color: #3d3d3d;"&gt;&amp;nbsp; &amp;nbsp; Linux kernel version: - 2.6.33.9 [with RT patch].&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 11.5pt; color: #3d3d3d;"&gt;&amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 11.5pt; color: #3d3d3d;"&gt;Issue:&amp;nbsp; - kernel crash with SIGILL 4 [illegal instruction].&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 11.5pt; color: #3d3d3d;"&gt;notes: -&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;OL style="margin-top: 0in;"&gt;&lt;LI style="color: #3d3d3d; margin-left: .5in;"&gt;&lt;SPAN style="font-size: 11.5pt;"&gt;Issue is only noted at high temperature [board at 70 degree Celsius].&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="color: #3d3d3d; margin-left: .5in;"&gt;&lt;SPAN style="font-size: 11.5pt;"&gt;DDR memory is ruled out of this [as independent&amp;nbsp;read/write&amp;nbsp;tests on DDR run perfectly till 90 Celsius].&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="color: #3d3d3d; margin-left: .5in;"&gt;&lt;SPAN style="font-size: 11.5pt;"&gt;when kernel dumped stack trace, the instruction at Failing/Faulting instruction address is &lt;SPAN style="background: lime;"&gt;valid&lt;/SPAN&gt; and &lt;SPAN style="background: lime;"&gt;right&lt;/SPAN&gt;.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="color: #3d3d3d; margin-left: .5in;"&gt;&lt;SPAN style="font-size: 11.5pt;"&gt;Same board with same code runs perfectly at lower temperatures [ &amp;lt; 60 Celsius].&lt;/SPAN&gt;&lt;UL style="margin-top: 0in;"&gt;&lt;LI style="color: #3d3d3d; margin-left: .5in;"&gt;&lt;SPAN style="font-size: 11.5pt;"&gt;So sw is ruled out.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI style="color: #3d3d3d; margin-left: .5in;"&gt;&lt;SPAN style="font-size: 11.5pt;"&gt;The Crash prone hipriTask is ruled out of this as crash.&lt;/SPAN&gt;&lt;UL style="margin-top: 0in;"&gt;&lt;LI style="color: #3d3d3d; margin-left: .5in;"&gt;&lt;SPAN style="font-size: 11.5pt;"&gt;As hipriTask is high priority task and it will be only task which is executing all the time.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="color: #3d3d3d; margin-left: .5in;"&gt;&lt;SPAN style="font-size: 11.5pt;"&gt;Also when crash happens, its not in one place on hipriTask, its all over the hipriTask Source Files.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="color: #3d3d3d; margin-left: .5in;"&gt;&lt;SPAN style="font-size: 11.5pt;"&gt;Also, hipriTask runs fine at lower temperatures.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 11.5pt; color: #3d3d3d;"&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 11.5pt; color: #3d3d3d;"&gt;PPID = 1257, PID = 1265&lt;BR /&gt; Thread = hipriTask&lt;BR /&gt; TID = 1292&lt;BR /&gt; Stack Depth = 15&lt;BR /&gt; Stack Trace:&lt;BR /&gt; 0x1015085C 0x10154C1C 0x00100350 0x101AA56C 0x101A9E48&lt;BR /&gt; 0x101A71D0 0x10190094 0x10173390 0x1019D270 0x101B17B0&lt;BR /&gt; 0x101AB45C 0x1015CA58 0x10149278 0x0F9FA558 0x0F6A2464&lt;BR /&gt; !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 11.5pt; color: #3d3d3d;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 11.5pt; color: #3d3d3d;"&gt;!!! Caught signal SIGILL (Illegal Instruction) !!!&lt;BR /&gt; SIGILL due to: 1&lt;BR /&gt; Faulting instruction address:&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="font-size: 11.5pt; color: red;"&gt;0x101a9cd8&lt;/SPAN&gt;&lt;SPAN style="font-size: 11.5pt; color: #3d3d3d;"&gt;&lt;BR /&gt; Physical frame number of SIGILL address: 0x065c7&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 11.5pt; color: #3d3d3d;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="font-size: 11.5pt; color: #3d3d3d;"&gt;&lt;BR /&gt; =&amp;gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="font-size: 11.5pt; color: red;"&gt;0x101a9cd8&lt;/SPAN&gt;&lt;SPAN style="font-size: 11.5pt; color: #3d3d3d;"&gt;&amp;nbsp;:&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="font-size: 11.5pt; color: red;"&gt;0x38000000&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="font-size: 11.5pt; color: #3d3d3d;"&gt;901F0040 381F0024 901F0034&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 11.5pt; color: #3d3d3d;"&gt;0x38000000 is a valid opcode for addi&amp;nbsp;instruction .&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Jul 2019 16:49:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Qonverge/Linux-kernel-2-6-panic-crash-high-temperature/m-p/925985#M423</guid>
      <dc:creator>rcreddy</dc:creator>
      <dc:date>2019-07-30T16:49:18Z</dc:date>
    </item>
    <item>
      <title>Re: Linux kernel 2.6 panic/crash [@high temperature]</title>
      <link>https://community.nxp.com/t5/Qonverge/Linux-kernel-2-6-panic-crash-high-temperature/m-p/925986#M424</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt;"&gt;Usually DDR SDRAM operations produce similar error message.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt;"&gt;Test memory on your boar at high temperature.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt;"&gt;NXP CodeWarrior 10.5.1 supports QCVS tools. This tool supports DDR validation:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt;"&gt;&lt;A href="https://www.nxp.com/docs/en/user-guide/QCVS_DDR_User_Guide.pdf"&gt;https://www.nxp.com/docs/en/user-guide/QCVS_DDR_User_Guide.pdf&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt;"&gt;Use this tools for testing DDR setting on your board.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a great day,&lt;BR /&gt;Pavel Chubakov&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "Mark Correct" button. Thank you!&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt; Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Aug 2019 06:29:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Qonverge/Linux-kernel-2-6-panic-crash-high-temperature/m-p/925986#M424</guid>
      <dc:creator>Pavel</dc:creator>
      <dc:date>2019-08-06T06:29:49Z</dc:date>
    </item>
  </channel>
</rss>

