public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Radu-Adrian Feurdean <raf@chez.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Athlon doesn't like Athlon optimisation? [PATCH]
Date: Fri, 31 Aug 2001 15:58:05 +0200	[thread overview]
Message-ID: <3B8F97ED.2030803@chez.com> (raw)
In-Reply-To: <200108310334.f7V3YZm442148@saturn.cs.uml.edu> <Pine.LNX.4.30.0108302117150.16904-100000@anime.net> <l4nnm9.rqp.ln@schlich.user.dfncis.de>

wolfram@schlich.org wrote:
> Dan Hollis <goemon@anime.net> wrote:
> 
>>On Thu, 30 Aug 2001, Albert D. Cahalan wrote:
>>
>>>Don't go blaming Linux when power supply upgrades sometimes
>>>make this problem go away. You could also try one of the
>>>recent SiS or ALi chipsets.
>>>I just saw a reference (maybe www.tomshardware.com) to AMD's new
>>>chips having trouble on VIA boards -- I'd guess that the Palimino
>>>core can push the motherboard too hard without fancy Athlon code.
>>>
> 
>>So what happens when someone is able to duplicate the problem on say AMD
>>760MP chipset with registered ECC PC2100 ram and 450W power supply?
>>
> 
>>Not to say it has happened yet (I havent got my dual Tyan Tiger MP yet :-)
>>
> 
> it has happened to me. dual athlon mp 1.2ghz w/ crucial reg. ddr sdram.
> after setting CONFIG_MK7 to CONFIG_MK6 all works fine.

The following worked for me (Duron@800, Epox 8KTA2L)

root@WormHole:/usr/src# diff -u linux-2.4.9/arch/i386/lib/mmx.c{~,}
--- linux-2.4.9/arch/i386/lib/mmx.c~	Tue May 22 19:23:16 2001
+++ linux-2.4.9/arch/i386/lib/mmx.c	Fri Aug 31 15:51:58 2001
@@ -97,7 +97,7 @@
  	return p;
  }

-#ifdef CONFIG_MK7
+#if 0

  /*
   *	The K7 has streaming cache bypass load/store. The Cyrix III, K6 and

-- 
Radu-Adrian Feurdean
mailto: raf@chez.com
------------------------------------------------------------------------------
+#if defined(__alpha__) && defined(CONFIG_PCI)
+       /*
+        * The meaning of life, the universe, and everything. Plus
+        * this makes the year come out right.
+        */
+       year -= 42;
+#endif
     -- From the patch for 1.3.2: (kernel/time.c), submitted by Marcus Meissner


  parent reply	other threads:[~2001-08-31 13:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-31  2:42 Athlon doesn't like Athlon optimisation? 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
     [not found]       ` <l4nnm9.rqp.ln@schlich.user.dfncis.de>
2001-08-31 13:58         ` Radu-Adrian Feurdean [this message]
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=3B8F97ED.2030803@chez.com \
    --to=raf@chez.com \
    --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