From: Nicholas Knight <tegeran@home.com>
To: VDA <VDA@port.imtp.ilyichevsk.odessa.ua>, brian@worldcontrol.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Re[2]: Athlon: Try this (was: Re: Athlon bug stomping #2)
Date: Wed, 19 Sep 2001 20:17:38 -0700 [thread overview]
Message-ID: <01091920173800.01212@c779218-a> (raw)
In-Reply-To: <Pine.GSO.4.21.0109140430540.2204-100000@jacui> <1663026712.20010919161037@port.imtp.ilyichevsk.odessa.ua> <01091916564902.00579@c779218-a>
In-Reply-To: <01091916564902.00579@c779218-a>
Here's a new one:
http://zerowing.idsoftware.com/linux/q3a/
I have an AMD CPU and a kernel 2.4.*, Quake III Arena is slowing down to
a complete stop after a while?
It seems the 3DNow! copy routines have issues with the southbridge chip
in the KT133A, this results in performances degrading while playing for a
while. Re-compile your kernel without 3DNow! instructions to avoid the
problem, and wait for newer kernels with better support for 3DNow! /
KT133A.
Anyone know further details on this and if it's in any way connected with
the current K7 optimization problems in the kernel?
next prev parent reply other threads:[~2001-09-20 3:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-13 12:31 Athlon bug stomping #2 VDA
2001-09-14 2:56 ` Roberto Jung Drebes
2001-09-14 4:02 ` Chris Vandomelen
2001-09-14 5:51 ` Eric W. Biederman
2001-09-14 7:34 ` Roberto Jung Drebes
2001-09-14 8:27 ` Athlon: Try this (was: Re: Athlon bug stomping #2) Roberto Jung Drebes
2001-09-14 9:26 ` Jeff Lightfoot
2001-09-14 18:19 ` Byron Stanoszek
2001-09-15 18:00 ` Liakakis Kostas
2001-09-15 20:28 ` VDA
2001-09-15 7:15 ` brian
2001-09-19 1:30 ` brian
2001-09-19 13:10 ` Re[2]: " VDA
2001-09-19 23:56 ` Nicholas Knight
2001-09-20 3:17 ` Nicholas Knight [this message]
2001-09-20 12:34 ` Alan Cox
2001-09-16 21:53 ` Carsten Leonhardt
2001-09-19 3:55 ` Dan Hollis
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=01091920173800.01212@c779218-a \
--to=tegeran@home.com \
--cc=VDA@port.imtp.ilyichevsk.odessa.ua \
--cc=brian@worldcontrol.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