mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Dennis Bjorklund <db@zigo.dhs.org>
Cc: linux-kernel@vger.kernel.org, Andre Hedrick <andre@linux-ide.org>,
	Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: Data-corruption bug in VIA chipsets
Date: Fri, 13 Apr 2001 11:44:56 +0200	[thread overview]
Message-ID: <20010413114456.C682@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <Pine.LNX.4.30.0104130953160.20273-100000@merlin.zigo.dhs.org>
In-Reply-To: <Pine.LNX.4.30.0104130953160.20273-100000@merlin.zigo.dhs.org>; from db@zigo.dhs.org on Fri, Apr 13, 2001 at 10:00:32AM +0200

On Fri, Apr 13, 2001 at 10:00:32AM +0200, Dennis Bjorklund wrote:
> 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.

These are the things, that one of the German links[1] suggest
(translated only, because I'm not the IDE guy ;-)):
   
   - PCI Delay Transaction = 0 (off) (Register 0x70, Bit 1)
   - PCI Master Read Caching = 0 (off) (Register 0x70, Bit 2)
   - PCI Latency = 0 (values between 0 and 32 *seem* to be safe,
        everything above seems to be *not* !)

Note: This also fixes some related USB issues according to [1].

Some hassles of setting the "PCI Latency" are described and one
of their reader found out, that it is "PCI Bus Master Time-Out"
on his board.

Register 0x75, Bits 0-3 are at 0001, which means 32 as latency
value. He set it to 0000 and it helps. This setting also does no
harm according to the magazine.

The observations are valid for the VT82C686B. One of their
readers also observed it at VT82C686A too and reported, that the
workaround helps.

So we might want to enable these workarounds for this
southbridge, too.

Hope this translation helps our maintainers a little ;-)

Regards

Ingo Oeser

[1] http://home.tiscalinet.de/au-ja/review-kt133a-4.html
-- 
10.+11.03.2001 - 3. Chemnitzer LinuxTag <http://www.tu-chemnitz.de/linux/tag>
         <<<<<<<<<<<<     been there and had much fun   >>>>>>>>>>>>

  reply	other threads:[~2001-04-13  9:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-13  8:00 Dennis Bjorklund
2001-04-13  9:44 ` Ingo Oeser [this message]
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

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=20010413114456.C682@nightmaster.csn.tu-chemnitz.de \
    --to=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=andre@linux-ide.org \
    --cc=db@zigo.dhs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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®