<?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: Bug with Intel MPI Message Queue Debugging in Intel® MPI Library</title>
    <link>https://community.intel.com/t5/Intel-MPI-Library/Bug-with-Intel-MPI-Message-Queue-Debugging/m-p/1514942#M10869</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.intel.com/t5/user/viewprofilepage/user-id/157027"&gt;@ShivaniK_Intel&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Apologies there appear to be issues with my old Intel account. I can create another ticket if need be, though I imagine it would just be pointing to this one.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;HR /&gt;Could you please try Intel MPI in debug mode and test if the request queues are still available?&lt;BR /&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;I have found the time to try with Intel MPI packaged with OneAPI 2023.2.0 and run with &lt;EM&gt;-genv I_MPI_DEBUG=10&lt;/EM&gt; (I assumed this is what you meant with in debug mode) but it still appears to display the same issues as before.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;All the best,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Josh&lt;/P&gt;</description>
    <pubDate>Thu, 17 Aug 2023 10:13:19 GMT</pubDate>
    <dc:creator>Linaro_Josh</dc:creator>
    <dc:date>2023-08-17T10:13:19Z</dc:date>
    <item>
      <title>Bug with Intel MPI Message Queue Debugging</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Bug-with-Intel-MPI-Message-Queue-Debugging/m-p/1500372#M10724</link>
      <description>&lt;DIV&gt;Hey Intel,&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;I am seeing some issues with the &lt;SPAN class=""&gt;Intel&lt;/SPAN&gt; &lt;SPAN class=""&gt;MPI&lt;/SPAN&gt; "Message Queue Debugger" system that I was wondering if you can look into his bug?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;This issue can be seen when using the Message Queue debugging with Linaro Forge, it appears as though the MQS is not working as expected.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;More specifically, calls to &lt;EM&gt;mqs_image_has_queues&lt;/EM&gt; are always returning 0 (&lt;I&gt;mqs_ok&lt;/I&gt;) but also includes the following message:&lt;BR /&gt;&lt;BLOCKQUOTE&gt;&lt;DIV&gt;&lt;PRE&gt;The symbols and types in the MPICH library used by TotalView
