From: Vojtech Pavlik <vojtech@suse.cz>
To: safemode <safemode@voicenet.com>
Cc: Peter Horton <pdh@colonel-panic.com>, linux-kernel@vger.kernel.org
Subject: Re: Via apollo KX133 ide bug in 2.4.x
Date: Sun, 21 Jan 2001 12:40:30 +0100 [thread overview]
Message-ID: <20010121124030.A804@suse.cz> (raw)
In-Reply-To: <3A68DCD1.FACB4135@voicenet.com> <20000120083812.A945@colonel-panic.com> <20010120205608.C2838@colonel-panic.com> <3A6A03F4.DB6C0362@voicenet.com>
In-Reply-To: <3A6A03F4.DB6C0362@voicenet.com>; from safemode@voicenet.com on Sat, Jan 20, 2001 at 04:32:36PM -0500
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-21 12:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-20 0:33 Via apollo KX133 ide bug in 2.4.x safemode
2000-01-20 8:38 ` Peter Horton
2001-01-20 20:56 ` Peter Horton
2001-01-20 21:32 ` safemode
2001-01-21 11:40 ` Vojtech Pavlik [this message]
2001-01-22 22:49 ` Peter Horton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010121124030.A804@suse.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=pdh@colonel-panic.com \
--cc=safemode@voicenet.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox