<?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: crashed in pardiso ( mkl 10.2) in Intel® oneAPI Math Kernel Library</title>
    <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/crashed-in-pardiso-mkl-10-2/m-p/872125#M8609</link>
    <description>I came across the same problem when linking C code into the Fortran/BLAS interface (also using Centos, but with newer MKL code -- original post is now 1 year old). Gennady -- I can probably forward a reproducible test code if desired.</description>
    <pubDate>Mon, 12 Jul 2010 12:21:50 GMT</pubDate>
    <dc:creator>jbp1atdukeedu</dc:creator>
    <dc:date>2010-07-12T12:21:50Z</dc:date>
    <item>
      <title>crashed in pardiso ( mkl 10.2)</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/crashed-in-pardiso-mkl-10-2/m-p/872121#M8605</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt; After update to mkl 10.2, the application crashed in pardiso, which was working well under 10.1.&lt;BR /&gt;&lt;BR /&gt;When set MKL_NUM_THREADS=1 the application works also.&lt;BR /&gt;&lt;BR /&gt;My system is Intel Core2 Quad CPU Q9400, CentOS release 5.3 (Final)&lt;BR /&gt;&lt;BR /&gt;[power@localhost se2]$ gcc -v&lt;BR /&gt;Using built-in specs.&lt;BR /&gt;Target: x86_64-unknown-linux-gnu&lt;BR /&gt;Configured with: ../gcc-4.4.0/configure --prefix=/opt --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-languages=c,c++ --with-mpfr=/usr/local&lt;BR /&gt;Thread model: posix&lt;BR /&gt;gcc version 4.4.0 (GCC) &lt;BR /&gt;&lt;BR /&gt;The output information is as following&lt;BR /&gt;&lt;BR /&gt;*** glibc detected *** ./app: free(): invalid next size (normal): 0x00002aaaac05bbd0 ***&lt;BR /&gt;======= Backtrace: =========&lt;BR /&gt;/lib64/libc.so.6[0x324da71ce2]&lt;BR /&gt;/lib64/libc.so.6(cfree+0x8c)[0x324da7590c]&lt;BR /&gt;./app(mkl_serv_mkl_free+0x1d)[0x528681]&lt;BR /&gt;./app[0x683dff]&lt;BR /&gt;./app(mkl_pds_lp64_sfinit_pardiso+0xf7)[0x550f73]&lt;BR /&gt;./app(mkl_pds_lp64_reorder1_pardiso+0xa42)[0x552816]&lt;BR /&gt;./app(mkl_pds_lp64_do_all_pardiso_fc+0x780e)[0x51eed2]&lt;BR /&gt;./app(mkl_pds_lp64_pardiso_c+0x305f)[0x4f5be7]&lt;BR /&gt;./app(mkl_pds_lp64_pardiso+0x44f)[0x4e2c8f]&lt;BR /&gt;./app(pardiso+0x2e)[0x4e283a]&lt;BR /&gt;/home/power/lib/libsparse_solve.so.1(_ZN13CSparseSolve213factorizationEPiS0_Pdi+0x1b3)[0x2b255b5626ef]&lt;BR /&gt;/home/power/lib/libsparse_solve.so.1(_ZN13CSparseSolve213factorizationER12CSparseStorei+0x40)[0x2b255b562534]&lt;BR /&gt;./app(_ZN15CSEFastDecouple5factQERSt3mapIiS0_IidSt4lessIiESaISt4pairIKidEEES2_SaIS3_IS4_S7_EEER12CSparseStore+0x1a1)[0x48d67f]&lt;BR /&gt;./app[0x49a6a5]&lt;BR /&gt;/opt/lib64/libgomp.so.1[0x2b255b9b0172]&lt;BR /&gt;/lib64/libpthread.so.0[0x324e606367]&lt;BR /&gt;/lib64/libc.so.6(clone+0x6d)[0x324dad2f7d]&lt;BR /&gt;</description>
      <pubDate>Thu, 25 Jun 2009 01:23:30 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/crashed-in-pardiso-mkl-10-2/m-p/872121#M8605</guid>
      <dc:creator>minifat</dc:creator>
      <dc:date>2009-06-25T01:23:30Z</dc:date>
    </item>
    <item>
      <title>Re: crashed in pardiso ( mkl 10.2)</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/crashed-in-pardiso-mkl-10-2/m-p/872122#M8606</link>
      <description>&lt;BR /&gt;
