mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eyal Lebedinsky <eyal@eyal.emu.id.au>
To: linux-kernel@vger.kernel.org
Subject: Re: VIA Southbridge bug (Was: Crash on boot (2.4.5))
Date: Wed, 11 Jul 2001 19:03:55 +1000	[thread overview]
Message-ID: <3B4C167B.528E9547@eyal.emu.id.au> (raw)
In-Reply-To: <E15JIVD-0000Qc-00@the-village.bc.nu> <01070912485904.00705@localhost.localdomain> <20010710121724.Z1503@niksula.cs.hut.fi>

Ville Herva wrote:
> 
> On Mon, Jul 09, 2001 at 12:48:59PM -0400, you [Rob Landley] claimed:
> >
> > (P.S. What kind of CPU load is most likely to send a processor into overheat?
> >  (Other than "a tight loop", thanks.  I mean what kind of instructions?)
> > This is going to be CPU specific, isn't it?  Our would a general instruction
> > mix that doesn't call halt be enough?  It would need to keep the FPU busy
> > too, wouldn't it?  And maybe handle interrupts.  Hmmm...)
> 
> See Robert Redelmeier's cpuburn:
> 
> http://users.ev1.net/~redelm/

I took this program for a spin and I noted the reported CPU temp
went up by 12dc (43->55).

However, more interesting, the +5V line dropped from 4.82 to 4.72.
This is on a Gigabyte GA-7ZX with an Athlon/1200 and 2x128MB.

Some mobos may actually have their voltages pushed outside accepted
levels and cause a failure, which is actually not related to the
temperature. And you do not need to run the test for a long time,
the drop is immediate and stable.

I can only imagine what will happen if some game pushes the CPU to
the limit while running a hot video card hard, as I expect some
highly optimized graphics drivers might do. May cause some
interesting crashes.

Anyone up to enhancing the program to stress the video memory at the
same time?


In other words, this is a good stress test for the whole mobo design
and setup, not just the CPU/HSF combo.

--
Eyal Lebedinsky (eyal@eyal.emu.id.au) <http://samba.anu.edu.au/eyal/>

  parent reply	other threads:[~2001-07-11  9:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-25  6:17 Crash on boot (2.4.5) Andy Ward
2001-06-25  6:32 ` VIA Southbridge bug (Was: Crash on boot (2.4.5)) Steven Walter
2001-06-25  7:06   ` Alan Cox
2001-06-30 13:58     ` Pavel Machek
2001-07-08 17:37       ` Alan Cox
2001-07-09 16:48         ` Rob Landley
2001-07-10  9:17           ` Ville Herva
2001-07-10 15:28             ` Hardware testing [was Re: VIA Southbridge bug (Was: Crash on boot (2.4.5))] Rob Landley
2001-07-11  4:18               ` Albert D. Cahalan
2001-07-11  8:43               ` Ville Herva
2001-07-11  9:11               ` Vojtech Pavlik
2001-07-11 15:05                 ` Rob Landley
2001-07-12  6:57                   ` Ville Herva
2001-07-10 21:24             ` VIA Southbridge bug (Was: Crash on boot (2.4.5)) Adam Sampson
2001-07-11  8:32               ` Ville Herva
2001-07-11  9:03             ` Eyal Lebedinsky [this message]
2001-06-25 19:55 Andy Ward
2001-06-25 19:57 Andy Ward
2001-06-25 20:27 ` David Grant
2001-06-26  9:10   ` pazke
2001-07-10  9:12 David Balazic

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=3B4C167B.528E9547@eyal.emu.id.au \
    --to=eyal@eyal.emu.id.au \
    --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®