<story><title>AMD Ryzen Machine Crashes on a Sequence of FMA3 Instructions</title><url>http://forum.hwbot.org/showthread.php?t=167605</url></story><parent_chain><item><author>CalChris</author><text>I think the original &lt;i&gt;hwbot&lt;/i&gt; posting is the better article.&lt;p&gt;&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;forum.hwbot.org&amp;#x2F;showthread.php?t=167605&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;forum.hwbot.org&amp;#x2F;showthread.php?t=167605&lt;/a&gt;&lt;p&gt;The original post has been updated as more facts came along. It verified that the bug was reproducible on other machines. And then it said:&lt;p&gt;&lt;pre&gt;&lt;code&gt;  Update 3&amp;#x2F;16&amp;#x2F;2017:

  As much as I had least expected this to be the case, this appears to have been confirmed as an errata in the AMD Zen processor.
&lt;/code&gt;&lt;/pre&gt;
And then it goes on to say:&lt;p&gt;&lt;pre&gt;&lt;code&gt;  Fortunately, it&amp;#x27;s one that is fixable with a microcode update and will not result in something catastrophic like a recall or the disabling of features.
&lt;/code&gt;&lt;/pre&gt;
Basically, this is an &lt;i&gt;awesome&lt;/i&gt; bug report. HN should link to it rather than the &lt;i&gt;techpowerup&lt;/i&gt; article.</text></item></parent_chain><comment><author>sriramkarnati</author><text>The issue seems to be fixed: &lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;forum.hwbot.org&amp;#x2F;showpost.php?p=480922&amp;amp;postcount=30&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;forum.hwbot.org&amp;#x2F;showpost.php?p=480922&amp;amp;postcount=30&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;forum.hwbot.org&amp;#x2F;showpost.php?p=480524&amp;amp;postcount=25&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;forum.hwbot.org&amp;#x2F;showpost.php?p=480524&amp;amp;postcount=25&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.bit-tech.net&amp;#x2F;news&amp;#x2F;hardware&amp;#x2F;2017&amp;#x2F;03&amp;#x2F;21&amp;#x2F;amd-ryzen-fma3-fix-promise&amp;#x2F;1&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.bit-tech.net&amp;#x2F;news&amp;#x2F;hardware&amp;#x2F;2017&amp;#x2F;03&amp;#x2F;21&amp;#x2F;amd-ryzen-...&lt;/a&gt;</text></comment>
<story><title>AMD Ryzen Machine Crashes on a Sequence of FMA3 Instructions</title><url>http://forum.hwbot.org/showthread.php?t=167605</url></story><parent_chain><item><author>CalChris</author><text>I think the original &lt;i&gt;hwbot&lt;/i&gt; posting is the better article.&lt;p&gt;&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;forum.hwbot.org&amp;#x2F;showthread.php?t=167605&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;forum.hwbot.org&amp;#x2F;showthread.php?t=167605&lt;/a&gt;&lt;p&gt;The original post has been updated as more facts came along. It verified that the bug was reproducible on other machines. And then it said:&lt;p&gt;&lt;pre&gt;&lt;code&gt;  Update 3&amp;#x2F;16&amp;#x2F;2017:

  As much as I had least expected this to be the case, this appears to have been confirmed as an errata in the AMD Zen processor.
&lt;/code&gt;&lt;/pre&gt;
And then it goes on to say:&lt;p&gt;&lt;pre&gt;&lt;code&gt;  Fortunately, it&amp;#x27;s one that is fixable with a microcode update and will not result in something catastrophic like a recall or the disabling of features.
&lt;/code&gt;&lt;/pre&gt;
Basically, this is an &lt;i&gt;awesome&lt;/i&gt; bug report. HN should link to it rather than the &lt;i&gt;techpowerup&lt;/i&gt; article.</text></item></parent_chain><comment><author>gghh</author><text>ah! the author of that hwbot.org post is Alex Yee; I remember his name as he wrote that insanely upvoted (and awesome) stackoverflow answer on branch misprediction: &lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;stackoverflow.com&amp;#x2F;a&amp;#x2F;11227902&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;stackoverflow.com&amp;#x2F;a&amp;#x2F;11227902&lt;/a&gt;</text></comment>