&lt;P&gt;This is an unknown problem for us, how can we reproduce the problem?&lt;BR /&gt;What's your linking line? Can you get the test case? ( you can use the private thread for that).&lt;BR /&gt;I have to remind you that CentOS doesn't support officially by MKL but nevertheless it should works ..&lt;BR /&gt;--Gennady&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 25 Jun 2009 05:42:54 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/crashed-in-pardiso-mkl-10-2/m-p/872122#M8606</guid>
      <dc:creator>Gennady_F_Intel</dc:creator>
      <dc:date>2009-06-25T05:42:54Z</dc:date>
    </item>
    <item>
      <title>Re: crashed in pardiso ( mkl 10.2)</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/crashed-in-pardiso-mkl-10-2/m-p/872123#M8607</link>
      <description>&lt;DIV style="margin:0px;"&gt;
&lt;DIV id="quote_reply" style="width: 100%; margin-top: 5px;"&gt;
&lt;DIV style="margin-left:2px;margin-right:2px;"&gt;Quoting - &lt;A href="https://community.intel.com/en-us/profile/334681"&gt;Gennady Fedorov (Intel)&lt;/A&gt;&lt;/DIV&gt;
&lt;DIV style="background-color:#E5E5E5; padding:5px;border: 1px; border-style: inset;margin-left:2px;margin-right:2px;"&gt;&lt;EM&gt;Thank you for your information.&lt;BR /&gt;When I checked the linking line, I found a little diffrent with the example. After erase the -lgomp, It works::)&lt;BR /&gt;&lt;BR /&gt;
&lt;P&gt;This is an unknown problem for us, how can we reproduce the problem?&lt;BR /&gt;What's your linking line? Can you get the test case? ( you can use the private thread for that).&lt;BR /&gt;I have to remind you that CentOS doesn't support officially by MKL but nevertheless it should works ..&lt;BR /&gt;--Gennady&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;/EM&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;BR /&gt;</description>
      <pubDate>Fri, 26 Jun 2009 06:20:10 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/crashed-in-pardiso-mkl-10-2/m-p/872123#M8607</guid>
      <dc:creator>minifat</dc:creator>
      <dc:date>2009-06-26T06:20:10Z</dc:date>
    </item>
    <item>
      <title>Re: crashed in pardiso ( mkl 10.2)</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/crashed-in-pardiso-mkl-10-2/m-p/872124#M8608</link>
      <description>&lt;DIV style="margin:0px;"&gt;Hello minifat,&lt;BR /&gt;Can you please send us a reproducible test case?&lt;BR /&gt;--Gennady&lt;BR /&gt;&lt;BR /&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 13 Jul 2009 15:17:30 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/crashed-in-pardiso-mkl-10-2/m-p/872124#M8608</guid>
      <dc:creator>Gennady_F_Intel</dc:creator>
      <dc:date>2009-07-13T15:17:30Z</dc:date>
    </item>
    <item>
      <title>Re: crashed in pardiso ( mkl 10.2)</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/crashed-in-pardiso-mkl-10-2/m-p/872125#M8609</link>
      <description>I came across the same problem when linking C code into the Fortran/BLAS interface (also using Centos, but with newer MKL code -- original post is now 1 year old). Gennady -- I can probably forward a reproducible test code if desired.</description>
      <pubDate>Mon, 12 Jul 2010 12:21:50 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/crashed-in-pardiso-mkl-10-2/m-p/872125#M8609</guid>
      <dc:creator>jbp1atdukeedu</dc:creator>
      <dc:date>2010-07-12T12:21:50Z</dc:date>
    </item>
    <item>
      <title>Re: crashed in pardiso ( mkl 10.2)</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/crashed-in-pardiso-mkl-10-2/m-p/872126#M8610</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;Please sendyour test case, it will be very useful for reproducing this problem. Anyway, did you check your link line? This KB &lt;A href="http://software.intel.com/en-us/articles/intel-mkl-link-line-advisor/" title="MKL Link Line Advisor"&gt;article&lt;/A&gt; may be helpful.&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;Artem</description>
      <pubDate>Mon, 12 Jul 2010 13:51:05 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/crashed-in-pardiso-mkl-10-2/m-p/872126#M8610</guid>
      <dc:creator>Artem_V_Intel</dc:creator>
      <dc:date>2010-07-12T13:51:05Z</dc:date>
    </item>
  </channel>
</rss>

