From: Joseph Carter <knghtbrd@debian.org>
To: Aaron Tiensivu <mojomofo@mojomofo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: REVISED: Experimentation with Athlon and fast_page_copy
Date: Fri, 4 May 2001 17:26:57 -0700 [thread overview]
Message-ID: <20010504172657.B14969@debian.org> (raw)
In-Reply-To: <E14vmpN-000822-00@the-village.bc.nu> <006e01c0d4e9$3c0bd210$0300a8c0@methusela>
In-Reply-To: <006e01c0d4e9$3c0bd210$0300a8c0@methusela>; from mojomofo@mojomofo.com on Fri, May 04, 2001 at 06:26:14PM -0400
[-- Attachment #1: Type: text/plain, Size: 903 bytes --]
On Fri, May 04, 2001 at 06:26:14PM -0400, Aaron Tiensivu wrote:
> This might be grasping at straws I remember VIA problem in the "good old
> days" of Socket 7 with CPU/PCI Prefetches and especially Read-around-Write
> settings that would cause issues like we're seeing with the Athlon
> pre-fetches. This could be (total conjecture) related somehow to the
> corruption bugs they are admitting to in the 686B although they are blaming
> the SB Live now.
I don't see how they figure, but in case there was any doubt I have a VIA
KT133A/686B board (Abit KT7A) and don't experience anything resembling
disk corruption unless the box crashes for some other reason. I do seem
to be experiencing AGP problems in spades, but my disks at least are fine.
--
Joseph Carter <knghtbrd@debian.org> Free software developer
<_Anarchy_> Argh.. who's handing out the paper bags 8)
[-- Attachment #2: Type: application/pgp-signature, Size: 273 bytes --]
next prev parent reply other threads:[~2001-05-05 0:26 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-04 17:22 REVISED: Experimentation with Athlon and fast_page_copy Seth Goldberg
2001-05-04 19:48 ` Brian Gerst
2001-05-04 21:09 ` Alan Cox
2001-05-04 22:26 ` Aaron Tiensivu
2001-05-04 18:10 ` Bobby D. Bryant
2001-05-05 6:43 ` John R Lenton
2001-05-05 7:20 ` Alan Cox
2001-05-07 1:26 ` John R Lenton
2001-05-07 1:30 ` Jeremy
2001-05-05 0:26 ` Joseph Carter [this message]
2001-05-05 3:51 ` Chris Wedgwood
2001-05-05 4:08 ` Seth Goldberg
[not found] ` <20010505163204.A29622@metastasis.f00f.org>
2001-05-05 5:03 ` Athlon and fast_page_copy: What's it worth ? :) Seth Goldberg
2001-05-05 6:20 ` Mark Hahn
2001-05-05 9:15 ` Tom Leete
2001-05-05 7:17 ` Alan Cox
2001-05-05 14:19 ` Jonathan Morton
2001-05-05 14:41 ` Alan Cox
2001-05-05 15:17 ` Jonathan Morton
2001-05-08 21:16 ` Arjan van de Ven
2001-05-05 5:45 ` REVISED: Experimentation with Athlon and fast_page_copy Joseph Carter
2001-05-09 2:11 ` Tom Leete
2001-05-09 8:49 ` Alan Cox
2001-05-09 11:38 ` Tom Leete
2001-05-09 12:38 ` Alan Cox
2001-05-09 13:02 ` Tom Leete
-- strict thread matches above, loose matches on Subject: below --
2001-05-04 19:14 Manfred Spraul
2001-05-04 19:30 ` Seth Goldberg
2001-05-04 21:43 ` Alan Cox
2001-05-08 21:15 ` Arjan van de Ven
2001-05-05 2:28 Dieter Nützel
2001-05-05 7:13 ` Alan Cox
2001-05-09 23:56 ` Dieter Nützel
2001-05-05 17:34 Jeremy
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=20010504172657.B14969@debian.org \
--to=knghtbrd@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mojomofo@mojomofo.com \
/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.