From: Ville Herva <vherva@vianova.fi>
To: linux-kernel@vger.kernel.org
Subject: Re: Strange disk corruption with Linux >= 2.6.13
Date: Wed, 28 Sep 2005 11:43:31 +0300 [thread overview]
Message-ID: <20050928084330.GC24760@viasys.com> (raw)
In-Reply-To: <20050927111038.GA22172@ime.usp.br>
On Tue, Sep 27, 2005 at 08:10:39AM -0300, you [Rogério Brito] wrote:
> Hi there. I'm seeing a really strange problem on my system lately and I
> am not really sure that it has anything to do with the kernels.
>
> I would appreciate any guidance with my problems. Any help is welcome.
>
> My desktop has a Duron 1.3GHz (but, for some reason, it runs only at
> 1.1GHz) and an Asus A7V motherboard, with chipset VIA KT133 (not the
> enhanced version KT133A).
You may be running into this problem:
http://www.uwsg.iu.edu/hypermail/linux/kernel/0207.2/0574.html
http://www.cs.helsinki.fi/linux/linux-kernel/2002-02/1727.html
http://www.cs.helsinki.fi/linux/linux-kernel/2002-01/1048.html
http://marc.theaimsgroup.com/?l=linux-kernel&m=99889965423508&w=2
(A google search will turn up more.)
I had enourmeous trouble with Via KT133 and IDE.
Placing network card to a different PCI slot helped somewhat as did
upgrading the bios.
I NEVER got the board stable, and ended up ditching it.
It seemed to be a KT133 Northbridge DMA issue. My impression is that KT133
is utter crap period.
When browsing the viaarena.com forums, I found huge number of problem
reports about KT133 corrupting DMA transfers with sound cards, video
editing cards and IDE. It seemed to me it just can't get DMA right when it
is under heavy load. The reports were mostly windows, btw.
-- v --
v@iki.fi
next prev parent reply other threads:[~2005-09-28 8:43 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 11:10 Strange disk corruption with Linux >= 2.6.13 Rogério Brito
2005-09-27 11:34 ` Diego Calleja
2005-09-27 11:58 ` Rogério Brito
2005-09-27 12:10 ` Rogério Brito
2005-09-27 11:57 ` Grant Coady
2005-09-27 12:43 ` Ondrej Zary
2005-10-01 21:22 ` Rogério Brito
2005-09-27 14:04 ` Lennart Sorensen
2005-10-01 21:28 ` Rogério Brito
2005-10-03 16:20 ` Lennart Sorensen
[not found] ` <Pine.LNX.4.63.0509271331590.21130@alpha.polcom.net>
2005-09-27 12:20 ` Rogério Brito
2005-09-27 12:38 ` Grzegorz Kulewski
2005-09-27 19:42 ` Guennadi Liakhovetski
2005-09-27 21:01 ` Erik Mouw
2005-09-27 21:44 ` Guennadi Liakhovetski
2005-10-01 21:15 ` Rogério Brito
2005-10-08 22:35 ` Guennadi Liakhovetski
2005-10-09 9:30 ` Rogério Brito
2005-10-01 21:02 ` Rogério Brito
2005-09-27 23:31 ` Nigel Cunningham
2005-10-01 21:36 ` Rogério Brito
2005-10-02 0:06 ` Grant Coady
2005-10-03 4:17 ` Rogério Brito
2005-10-03 4:20 ` Willy Tarreau
2005-10-03 4:55 ` Nigel Cunningham
2005-10-04 10:28 ` Sander
2005-10-04 12:42 ` Nigel Cunningham
2005-09-28 8:43 ` Ville Herva [this message]
2005-09-28 23:23 ` Alan Cox
2005-09-29 6:29 ` Ville Herva
2005-09-29 16:14 ` Alan Cox
2005-10-03 5:05 ` Rogério Brito
2005-10-03 5:15 ` Rogério Brito
[not found] <4RlFC-2ev-17@gated-at.bofh.it>
[not found] ` <4Rxdq-2Tc-19@gated-at.bofh.it>
[not found] ` <4SXfs-7hM-27@gated-at.bofh.it>
2005-10-02 3:37 ` Bodo Eggert
2005-10-03 4:30 ` Rogério Brito
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=20050928084330.GC24760@viasys.com \
--to=vherva@vianova.fi \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).