<?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 Pardiso crashes in 2017 MKL only when OMP_NUM_THREADS=2 in Intel® oneAPI Math Kernel Library</title>
    <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Pardiso-crashes-in-2017-MKL-only-when-OMP-NUM-THREADS-2/m-p/1091385#M23278</link>
    <description>&lt;P&gt;I have a small matrix that consistently causes pardiso to crash only when I use OMP_NUM_THREADS=2 or 3. My machine has 12 cpus and any other setting for OMP_NUM_THREADS works. The other odd thing is this same matrix solved without any issue in earlier version of Intel compiler ( 2016 ).&lt;/P&gt;

&lt;P&gt;I modified the example cl_solver_sym_sp_0_based_c to read in my matrix and reproduce my error. I can share my test case if you like. Or is this a known issue with 2017 Intel compiler?&lt;/P&gt;

&lt;P&gt;I have found a workaround is to set iparm[0]=1 . Then I can use any value for OMP_NUM_THREADS. With iparm[0]=0, the crash consistently appears. As mentioned this error is new to 2017 intel compiler. I did not ever experience it before with the same matrix.&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 26 Sep 2016 04:29:59 GMT</pubDate>
    <dc:creator>Ferris_H_</dc:creator>
    <dc:date>2016-09-26T04:29:59Z</dc:date>
    <item>
      <title>Pardiso crashes in 2017 MKL only when OMP_NUM_THREADS=2</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Pardiso-crashes-in-2017-MKL-only-when-OMP-NUM-THREADS-2/m-p/1091385#M23278</link>
      <description>&lt;P&gt;I have a small matrix that consistently causes pardiso to crash only when I use OMP_NUM_THREADS=2 or 3. My machine has 12 cpus and any other setting for OMP_NUM_THREADS works. The other odd thing is this same matrix solved without any issue in earlier version of Intel compiler ( 2016 ).&lt;/P&gt;

&lt;P&gt;I modified the example cl_solver_sym_sp_0_based_c to read in my matrix and reproduce my error. I can share my test case if you like. Or is this a known issue with 2017 Intel compiler?&lt;/P&gt;

&lt;P&gt;I have found a workaround is to set iparm[0]=1 . Then I can use any value for OMP_NUM_THREADS. With iparm[0]=0, the crash consistently appears. As mentioned this error is new to 2017 intel compiler. I did not ever experience it before with the same matrix.&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 26 Sep 2016 04:29:59 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Pardiso-crashes-in-2017-MKL-only-when-OMP-NUM-THREADS-2/m-p/1091385#M23278</guid>
      <dc:creator>Ferris_H_</dc:creator>
      <dc:date>2016-09-26T04:29:59Z</dc:date>
    </item>
    <item>
      <title>yes, the problem with METIS</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Pardiso-crashes-in-2017-MKL-only-when-OMP-NUM-THREADS-2/m-p/1091386#M23279</link>
      <description>&lt;P&gt;yes, the problem with METIS has been addressed into MKL 2017. Could you please check it on your side and give us the results!&lt;/P&gt;</description>
      <pubDate>Mon, 26 Sep 2016 05:59:35 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Pardiso-crashes-in-2017-MKL-only-when-OMP-NUM-THREADS-2/m-p/1091386#M23279</guid>
      <dc:creator>Gennady_F_Intel</dc:creator>
      <dc:date>2016-09-26T05:59:35Z</dc:date>
    </item>
    <item>
      <title>Thanks for the quick reply,</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Pardiso-crashes-in-2017-MKL-only-when-OMP-NUM-THREADS-2/m-p/1091387#M23280</link>
      <description>&lt;P&gt;Thanks for the quick reply, however, the issue I am experiencing is with 2017 MKL. The same matrix solves perfectly in 2016 and older MKL. Seems some bug with the 2017 release. I can provide my test case if you like.&lt;/P&gt;</description>
      <pubDate>Mon, 26 Sep 2016 15:27:41 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Pardiso-crashes-in-2017-MKL-only-when-OMP-NUM-THREADS-2/m-p/1091387#M23280</guid>
      <dc:creator>Ferris_H_</dc:creator>
      <dc:date>2016-09-26T15:27:41Z</dc:date>
    </item>
  </channel>
</rss>

