Date: Tue, 12 Aug 2003 13:58:56 -0300 (BRT)
From: Marcelo Tosatti <marcelo@conectiva.com.br>
To: maney@pobox.com
cc: linux-kernel@vger.kernel.org, Stephan von Krawczynski <skraw@ithnet.com>,
       Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: 2.4.22-rc2 ext2 filesystem corruption
In-Reply-To: <20030812151421.GB1074@furrr.two14.net>
Message-ID: <Pine.LNX.4.44.0308121358100.5995-100000@logos.cnet>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1155
Lines: 31


On Tue, 12 Aug 2003, Martin Maney wrote:

> On Tue, Aug 12, 2003 at 11:10:51AM -0300, Marcelo Tosatti wrote:
> > I'll try to reproduce around here. In the meantime can you try to isolate 
> > the corruption. You said it didnt happen with 2.4.21 -- which pre shows up 
> > the problem? 
> 
> Yes, that's on my list.  Unfortunately this has so far only been seen
> on my workstation, and I have to get a bit of work done before I can
> pursue this.  At least I can get some candidates built in the
> background.
> 
> I have tried a few things quickly with 22-rc2, and the short summary
> is:
> 
>  * noapic makes no difference (don't recall why I had UP APIC enabled)
> 
>  * disabling DMA w/hdparm stops the corruption (all normal operation
>    and previous testing has been with DMA enabled)

Okey so its probably the Promise driver. 

Alan, have you ever heard of corruption with the newer Promise driver?

-
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/