public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carsten Leonhardt <leo@arioch.oche.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Athlon/K7-Opimisation problems
Date: 10 Sep 2001 01:49:59 +0200	[thread overview]
Message-ID: <87iter6i1k.fsf@cymoril.oche.de> (raw)
In-Reply-To: <87g09w70o4.fsf@cymoril.oche.de> <01090915115400.00173@c779218-a> <063301c1397e$0efa6d00$1125a8c0@wednesday> <01090915292502.00173@c779218-a>
In-Reply-To: <01090915292502.00173@c779218-a>

Nicholas Knight <tegeran@home.com> writes:

> On Sunday 09 September 2001 03:23 pm, J. Dow wrote:
> > From: "Nicholas Knight" <tegeran@home.com>

> > > 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?

I sold the 1GHz, so I can't tell anymore.  I have a huge heatsink with
a Papst-fan. I have to admit that it was sold to me as being good
enough for 1.33GHz (by the manufacturer himself), but that shouldn't
be the problem, see below.

(If someone wants to know exactly:
http://www.tiger-electronics.de/english/cooler2.htm and look at
PDA38000BC, for a picture look at cooler1.htm SDA38000BC and pretend
you see the Papst-Fan on the top -- the pages seem to be outdated, the
invoice says the fan is good for a 1.33GHz Athlon).

> > What about the power supply. If it is at all marginal the power
> > consumption boost going to 1.4G is likely a killer.
> 
> Well, he didn't mention the amperage outputs, but he said 431W Enermax, 
> from what I hear Enermax PSU's are good.

Here's the data from the PSU's label:

Model: EG465P-VE
DC Output: +3.3V: 38A
           +5V  : 44A
           +12V : 20A
           -5V  : 2A
           -12V : 1A
           +5Vsb: 2.2A
     +3.3V & 5V : 220W max
    total power : 431W

> Do most people that experience this problem also experience after a 
> cold-boot where the system had been off for at least 10-15 minutes?

I just switched the machine off for about 10min, and for good measure,
jumpered the board to 100MHz FSB, so the CPU runs at 1050MHz (thus
being well below the spec for the heatsink). It may have gotten a tad
further in the boot process, but if so, not much. Luckily, it never
reaches the point where filesystems get mounted rw...

Without the optimisation the machine runs smoothly with steady
cpu-load generated by a distributed-net client.
Currently I added a burnK7 and a burnMMX to the load, I'll see if the
machine is still alive in the morning...

leo

  parent reply	other threads:[~2001-09-09 23:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-09 17:07 Athlon/K7-Opimisation problems 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 [this message]
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
     [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=87iter6i1k.fsf@cymoril.oche.de \
    --to=leo@arioch.oche.de \
    --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