From: Robert Redelmeier <redelm@ev1.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4 freezes on VIA KT133 -- mine FIXED
Date: Tue, 29 May 2001 19:35:51 -0500 [thread overview]
Message-ID: <3B144067.60EA@ev1.net> (raw)
Mark Hahn wrote:
> > > contrary to the implication here, I don't believe there is any *general*
> > > problem with Linux/VIA/AMD stability. there are well-known issues
> ...
> > VIA hardware is not suitable for anything until we _know_ the
> > truth about what is wrong. VIA is hiding something big.
<snip>
> afaik, there are absolutely zero problems reported with kt133-no-a
> machines, for instance. mine has certainly worked flawlessly for a
> long time, on most every 2.3/2.4 kernel over the past year+.
FWIW, I'm shaking down a 8.5*100 T'bird VIA VT8363 (no "A")
Northbridge & VT82C686A (Southbridge). KT133 no A. No HPT366.
I had terrible read errors on a single UDMA66 HD: one in 5 md5sums
on an unmounted 1.5 GB partition was different. WD Diags said
drives were good (sectors verified OK). Swapped PS, RAM, HDs,
cables, PCI cards, 2.2/2.4/FreeBSD kernels, nothing helped ...
... until I slowed the SDRAM down from the PC133 (it really _is_
and passes memtest-86 and my burnMMX) down to PC100. At least
UDMA is still working, even if my RAM is decidedly slower. YMMV
I've now tested 9 hrs copying a 500 MB file back and forth on the
same drive without error. 21 hrs copying back and forth and
md5sum'ing from /dev/hdc3 [UDMA66] is OK too.
-- Robert author `cpuburn` http://users.ev1.net/~redelm
reply other threads:[~2001-05-30 0:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3B144067.60EA@ev1.net \
--to=redelm@ev1.net \
--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