Re: Via apollo KX133 ide bug in 2.4.x

Vojtech Pavlik
2001-01-21T12:25:24Z

On Sat, Jan 20, 2001 at 04:32:36PM -0500, safemode wrote:
> Peter Horton wrote:
>
> > On Thu, Jan 20, 2000 at 08:38:12AM +0000, Peter Horton wrote:
> > >
> > > I think I'm suffering the same thing on my new Asus A7V. Yesterday I got a
> > > single "error in bitmap, remounting read only" type error, and today I got
> > > some files in /tmp that returned I/O error when stat()ed. I do have DMA
> > > enabled, but only UDMA33. I've done several kernel compiles with no
> > > problems at all so looks like something is on the edge. Think I might go
> > > back to 2.2.x for a bit and see what happens, or maybe just remove the VIA
> > > driver :-((.
> > >
> >
> > I apologise for following up my own E-mail, but there is something I'm
> > missing here (maybe a whole lot of something). Anyone know how come we're
> > seeing silent corruption ... I thought this UDMA stuff was all checksummed
> > ? If there error is outside the data I assume the driver would notice ?
> >
> > P.
>
> The thing is, even with UDMA disabled in the kernel, I still see the corruption
> with 2.4.x (release) and above. Anything written while using the kernel is
> corrupted. Much of the stuff will read fine (files) ... but I believe
> directories get the IO error immediately and some files do also. Everything is
> seen as corrupted when you fsck a partition where this kernel has been run and
> created files on. This is a silent corruption without any errors reported and
> I've only tested it on ext2. You cannot create FS's with these kernels (at
> least on the VIA chipsets) since they too are corrupted (note, only tested ext2
> fs). I did disable UDMA everywhere and still saw it happen, this problem is
> not present in older 2.4.0-test kernels so it's something in the late
> pre-release stage and into the release stage.

Do you have the via driver compiled in? If yes, try without, if no, try
with it ...

--
Vojtech Pavlik
SuSE Labs