<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>PragmaticPulp</author><text>This depends on the C6 sleep state being enabled and the server not having been restarted for 3 years. It’s extremely unlikely that your cloud provider servers are going to meet this criteria &lt;i&gt;and&lt;/i&gt; ignore this errata for a part they’ve bought thousands of.&lt;p&gt;So no, it’s not going to start randomly hitting people.&lt;p&gt;&amp;gt; Seems comparably problematic to me.&lt;p&gt;Not even close. The FDIV bug hit common operations that could be issued millions of times per second. This bug only applies to specific configurations that haven’t been rebooted for 3 years and has a clear workaround.&lt;p&gt;They’re not even close to comparable in impact and ability to work around. Literally many orders of magnitude different.</text><parent_chain><item><author>gchamonlive</author><text>It means anyone launching amd powered virtual machines on cloud providers can experience this now, at any point, and you don&amp;#x27;t know when it will happen, given this type of CPU could have been bought, booted or rebooted anytime in the past three years.&lt;p&gt;Seems comparably problematic to me.</text></item><item><author>Waterluvian</author><text>It feels a little bit different.&lt;p&gt;One creates uncertainty in all floating point results, given you don’t know when it happens. The other requires you to reboot maybe every ~3 years and you know exactly when it happens.&lt;p&gt;I’m not saying we &lt;i&gt;should&lt;/i&gt; tolerate a defect, but it doesn’t feel nearly as problematic.</text></item><item><author>RobotToaster</author><text>I feel like some of the comments here are missing the point. Yes it&amp;#x27;s only likely to effect a small number of users, so did the intel fdiv bug, both are defective products.&lt;p&gt;Back then intel were pressured into a recall, today we seem too willing to put up with being sold broken stuff.</text></item></parent_chain></comment><story><title>EPYC 7002 CPUs may hang after 1042 days of uptime</title><url>https://old.reddit.com/r/sysadmin/comments/13wmowy/psa_epyc_7002_cpus_may_hang_after_1042_days_of/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>Waterluvian</author><text>I’d prefer a bug that crashes a program than one that quietly inserts wrong data and keeps going.</text><parent_chain><item><author>gchamonlive</author><text>It means anyone launching amd powered virtual machines on cloud providers can experience this now, at any point, and you don&amp;#x27;t know when it will happen, given this type of CPU could have been bought, booted or rebooted anytime in the past three years.&lt;p&gt;Seems comparably problematic to me.</text></item><item><author>Waterluvian</author><text>It feels a little bit different.&lt;p&gt;One creates uncertainty in all floating point results, given you don’t know when it happens. The other requires you to reboot maybe every ~3 years and you know exactly when it happens.&lt;p&gt;I’m not saying we &lt;i&gt;should&lt;/i&gt; tolerate a defect, but it doesn’t feel nearly as problematic.</text></item><item><author>RobotToaster</author><text>I feel like some of the comments here are missing the point. Yes it&amp;#x27;s only likely to effect a small number of users, so did the intel fdiv bug, both are defective products.&lt;p&gt;Back then intel were pressured into a recall, today we seem too willing to put up with being sold broken stuff.</text></item></parent_chain></comment><story><title>EPYC 7002 CPUs may hang after 1042 days of uptime</title><url>https://old.reddit.com/r/sysadmin/comments/13wmowy/psa_epyc_7002_cpus_may_hang_after_1042_days_of/</url></story>