<?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 for Just another FreeBSD Hacker</title>
	<atom:link href="http://blogs.freebsdish.org/kientzle/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.freebsdish.org/kientzle</link>
	<description>Just another blogs.freebsdish.org site</description>
	<lastBuildDate>Fri, 08 Feb 2013 06:22:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>Comment on Watchdogs by kientzle</title>
		<link>http://blogs.freebsdish.org/kientzle/2013/01/05/watchdogs/#comment-44</link>
		<dc:creator>kientzle</dc:creator>
		<pubDate>Fri, 08 Feb 2013 06:22:11 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.freebsdish.org/kientzle/?p=5#comment-44</guid>
		<description><![CDATA[I did finally track down the root cause of the every-20-minute hang. It turned out to be the flow-control setting on the controller. I still don&#039;t know why enabling flow control caused the driver to hang but disabling flow control has definitely fixed the problem for me.

The problem seemed to be triggered by some particular timing related to ARP probes, which is why it happened every 20 minutes (the default ARP timeout).  Figuring out the ARP connection turned out to be crucial to solving the bug, since I was able to set the ARP timeout to 3 seconds and see the problem happen very often, which made it a lot faster to experiment with different possible solutions.]]></description>
		<content:encoded><![CDATA[<p>I did finally track down the root cause of the every-20-minute hang. It turned out to be the flow-control setting on the controller. I still don&#8217;t know why enabling flow control caused the driver to hang but disabling flow control has definitely fixed the problem for me.</p>
<p>The problem seemed to be triggered by some particular timing related to ARP probes, which is why it happened every 20 minutes (the default ARP timeout).  Figuring out the ARP connection turned out to be crucial to solving the bug, since I was able to set the ARP timeout to 3 seconds and see the problem happen very often, which made it a lot faster to experiment with different possible solutions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Watchdogs by kientzle</title>
		<link>http://blogs.freebsdish.org/kientzle/2013/01/05/watchdogs/#comment-43</link>
		<dc:creator>kientzle</dc:creator>
		<pubDate>Sun, 27 Jan 2013 08:02:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.freebsdish.org/kientzle/?p=5#comment-43</guid>
		<description><![CDATA[Update:  The new watchdog logic is holding up well.  I&#039;ve made one improvement recently:  the &quot;nothing to do&quot; case has been fleshed out to include cases where the driver is not running.]]></description>
		<content:encoded><![CDATA[<p>Update:  The new watchdog logic is holding up well.  I&#8217;ve made one improvement recently:  the &#8220;nothing to do&#8221; case has been fleshed out to include cases where the driver is not running.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
