From: ebiederm@xmission.com (Eric W. Biederman)
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: 16 Apr 2001 00:45:12 -0600 [thread overview]
Message-ID: <m1ae5htkav.fsf@frodo.biederman.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.
>
> > I just bought one of these babies and I should probably return it
> > directly. I have seven days to return it and get my money back. I have not
> > even opened the box yet.
>
> Disabling pci master read caching is likely to reduce the performance of the
> board.
>
> > They seems to think they can correct it by some bios updates, but who
> > knows what that fix might be. Maybe they turn of DMA alltogether
> > (hopefully not).
>
> The -ac kernel does this on the KT7 series boards which seemed the worst
> affected.
>
> Hopefully now someone in VIA will have the decency to tell the community
> how to detect setups that need a BIOS upgrade so we can warn them before the
> chipset bug turns there file systems into sludge.
I wonder if someone at VIA even knows what is going on. In working
with linuxBIOS Ron Minnich was worked with VIA to get it up on some of
their chipsets. He ran into a few cases where his code wouldn't work,
he'd show it to the engineers at VIA and they also wouldn't have a
clue why his code was failing. And that it looked like only Award
knew how the chipset really worked. This is northbridge code not
southbridge code so it may be an entirely different ball game but...
Anyway Alan you might want to bounce off Ron. He might have a clue
how to help you get get VIA's attention...
Eric
prev parent reply other threads:[~2001-04-16 6:47 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
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 [this message]
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=m1ae5htkav.fsf@frodo.biederman.org \
--to=ebiederm@xmission.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