<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: hda: lost interrupt</title>
	<link>http://www.jimohalloran.com/2004/02/15/hda-lost-interrupt/</link>
	<description>Keeping the rabbits out since 1975</description>
	<pubDate>Thu, 17 May 2012 20:18:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3</generator>
		<item>
		<title>By: Tahir Mehmood</title>
		<link>http://www.jimohalloran.com/2004/02/15/hda-lost-interrupt/#comment-484430</link>
		<dc:creator>Tahir Mehmood</dc:creator>
		<pubDate>Sun, 13 Mar 2011 08:41:02 +0000</pubDate>
		<guid>http://www.jimohalloran.com/2004/02/15/hda-lost-interrupt/#comment-484430</guid>
		<description>i am facing same problem with my image stream linux based router,  what should i do, any idea?</description>
		<content:encoded><![CDATA[<p>i am facing same problem with my image stream linux based router,  what should i do, any idea?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: niku</title>
		<link>http://www.jimohalloran.com/2004/02/15/hda-lost-interrupt/#comment-417624</link>
		<dc:creator>niku</dc:creator>
		<pubDate>Fri, 12 Mar 2010 05:29:38 +0000</pubDate>
		<guid>http://www.jimohalloran.com/2004/02/15/hda-lost-interrupt/#comment-417624</guid>
		<description>Bad cable here too. Thanks to OP and people who commented.</description>
		<content:encoded><![CDATA[<p>Bad cable here too. Thanks to OP and people who commented.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peter</title>
		<link>http://www.jimohalloran.com/2004/02/15/hda-lost-interrupt/#comment-65340</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Thu, 02 Aug 2007 21:37:29 +0000</pubDate>
		<guid>http://www.jimohalloran.com/2004/02/15/hda-lost-interrupt/#comment-65340</guid>
		<description>hi folks,
I had same issues with the "lost interrupt". The solution was the right cable PATA, for DMA 133 transfer.
Thanks you.</description>
		<content:encoded><![CDATA[<p>hi folks,<br />
I had same issues with the &#8220;lost interrupt&#8221;. The solution was the right cable PATA, for DMA 133 transfer.<br />
Thanks you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gabriel</title>
		<link>http://www.jimohalloran.com/2004/02/15/hda-lost-interrupt/#comment-18418</link>
		<dc:creator>gabriel</dc:creator>
		<pubDate>Sat, 04 Nov 2006 12:23:59 +0000</pubDate>
		<guid>http://www.jimohalloran.com/2004/02/15/hda-lost-interrupt/#comment-18418</guid>
		<description>fucked up cable here too! thanks paha! that was driving me insane. Changed PATA cable, 100% recovery.

PS: never trust ASUS cables.</description>
		<content:encoded><![CDATA[<p>fucked up cable here too! thanks paha! that was driving me insane. Changed PATA cable, 100% recovery.</p>
<p>PS: never trust ASUS cables.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy Zawodny</title>
		<link>http://www.jimohalloran.com/2004/02/15/hda-lost-interrupt/#comment-267</link>
		<dc:creator>Jeremy Zawodny</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://www.jimohalloran.com/2004/02/15/hda-lost-interrupt/#comment-267</guid>
		<description>And performance probably sucks that way too...</description>
		<content:encoded><![CDATA[<p>And performance probably sucks that way too&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: [b]</title>
		<link>http://www.jimohalloran.com/2004/02/15/hda-lost-interrupt/#comment-268</link>
		<dc:creator>[b]</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://www.jimohalloran.com/2004/02/15/hda-lost-interrupt/#comment-268</guid>
		<description>I had this same problem just before my powersupply died on a redhat 9 2.4.24-6 kernel.  As soon as i replaced my powersupply it stopped reporting this error, so this error may be caused by insufficient power!

Not sure if that helps, but it DEFENATELY fixed my problem =)</description>
		<content:encoded><![CDATA[<p>I had this same problem just before my powersupply died on a redhat 9 2.4.24-6 kernel.  As soon as i replaced my powersupply it stopped reporting this error, so this error may be caused by insufficient power!</p>
<p>Not sure if that helps, but it DEFENATELY fixed my problem =)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frick 'n' Frack</title>
		<link>http://www.jimohalloran.com/2004/02/15/hda-lost-interrupt/#comment-269</link>
		<dc:creator>Frick 'n' Frack</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://www.jimohalloran.com/2004/02/15/hda-lost-interrupt/#comment-269</guid>
		<description>When I try to install Redhat Linux 6.2, The computer seems to stall on these packages: 
ImageMagick, and glibc 2.1.3-15. I can find ImageMagick and uncheck it in custom install, but I cannot find glibc 2.1.3-15. Plus, when I do a control+alt+F5, processing halts, though the cursor is still blinking, and with control+alt+F4 there is the message; "Lost Interrupts". The interrupt message repeats over and over again with no apparent end in sight. You got any suggestions for fixing this problem?</description>
		<content:encoded><![CDATA[<p>When I try to install Redhat Linux 6.2, The computer seems to stall on these packages:<br />
ImageMagick, and glibc 2.1.3-15. I can find ImageMagick and uncheck it in custom install, but I cannot find glibc 2.1.3-15. Plus, when I do a control+alt+F5, processing halts, though the cursor is still blinking, and with control+alt+F4 there is the message; &#8220;Lost Interrupts&#8221;. The interrupt message repeats over and over again with no apparent end in sight. You got any suggestions for fixing this problem?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: paha</title>
		<link>http://www.jimohalloran.com/2004/02/15/hda-lost-interrupt/#comment-270</link>
		<dc:creator>paha</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://www.jimohalloran.com/2004/02/15/hda-lost-interrupt/#comment-270</guid>
		<description>I had the same problem with my Debian and Seagate ST340014A.  But I replaced the IDE-cables with brand new 80-wire cables, and everything went OK.
</description>
		<content:encoded><![CDATA[<p>I had the same problem with my Debian and Seagate ST340014A.  But I replaced the IDE-cables with brand new 80-wire cables, and everything went OK.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

