From: insecure <insecure@mail.od.ua>
To: Jamie Lokier <jamie@shareable.org>, Wes Janzen <superchkn@sbcglobal.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, reiserfs-list@namesys.com
Subject: Re: FS Corruption with VIA MVP3 + UDMA/DMA
Date: Sat, 9 Aug 2003 19:43:25 +0300 [thread overview]
Message-ID: <200308091943.25231.insecure@mail.od.ua> (raw)
In-Reply-To: <20030809162710.GC29647@mail.jlokier.co.uk>
On Saturday 09 August 2003 19:27, Jamie Lokier wrote:
> Wes Janzen wrote:
> > I seemed to get a skeptical reaction when I originally posted this to
> > the list, however, just google for "mvp3 corrupt dma mode" to confirm.
>
> The VP2/97 also had severe problems with DMA. I could never run
> standard kernels on mind in the 2.0 days, and distro installs would
> always lock up during installation, although Mandrake 8 seemed
> reliable so something improved.
I had a VIA VPX sometime ago. AFAIR it worked fine...
I suspect PCI conf tweaks etc could work around
this trouble. I'm afraid there won't be much interest
in fixing these oldies. For example, I got rid of that
board (exchanged for Socket A one) -> no way to test fixes :(
--
vda
next prev parent reply other threads:[~2003-08-09 16:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-30 14:37 [PATCH 1/4] Optimize NFS open() calls by means of 'intents' Trond Myklebust
2003-06-30 14:37 ` Trond Myklebust
2003-06-30 14:39 ` Trond Myklebust
2003-06-30 14:39 ` Trond Myklebust
2003-06-30 18:17 ` FS Corruption with VIA MVP3 + UDMA/DMA Wes Janzen
2003-07-12 20:42 ` Wes Janzen
2003-07-14 9:06 ` Vladimir B. Savkin
2003-07-14 14:13 ` Wes Janzen
2003-08-09 12:19 ` Wes Janzen
2003-08-09 14:37 ` Alan Cox
2003-08-09 15:57 ` Helge Hafting
2003-08-09 17:11 ` John Wendel
2003-08-09 16:27 ` Jamie Lokier
2003-08-09 16:43 ` insecure [this message]
2003-08-09 17:38 ` Jamie Lokier
2003-08-09 23:18 ` Wes Janzen
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=200308091943.25231.insecure@mail.od.ua \
--to=insecure@mail.od.ua \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.com \
--cc=superchkn@sbcglobal.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.