public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Matthew S . Hallacy" <poptix@techmonkeys.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Athlon doesn't like Athlon optimisation?
Date: Tue, 4 Sep 2001 03:35:17 -0600	[thread overview]
Message-ID: <20010904033517.G20505@techmonkeys.org> (raw)
In-Reply-To: <E15dorf-0003vE-00@pranika.wulf>
In-Reply-To: <E15dorf-0003vE-00@pranika.wulf>; from ejolson%pranika@fractal.math.unr.edu on Mon, Sep 03, 2001 at 01:13:51AM -0700

On Mon, Sep 03, 2001 at 01:13:51AM -0700, Eric Olson wrote:
> I have found these Athlon problems are very interesting.
> 
> Is there a usermode memory testing program which uses the K7 MMX 3DNow
> streaming cache bypass load/store instruction sequences that appear in
> linux/arch/i386/lib/mmx.c ?
> 
> Could Robert Redelmeier's burnMMX at 
> 	http://users.ev1.net/~redelm/
> be modified for the Athlon to detect these problems?
> 

Howdy, I've got a 1.3Ghz (non overclocked) running on the SiS 735 chipset
(yes, the first good chipset from SiS) with no problems under 2.4.9 with
athlon optimizations, the system has DDR ram, and is used a lot for video
capture/compression, the avifile library detects (and supposedly uses) the
optimizations, and I've had no problems whatsoever with the system. Perhaps
this is another VIA problem.

> It would be usefull to have a Microsoft Windows program that could 
> detect a faulty system without having to load Linux.  This would allow 
> testing a system in a store before purchase, and quick testing of a 
> new system shipped with Windows to determine whether it needs to be 
> returned before reformatting the harddisk and installing Linux.
> 
> The reports I've know are for KT133 motherboards.  Have problems been 
> reported with the KT266 DDR-SDRAM chipsets as well?

As I write this a friend is repairing a lost partition on his FIC AZ11E 
motherboard (KT133 chipset), apparently due to a BIOS bug..

> 
> All the best, Eric Olson

  parent reply	other threads:[~2001-09-04  9:35 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-03  8:13 Athlon doesn't like Athlon optimisation? Eric Olson
2001-09-03 15:55 ` Ghozlane Toumi
2001-09-04 10:19   ` Dan Hollis
2001-09-04  9:35 ` Matthew S . Hallacy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-09-23 10:04 Jim Blomo
2001-09-07  7:33 Jim Blomo
2001-09-07  8:00 ` Dan Hollis
2001-09-07  8:39 ` Andrzej Krzysztofowicz
2001-09-07 17:25   ` Mike Fedyk
2001-09-05 18:37 Eric Olson
2001-09-05 14:22 noneuclidean
2001-09-05 17:37 ` Simen Thoresen
2001-09-05 18:07 ` Dan Hollis
2001-09-05  5:21 Eric Olson
2001-09-05  9:59 ` Matthew S . Hallacy
2001-09-05 15:56 ` David Hollister
     [not found] <fa.kt7mv6v.qiq718@ifi.uio.no>
     [not found] ` <fa.j3okgqv.lmova7@ifi.uio.no>
2001-08-31 12:11   ` Dan Maas
2001-08-31  2:42 Jan Niehusmann
2001-08-31  3:07 ` David Hollister
2001-08-31  3:34   ` Albert D. Cahalan
2001-08-31  3:50     ` Richard Gooch
2001-08-31  4:20     ` Dan Hollis
2001-08-31  5:05       ` Chris Abbey
2001-08-31  8:27         ` Arjan van de Ven
2001-08-31  9:36           ` Nicholas Knight
2001-08-31 14:17           ` David Hollister
2001-08-31  6:02       ` Paul G. Allen
2001-08-31  6:15         ` Steven Spence
2001-08-31 14:06         ` Alan Cox
2001-08-31  9:21       ` Phillip Susi
2001-08-31 14:00       ` Alan Cox
2001-08-31 20:37         ` Dan Hollis
2001-08-31 20:53           ` Alan Cox
2001-09-08 18:01             ` Eric W. Biederman
2001-08-31 20:53           ` Mike Fedyk
2001-08-31  8:08   ` Joerg Plate
2001-08-31 18:18   ` Tim Moore
2001-08-31 19:17     ` Bobby D. Bryant
2001-08-31 19:43       ` Tim Moore
2001-09-01 10:06   ` Jim Roland
2001-09-01 12:04     ` Joerg Plate
2001-09-01 14:39     ` David Hollister
2001-09-01 15:50       ` Alan Cox
2001-09-01 16:27         ` David Hollister
2001-09-03  8:03       ` Jim Roland

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=20010904033517.G20505@techmonkeys.org \
    --to=poptix@techmonkeys.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