Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Oct 2001 01:11:44 +0100
From:      "Siegbert Baude" <Siegbert.Baude@gmx.de>
To:        "Nils Holland" <nils@tisys.org>, =?iso-8859-1?Q?S=F8ren_Schmidt?= <sos@freebsd.dk>
Cc:        "Randall Hopper" <aa8vb@nc.rr.com>, <multimedia@freebsd.org>, <stable@freebsd.org>
Subject:   Re: "VIA '686b southbridge fix applied" & -stable
Message-ID:  <012c01c160d7$76229ea0$4011a8c0@wohnheim.uniulm.de>
References:  <20011029140547.D398-100000@howie.ncptiddische.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Hello,

> On Mon, 29 Oct 2001, Søren Schmidt wrote:
>
> > Depends, it seems this bug is a combination of mb vendors not
> > knowing how to set the config regs of the VIA chips, and the
> > SBLive not conforming to the specs. I've had reports that it
> > works, but also afew that it doesn't...
>
> I guess the SBLive is not absolutely neccessary to make this bug occur. I
> haven't gotten into this issue too deep, but from what I have read, it
> seems that this bug might very well also occur if there is no SBLive in
> the system. One article claimed that the SBLive puts the PCI bus under
> heavier-than-normal stress, which in turn triggers the bug more often.
>
> Furthermore, I guess that all "patches", like VIAs 4-in-1 driver for
> Windows (never used that since I don't have Windows) and the FreeBSD patch
> are only workarounds. The core of the problem has to be found (and fixed)
> in the BIOS, AFAIK. From my own experience, a mobo I own was initially
> subject to the bug, but once I updated the BIOS provided by the
> manufacturer, I could do whatever I wanted to without ever having any
> problems again...

As a friend of mine had a system, which reproducably showed the data corruption behaviour, I can state for sure, what
Soeren told:
- It occurs with different cards than SB Live. In this special case it was a SB 128.
- The newest BIOS (don't know the exact model of the motherboard, believe to remember it was some MSI with KT133) didn't
solve the problem. Only the VIA 4/1 drivers for Win2k or the respective Linux kernel patches solved the problem (no FBSD
on this system).

Side note: Linux' Reiser FS on this system was damaged beyond any recovery by this data corruption bug. No data
available at all. Would ufs/ffs behave better in similar circumstances (i.e. hardware failure)?

Ciao
Siegbert


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-multimedia" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?012c01c160d7$76229ea0$4011a8c0>