<?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>Other NXP Products中的主题 ptp4l send delay request failed and minimum delay request 2^-4 then timeout</title>
    <link>https://community.nxp.com/t5/Other-NXP-Products/ptp4l-send-delay-request-failed-and-minimum-delay-request-2-4/m-p/1312227#M12052</link>
    <description>&lt;P&gt;When running ptp4l as a slave I face (every few second) get the following error:&lt;/P&gt;&lt;DIV class="mceNonEditable lia-copypaste-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;ptp4l[556.407]: timed out while polling for tx timestamp&lt;BR /&gt;ptp4l[556.408]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;STRONG&gt;see please attached two photo log history of the problem -&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://im.ge/i/7C2o1" target="_self"&gt;https://im.ge/i/7C2o1&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://im.ge/i/7CSUf" target="_self"&gt;https://im.ge/i/7CSUf&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I do increase tx_timestamp_timeout, the error happens less frequently, but at 10 ms, ten times the default, it still happens frequently.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As I understand it, the tx timpestamp is returned by the SoC itself after sending the delay request message, so it is strange that it should take this much time. I don't whether the ptp4l author means that it is a driver bug when it takes much time, or when the timestamp does not arrive at all. I can see that the timestamp always arrive eventually when this happens by re-polling.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How come it takes so long time to get back the timestamp? Is this a bug? If not, how long should the timeout value be? how do I fix the problem to prevent that bug happen?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My kernel is based on linux centos ssh.&lt;/P&gt;</description>
    <pubDate>Thu, 22 Jul 2021 22:41:46 GMT</pubDate>
    <dc:creator>jimmy21</dc:creator>
    <dc:date>2021-07-22T22:41:46Z</dc:date>
    <item>
      <title>ptp4l send delay request failed and minimum delay request 2^-4 then timeout</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/ptp4l-send-delay-request-failed-and-minimum-delay-request-2-4/m-p/1312227#M12052</link>
      <description>&lt;P&gt;When running ptp4l as a slave I face (every few second) get the following error:&lt;/P&gt;&lt;DIV class="mceNonEditable lia-copypaste-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;ptp4l[556.407]: timed out while polling for tx timestamp&lt;BR /&gt;ptp4l[556.408]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;STRONG&gt;see please attached two photo log history of the problem -&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://im.ge/i/7C2o1" target="_self"&gt;https://im.ge/i/7C2o1&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://im.ge/i/7CSUf" target="_self"&gt;https://im.ge/i/7CSUf&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I do increase tx_timestamp_timeout, the error happens less frequently, but at 10 ms, ten times the default, it still happens frequently.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As I understand it, the tx timpestamp is returned by the SoC itself after sending the delay request message, so it is strange that it should take this much time. I don't whether the ptp4l author means that it is a driver bug when it takes much time, or when the timestamp does not arrive at all. I can see that the timestamp always arrive eventually when this happens by re-polling.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How come it takes so long time to get back the timestamp? Is this a bug? If not, how long should the timeout value be? how do I fix the problem to prevent that bug happen?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My kernel is based on linux centos ssh.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Jul 2021 22:41:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/ptp4l-send-delay-request-failed-and-minimum-delay-request-2-4/m-p/1312227#M12052</guid>
      <dc:creator>jimmy21</dc:creator>
      <dc:date>2021-07-22T22:41:46Z</dc:date>
    </item>
    <item>
      <title>Re: ptp4l send delay request failed and minimum delay request 2^-4 then timeout</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/ptp4l-send-delay-request-failed-and-minimum-delay-request-2-4/m-p/1312229#M12053</link>
      <description>&lt;P&gt;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/52411"&gt;@yipingwang&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/85543"&gt;@lpm&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Appreciated much you both can help me to fix that problem/bug.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Jul 2021 22:45:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/ptp4l-send-delay-request-failed-and-minimum-delay-request-2-4/m-p/1312229#M12053</guid>
      <dc:creator>jimmy21</dc:creator>
      <dc:date>2021-07-22T22:45:29Z</dc:date>
    </item>
  </channel>
</rss>

