public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Knight <tegeran@home.com>
To: "J. Dow" <jdow@earthlink.net>,
	"Carsten Leonhardt" <leo@debian.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: Athlon/K7-Opimisation problems
Date: Sun, 9 Sep 2001 16:44:12 -0700	[thread overview]
Message-ID: <01090916441200.00423@c779218-a> (raw)
In-Reply-To: <87g09w70o4.fsf@cymoril.oche.de> <01090915292502.00173@c779218-a> <066701c13981$b9e91830$1125a8c0@wednesday>
In-Reply-To: <066701c13981$b9e91830$1125a8c0@wednesday>

On Sunday 09 September 2001 03:49 pm, J. Dow wrote:
> From: "Nicholas Knight" <tegeran@home.com>
>
> > > 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.
> > I still have trouble dealing with the idea that the optimizations
> > cause power consumption like this, but then, I have trouble with my
> > own idea that it causes sufficient heat increase in the chipset that
> > soon after boot.
> >
> > 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?
> > And has ANYONE sucsesfully cured this problem by changing power
> > supplies?
>
> Don't forget that there are two regulators involved. First there is the
> primary power supply's regulator down to either 3.3 or 5 volts. Then
> there is the motherboard regulator down to the 1.7 volt range. If THAT
> one is not up to handling the required oompf during certain CPU loads
> that is a sure way to glitch the machine.

Now THAT I'll buy... It would certainly explain why some KT133A 
motherboards work and some don't, but the relation would be a little 
complex, the chipset might be exposing general problems with regulators 
used in motherboards.
Verifying this would require both extensive analysis of the motherboards 
and chipsets, and the regulators.
You'd also need to verify the manufacturing place, batch and time/date 
for at least 50 to 100 motherboards to begin verifying this.

  reply	other threads:[~2001-09-09 23:44 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 [this message]
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
     [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=01090916441200.00423@c779218-a \
    --to=tegeran@home.com \
    --cc=jdow@earthlink.net \
    --cc=leo@debian.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