From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: Athlon/K7-Opimisation problems
Date: Thu, 20 Sep 2001 16:43:19 -0400 [thread overview]
Message-ID: <200109202043.f8KKhJ202923@deathstar.prodigy.com> (raw)
In-Reply-To: <01090915115400.00173@c779218-a>
In article <01090915115400.00173@c779218-a> you write:
| On Sunday 09 September 2001 10:07 am, Carsten Leonhardt wrote:
| > Hi,
| >
| > here's my data regarding the K7 optimisation problem.
| >
| > Until last week I had a 1GHz Athlon with 133MHz FSB. I then bought a
| > 1.4GHz Athlon, again 133MHz FSB.
| >
| > I never had any problems with the 1GHz processor, but as soon as I
| > stuck the 1.4GHz processor in, the kernel oopsed itself to
| > oblivion. (That was with kernel 2.4.5-ac5, approximately)
|
| This is common enough it's becoming absurd.
Never had a slower Athlon than 1.4, but I suppose the system could be
underclocked as well;-) However, I have to think there's other stuff
happen, see below.
| >
| > I also noticed that the computer booted ok with the Debian
| > bootfloppies, which use a kernel compiled for i386. So after several
| > kernel compile/boot cycles, I found out that I had to disable K7
| > optimisation to make the system boot again.
| >
| > The mainboard is a Tyan Trinity KT-A (S2390B) with a VIA KT133A
| > chipset.
| >
| > After reading here that it may be the PSU, I upgraded my 300W PSU to a
| > 431W Enermax, which made no difference.
| >
| > The only difference I can make out between the working and the
| > non-working CPU is the internal clockspeed of the CPU and the
| > stepping (old: 2, new: 4).
|
| Heat anyone? stepping 4 hasn't seemed to be the problem, at least not
| directly
| What's the tempature difference between your 1Ghz and 1.4Ghz? both CPU
| and system? What kind of cooling do you have?
In my case, if I compile a 686 kernel it is nice and stable, while an
Athlon kernel is not. With all due respect I bet the temperature is dead
the same regardless of kernel, so I can't blame temperature.
The problem I have is seen only when I use Athlon code enabled with
menuconfig, so the question is if the code is bad (as in timing
sensitive), or if the compiler might be generating bad code for Athlon.
Just a data point, I believe that the problems (at least those which are
bugging me) are releated to something other than temperature.
--
bill davidsen <davidsen@tmr.com>
"If I were a diplomat, in the best case I'd go hungry. In the worst
case, people would die."
-- Robert Lipe
next prev parent reply other threads:[~2001-09-20 20:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-09 17:07 Carsten Leonhardt
2001-09-09 22:11 ` Nicholas Knight
2001-09-09 22:23 ` J. Dow
2001-09-09 22:29 ` Nicholas Knight
2001-09-09 22:49 ` J. Dow
2001-09-09 23:44 ` Nicholas Knight
2001-09-09 23:49 ` Carsten Leonhardt
2001-09-10 6:35 ` J. Dow
2001-09-10 6:56 ` Jan Niehusmann
2001-09-10 15:16 ` Liakakis Kostas
2001-09-10 2:18 ` David Hollister
2001-09-20 20:43 ` bill davidsen [this message]
[not found] <Pine.LNX.4.10.10109211552370.12592-100000@coffee.psychology.mcmaster.ca>
2001-09-23 11:58 ` Bill Davidsen
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=200109202043.f8KKhJ202923@deathstar.prodigy.com \
--to=davidsen@tmr.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
all inboxes | Powered by JetHome®