Re: 2.4.22-rc2 ext2 filesystem corruption

[maney@two14.net (Martin Maney)]

On Wed, Aug 13, 2003 at 11:55:52AM -0300, Marcelo Tosatti wrote:
> Please reback just that change and see if you still get the corruption, 
> please. 
> 
> That way we can be sure. 

At this point the outcome was pretty much a foregone conclusion, but
yep, reverting to ".id" stopped the corruption for this test case.  As
Alan said, it "fixed" it only because that incorrect test happens to
force the driver to use the lower DMA speed.  I had been about to
report on that when your request for the explicit test arrived, but in
short it's that rc1 (and earlier) were disabling the "66" clock speed,
while rc2 was, correctly, finding no reason not to enable it.  The real
bug, be it hardware or software, is that enabling the higher speed
causes the corruption.

I suppose the obvious bandaid would be to add a config option or yet
another /proc/something kluge to let Promise chips be throttled on
purpose, rather than fortuitously.  For my own use, I think I'm just
going to reconfigure to avoid the Promise controller on this machine. 
I would be willing, in principle, to try any proposed fixes, but for a
while longer I would flinch at trying any untested code that I didn't
feel I understood.  Later on this hardware ought to be more available
for testing, at least until it gets repurposed again.

I do have one casual question, if someone should have the answer.  The
driver only talks about a 66MHz high speed; does that mean that the
20265 never gets run at its full speed under Linux, or is it just old
terminology from back when UDMA66 was the top speed?

-- 
An education that does not teach clear, coherent writing
cannot provide our world with thoughtful adults; it gives us instead,
at the best, clever children of all ages.  -- Richard Mitchell