From: Doug McNaught <doug@wireboard.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: db@zigo.dhs.org (Dennis Bjorklund), linux-kernel@vger.kernel.org
Subject: Re: Data-corruption bug in VIA chipsets
Date: 13 Apr 2001 10:02:30 -0400 [thread overview]
Message-ID: <m3y9t4ew3t.fsf@belphigor.mcnaught.org> (raw)
In-Reply-To: <E14o3k7-0002tq-00@the-village.bc.nu>
In-Reply-To: Alan Cox's message of "Fri, 13 Apr 2001 14:36:05 +0100 (BST)"
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> > Is this problem likely to affect 2.2.X? I have a VIA-based board on
> > order (Tyan Trinity) and I don't plan to run 2.4 on it anytime soon
> > (it's upgrading a stock RH6.2 box).
> >
> > Am I safe if I stay in PIO mode?
>
> I have received exactly zero reports of 2.2 problems, and as the 2.2
> maintainer I would have expected more (I delete 2.2 + ide-patch
> reports). My suspicion is the problem requires UDMA to occur, or to
> occur with any probability.
This is good to know. I'll stay away from UDMA and the ide-patches
until things seem clearer then.
> The real concern (as with all of these things) is going to be what the
> workaround does to performance - as measured in frames/second for most folks ;)
Well, this is a compile server (and will have a lot of RAM) so running
PIO for a while shouldn't have much impact.
Thanks, Alan.
-Doug
next prev parent reply other threads:[~2001-04-13 14:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-13 8:00 Data-corruption bug in VIA chipsets Dennis Bjorklund
2001-04-13 9:44 ` Ingo Oeser
2001-04-13 13:11 ` Alan Cox
2001-04-13 13:06 ` Alan Cox
2001-04-13 13:29 ` Doug McNaught
2001-04-13 13:36 ` Alan Cox
2001-04-13 14:02 ` Doug McNaught [this message]
2001-04-13 22:58 ` Jamie Lokier
2001-04-14 4:38 ` Dan Podeanu
2001-04-15 17:45 ` Thomas Molina
2001-04-16 6:45 ` Eric W. Biederman
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=m3y9t4ew3t.fsf@belphigor.mcnaught.org \
--to=doug@wireboard.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=db@zigo.dhs.org \
--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