<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Fix for Ryzen users	</title>
	<atom:link href="https://www.dragonflydigest.com/2017/08/11/fix-for-ryzen-users/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.dragonflydigest.com/2017/08/11/fix-for-ryzen-users/</link>
	<description>A running description of activity related to DragonFly BSD.</description>
	<lastBuildDate>Sat, 12 Aug 2017 10:26:43 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>
	<item>
		<title>
		By: Guest		</title>
		<link>https://www.dragonflydigest.com/2017/08/11/fix-for-ryzen-users/comment-page-1/#comment-486694</link>

		<dc:creator><![CDATA[Guest]]></dc:creator>
		<pubDate>Sat, 12 Aug 2017 10:26:43 +0000</pubDate>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=20089#comment-486694</guid>

					<description><![CDATA[This isn&#039;t the first time AMD acknowledged a hardware bug Matt found: http://lists.dragonflybsd.org/pipermail/kernel/2012-March/222494.html]]></description>
			<content:encoded><![CDATA[<p>This isn&#8217;t the first time AMD acknowledged a hardware bug Matt found: <a href="http://lists.dragonflybsd.org/pipermail/kernel/2012-March/222494.html" rel="nofollow ugc">http://lists.dragonflybsd.org/pipermail/kernel/2012-March/222494.html</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: mer		</title>
		<link>https://www.dragonflydigest.com/2017/08/11/fix-for-ryzen-users/comment-page-1/#comment-486692</link>

		<dc:creator><![CDATA[mer]]></dc:creator>
		<pubDate>Sat, 12 Aug 2017 09:33:16 +0000</pubDate>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=20089#comment-486692</guid>

					<description><![CDATA[Dang, that&#039;s a fun one.  Good work on tracking it down and getting AMD to acknowledge it.  My experience has been CPU makers don&#039;t want to admit things like this, but wind up releasing firmware updates/microcode patches that make the problem go away (if they can, that is).

Stuff like this is why we need multiple OSes.]]></description>
			<content:encoded><![CDATA[<p>Dang, that&#8217;s a fun one.  Good work on tracking it down and getting AMD to acknowledge it.  My experience has been CPU makers don&#8217;t want to admit things like this, but wind up releasing firmware updates/microcode patches that make the problem go away (if they can, that is).</p>
<p>Stuff like this is why we need multiple OSes.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Fix for Ryzen users &#8211; FreshBSD.com		</title>
		<link>https://www.dragonflydigest.com/2017/08/11/fix-for-ryzen-users/comment-page-1/#comment-486690</link>

		<dc:creator><![CDATA[Fix for Ryzen users &#8211; FreshBSD.com]]></dc:creator>
		<pubDate>Fri, 11 Aug 2017 22:10:16 +0000</pubDate>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=20089#comment-486690</guid>

					<description><![CDATA[[&#8230;] Go to Source Author: Justin Sherrill [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] Go to Source Author: Justin Sherrill [&#8230;]</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
