mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Wes Janzen <superchkn@sbcglobal.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	reiserfs-list@namesys.com
Subject: Re: FS Corruption with VIA MVP3 + UDMA/DMA
Date: 09 Aug 2003 15:37:07 +0100	[thread overview]
Message-ID: <1060439826.4938.88.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <3F34E6D1.7030900@sbcglobal.net>

On Sad, 2003-08-09 at 13:19, Wes Janzen wrote:
> I don't know why I didn't google for this in the first place, but it 
> looks like it is a known issue.  Just apparently not well-known.
> 
> Probably not especially important though, I wonder just how many people 
> are still running this setup...  With Linux, I'd say even fewer.

I'm running MVP4 without problems. I've got an old MVP3 board I need to
dig out and play with. Certainly MVP3 has problems with some AGP and
some other high load PCI situations. 

  reply	other threads:[~2003-08-09 14:41 UTC|newest]

Thread overview: 13+ 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: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-08-09 12:19     ` Wes Janzen
2003-08-09 14:37       ` Alan Cox [this message]
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
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=1060439826.4938.88.camel@dhcp22.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®