Reply-To: <Erik@echohome.org>
From: "Erik Ohrnberger" <Erik@echohome.org>
To: <linux-kernel@vger.kernel.org>
Subject: RE: System / libata IDE controller woes (long)
Date: Sun, 7 Jan 2007 20:41:01 -0500
Organization: EchoHome.org
Message-ID: <!&!AAAAAAAAAAAYAAAAAAAAAIiq6P81RFNNl8OW5VuEScvCgAAAEAAAAASPhcTp3AFGoVU+FXAXe2wBAAAAAA==@EchoHome.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <Pine.LNX.4.64.0612261442120.19760@p34.internal.lan>
Thread-Index: AccpJhmybUONOclCRtC4k/j1aiGcEQDCyngQ
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1007
Lines: 24

Well, after more mucking about, and copying data off of the production LVM
on to the backup LVM, I noticed that no matter where I put this one Seagate
drive, it caused dma_timer_expiry errors.  Once I replaced this drive,
everything settled down again, and has been running normally.

So it's not the old IDE driver code can't handle that many controllers, it
can.  It's also no problem for libata in a similar configuration.  Both work
and work well.

I have to admit that it sure took me a long time to figure out that the
drive was the problem.  I guess that sort of thing should move higher in the
diagnosis decision tree.  You live, you learn.

Thanks for everyone's patience and help in this.  It helped me keep my
sanity through all this.

Cheers,
	Erik.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/