mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stuart Young <sgy@amc.com.au>
To: linux-kernel@vger.kernel.org
Cc: "David S. Miller" <davem@redhat.com>,
	akpm@zip.com.au, andrea@suse.de, reid.hekman@ndsu.nodak.edu,
	alan@lxorg.ukuu.org
Subject: Re: Athlon PSE/AGP Bug
Date: Tue, 22 Jan 2002 11:26:33 +1100	[thread overview]
Message-ID: <5.1.0.14.0.20020122110233.00a1e2e0@mail.amc.localnet> (raw)
In-Reply-To: <20020121.142320.123999571.davem@redhat.com>
In-Reply-To: <3C4C5B26.3A8512EF@zip.com.au> <20020121.053724.124970557.davem@redhat.com> <20020121175410.G8292@athlon.random> <3C4C5B26.3A8512EF@zip.com.au>

At 02:23 PM 21/01/02 -0800, David S. Miller wrote:
>    I does seem that the nVidia driver is usually involved.
>
>I think this is all "just so happens" personally, and all the that
>turning off the large pages really does is change the timings so that
>whatever bug is really present simply becomes a heisenbug.

I'd definitely agree with that. My home system seems rock stable in regards 
to games. Every game problem I've had I've somehow tracked down to a memory 
leak in the game (or another app running in the background) that 
(assumedly) blew out the VM after a while. (Athlon 1400, Asus A7M, Creative 
SBLive!, Asus V8200 GF3DDR, decent power supply and cooling).

I would not be surprised if some of these "crashes" were power related. 
It's quite possible that by slowing things down (even marginally) it will 
reduce the current drain on the system. Some systems power supplies (and 
associated m/board power circuitry) can be so touchy they become unstable, 
and will eventually provide unclean power (usually an AC ripple on the DC). 
 From there, chaos.

Then you've got heat, which is the "next big killer" with the Athlon's. 
They produce a lot of it, and if it doesn't circulate properly, you can 
never expect anything reliable. Of course, the video card generally is 
quite close to the CPU, and it generates heat too, and can suffer from all 
sorts of issues if they get too hot.

Almost all the Athlon problems I've looked at for friends (with lockups 
specifically) have pretty much fallen into either; the above failure 
categories, "broken hardware" or "kernel issues" (usually known issues, not 
specific to Athlon).

I doubt it's as bad as everyone makes out. Unfortunately people buy cheap 
hardware because it's cheap, not because it's reliable.


Stuart Young - sgy@amc.com.au
(aka Cefiar) - cefiar1@optushome.com.au

[All opinions expressed in the above message are my]
[own and not necessarily the views of my employer..]


  parent reply	other threads:[~2002-01-22  0:26 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-21 10:53 Reid Hekman
2002-01-21 13:37 ` David S. Miller
2002-01-21 13:50   ` Arjan van de Ven
2002-01-21 16:58     ` jepler
2002-01-21 17:26     ` Ed Sweetman
2002-01-21 16:54   ` Andrea Arcangeli
2002-01-21 18:17     ` Andrew Morton
2002-01-22  0:36       ` Steve Brueggeman
2002-01-22  1:02         ` Steve Brueggeman
2002-01-22 20:13           ` Florian Weimer
2002-01-22 22:32             ` Steve Brueggeman
2002-01-23  0:36             ` Stuart Young
2002-01-22 22:14           ` Ed Sweetman
2002-01-22 22:52             ` Steve Brueggeman
2002-01-22 23:49               ` Rik van Riel
2002-01-23  1:20               ` Rene Rebe
2002-01-23  2:01                 ` Gustavo Zacarias
2002-01-23  2:11                   ` Tom Hornyak
2002-01-22  5:45       ` Shaya Potter
2002-01-22 12:58         ` Dave Jones
2002-01-22 15:27         ` Shaya Potter
2002-01-22 18:52           ` Greg
2002-01-22 22:08           ` Rene Rebe
2002-01-21 19:11     ` Harold Campbell
2002-01-21 22:23     ` David S. Miller
2002-01-22  0:39       ` Andrea Arcangeli
2002-01-22  1:08       ` David S. Miller
2002-01-22  7:05         ` Ville Herva
2002-01-22  8:05           ` Daniel Robbins
2002-01-22  7:08         ` David S. Miller
2002-01-22  0:26     ` Stuart Young [this message]
2002-01-21 17:57   ` Reid Hekman
2002-01-21 22:14   ` David S. Miller
2002-01-21 22:19   ` David S. Miller
2002-01-22  0:37     ` Andrea Arcangeli
2002-01-22  0:43       ` Russell King
2002-01-22  0:53         ` Andrea Arcangeli
2002-01-22  0:55           ` Russell King
2002-01-22  1:07     ` David S. Miller
2002-01-22  1:27       ` Andrea Arcangeli
2002-01-22 16:57       ` David Woodhouse
2002-01-21 19:37 ` Alan Cox
2002-01-21 19:34   ` David Weinehall
2002-01-21 19:53   ` Sipos Ferenc
2002-01-22  6:32   ` Paul G. Allen
2002-01-22 14:12 Halpaap, Mark (CETA)
2002-01-22 14:51 ` Ed Sweetman
2002-01-22 14:51 ` João Seabra
2002-01-22 23:21 ` Ian Molton
2002-01-23 18:49 ` Marek Mentel
2002-01-22 17:59 Ben Carrell

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=5.1.0.14.0.20020122110233.00a1e2e0@mail.amc.localnet \
    --to=sgy@amc.com.au \
    --cc=akpm@zip.com.au \
    --cc=alan@lxorg.ukuu.org \
    --cc=andrea@suse.de \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reid.hekman@ndsu.nodak.edu \
    /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®