From: Wes Janzen <superchkn@sbcglobal.net>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: reiserfs-list@namesys.com
Subject: Re: FS Corruption with VIA MVP3 + UDMA/DMA
Date: Sat, 09 Aug 2003 07:19:29 -0500 [thread overview]
Message-ID: <3F34E6D1.7030900@sbcglobal.net> (raw)
In-Reply-To: <3F10729F.7070701@sbcglobal.net>
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.
I don't know that it takes to hit this error, but it's very easy to
reproduce on my machine. Some links only mention UDMA, but all DMA
modes are affected on my board. I couldn't even burn a CD over 12X
without running into this issue. There I thought it was bad media, but
after burning 11 CD's at 32X with the PDC20269 (rather than the native
IDE) and not encountering any errors using the same batch of media and
writer, the culprit is clear.
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.
next prev parent reply other threads:[~2003-08-09 12:19 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 [this message]
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
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=3F34E6D1.7030900@sbcglobal.net \
--to=superchkn@sbcglobal.net \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.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;
as well as URLs for NNTP newsgroup(s).