to extract the message queues are not as expected in
the image '%s'
No message queue display is possible.
This is probably an MPICH version or configuration problem.&lt;/PRE&gt;&lt;/DIV&gt;&lt;/BLOCKQUOTE&gt;&lt;/DIV&gt;&lt;DIV&gt;It is worth noting that there were several &lt;I&gt;mqs_field_offset&lt;/I&gt; callbacks made at this time to elements that appear to not exist:&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;BLOCKQUOTE&gt;&lt;DIV&gt;&lt;I&gt;&lt;SPAN&gt;fieldOffset : mqs_type = 0x557143a2f9e0, char* = unexp_head_ptr&lt;/SPAN&gt;&lt;/I&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;I&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/I&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;I&gt;&lt;SPAN&gt;$(gdb) output ((int)&amp;amp;((MPIDIG_comm_t *)1)-&amp;gt;unexp_head_ptr)-1"&lt;/SPAN&gt;&lt;BR /&gt;&lt;/I&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;I&gt;&lt;SPAN&gt;"There is no member named unexp_head_ptr."&lt;/SPAN&gt;&lt;/I&gt;&lt;/DIV&gt;&lt;/BLOCKQUOTE&gt;&lt;BLOCKQUOTE&gt;&lt;DIV&gt;&lt;SPAN&gt;&lt;I&gt;fieldOffset : mqs_type = 0x7fa8d9a72830, char* = comm_next&lt;/I&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;&lt;I&gt;&amp;nbsp;&lt;/I&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;&lt;I&gt;$(gdb) output ((int)&amp;amp;((_MPIR_Comm *)1)-&amp;gt;comm_next)-1&lt;BR /&gt;&lt;/I&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;&lt;I&gt;"There is no member named comm_next"&lt;BR /&gt;&lt;/I&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/BLOCKQUOTE&gt;&lt;BLOCKQUOTE&gt;&lt;DIV&gt;&lt;SPAN&gt;&lt;I&gt;fieldOffset : mqs_type = 0x563bf7816460, char* = am&lt;/I&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;&lt;I&gt;&lt;BR /&gt;$(gdb) output ((int)&amp;amp;((MPIDIG_comm_t *)1)-&amp;gt;unexp_head_ptr)-1\n"&lt;/I&gt;&lt;/SPAN&gt;&lt;DIV&gt;"There is no member named unexp_head_ptr."&lt;/DIV&gt;&lt;/DIV&gt;&lt;/BLOCKQUOTE&gt;&lt;DIV&gt;Perhaps because of the above, it appears that every sequential &lt;I&gt;mqs_setup_operation_iterator &lt;/I&gt;call returns either 1 or 2.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;You can see &lt;A href="https://github.com/pmodels/mpich/issues/6131" target="_blank" rel="noopener"&gt;https://github.com/pmodels/mpich/issues/6131&lt;/A&gt; for an example of a similar issue with MQD on mpich (and a reproducer if you have access to Linaro Forge to test with).&lt;/DIV&gt;</description>
      <pubDate>Thu, 29 Jun 2023 15:01:03 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Bug-with-Intel-MPI-Message-Queue-Debugging/m-p/1500372#M10724</guid>
      <dc:creator>Josh_Linaro</dc:creator>
      <dc:date>2023-06-29T15:01:03Z</dc:date>
    </item>
    <item>
      <title>Re:Bug with Intel MPI Message Queue Debugging</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Bug-with-Intel-MPI-Message-Queue-Debugging/m-p/1501571#M10731</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;We are working on it and will get back to you soon.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards&lt;/P&gt;&lt;P&gt;Shivani&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 04 Jul 2023 05:35:22 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Bug-with-Intel-MPI-Message-Queue-Debugging/m-p/1501571#M10731</guid>
      <dc:creator>ShivaniK_Intel</dc:creator>
      <dc:date>2023-07-04T05:35:22Z</dc:date>
    </item>
    <item>
      <title>Re:Bug with Intel MPI Message Queue Debugging</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Bug-with-Intel-MPI-Message-Queue-Debugging/m-p/1510768#M10830</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thanks for your patience.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;The root cause for this issue is the same as for mpich. The change in the new infrastructure ch4 makes it necessary to implement some features differently.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Could you please try Intel MPI in debug mode and test if the request queues are still available? These can be viewed with the TotalView debugger.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards&lt;/P&gt;&lt;P&gt;Shivani&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 03 Aug 2023 08:46:21 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Bug-with-Intel-MPI-Message-Queue-Debugging/m-p/1510768#M10830</guid>
      <dc:creator>ShivaniK_Intel</dc:creator>
      <dc:date>2023-08-03T08:46:21Z</dc:date>
    </item>
    <item>
      <title>Re:Bug with Intel MPI Message Queue Debugging</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Bug-with-Intel-MPI-Message-Queue-Debugging/m-p/1512774#M10848</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;As we did not hear back from you,could you please respond to my previous post.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards&lt;/P&gt;&lt;P&gt;Shivani&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 10 Aug 2023 05:39:33 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Bug-with-Intel-MPI-Message-Queue-Debugging/m-p/1512774#M10848</guid>
      <dc:creator>ShivaniK_Intel</dc:creator>
      <dc:date>2023-08-10T05:39:33Z</dc:date>
    </item>
    <item>
      <title>Re:Bug with Intel MPI Message Queue Debugging</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Bug-with-Intel-MPI-Message-Queue-Debugging/m-p/1514879#M10867</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;We have not heard back from you. This thread will no longer be monitored by Intel. If you need further assistance, please post a new question.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards&lt;/P&gt;&lt;P&gt;Shivani&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 17 Aug 2023 06:29:56 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Bug-with-Intel-MPI-Message-Queue-Debugging/m-p/1514879#M10867</guid>
      <dc:creator>ShivaniK_Intel</dc:creator>
      <dc:date>2023-08-17T06:29:56Z</dc:date>
    </item>
    <item>
      <title>Re: Bug with Intel MPI Message Queue Debugging</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Bug-with-Intel-MPI-Message-Queue-Debugging/m-p/1514942#M10869</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.intel.com/t5/user/viewprofilepage/user-id/157027"&gt;@ShivaniK_Intel&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Apologies there appear to be issues with my old Intel account. I can create another ticket if need be, though I imagine it would just be pointing to this one.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;HR /&gt;Could you please try Intel MPI in debug mode and test if the request queues are still available?&lt;BR /&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;I have found the time to try with Intel MPI packaged with OneAPI 2023.2.0 and run with &lt;EM&gt;-genv I_MPI_DEBUG=10&lt;/EM&gt; (I assumed this is what you meant with in debug mode) but it still appears to display the same issues as before.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;All the best,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Josh&lt;/P&gt;</description>
      <pubDate>Thu, 17 Aug 2023 10:13:19 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Bug-with-Intel-MPI-Message-Queue-Debugging/m-p/1514942#M10869</guid>
      <dc:creator>Linaro_Josh</dc:creator>
      <dc:date>2023-08-17T10:13:19Z</dc:date>
    </item>
  </channel>
</rss>

