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 09:29:59 -0400 [thread overview]
Message-ID: <m38zl5exm0.fsf@belphigor.mcnaught.org> (raw)
In-Reply-To: <E14o3HM-0002pm-00@the-village.bc.nu>
In-Reply-To: Alan Cox's message of "Fri, 13 Apr 2001 14:06:22 +0100 (BST)"
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> > Here might be one of the resons for the trouble with VIA chipsets:
> >
> > http://www.theregister.co.uk/content/3/18267.html
> >
> > Some DMA error corrupting data, sounds like a really nasty bug. The
> > information is minimal on that page.
>
> What annoys me is that we've known about the problem for _ages_. If you look
> the 2.4 kernel has experimental workarounds for this problem. VIA never once
> even returned an email to say 'we are looking into this'. Instead people sat
> there flashing multiple BIOS images and seeing what made the difference.
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?
-Doug
next prev parent reply other threads:[~2001-04-13 13:30 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 [this message]
2001-04-13 13:36 ` Alan Cox
2001-04-13 14:02 ` Doug McNaught
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=m38zl5exm0.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 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.