public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Sweetman <ed.sweetman@wmich.edu>
To: Florian Weimer <Weimer@CERT.Uni-Stuttgart.DE>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Athlon PSE/AGP Bug
Date: 22 Jan 2002 17:14:27 -0500	[thread overview]
Message-ID: <1011737673.10474.12.camel@psuedomode> (raw)
In-Reply-To: <87k7uakutl.fsf@CERT.Uni-Stuttgart.DE>
In-Reply-To: <1011610422.13864.24.camel@zeus> <20020121.053724.124970557.davem@redhat.com> <20020121.053724.124970557.davem@redhat.com> <20020121175410.G8292@athlon.random> <3C4C5B26.3A8512EF@zip.com.au> <o7cp4ukpr9ehftpos1hg807a9hfor7s55e@4ax.com> <hbep4uka8q6t1tfv6694sjtvfrulipg3a4@4ax.com>  <87k7uakutl.fsf@CERT.Uni-Stuttgart.DE>

On the same note.  Anyone trying to run their ram faster than it should
go from the bios would eventually see these kind of things happen. I
used to get errors from anything really memory intensive, games and such
from having ram set at cas 2 instead of cas 3 and removing certain
delays when i shouldn't.  People should really make sure their tuned up
systems aren't just overtuned before forking up segfaults to the Athlon
bug that apparently all the kernel guru's have decided doesn't affect
linux just as it doesn't affect the bsd people.   

It seems to me that the bug "could" be in your chip, it doesn't mean
it's in every athlon...  otherwise we'd be seeing some commonalities and
so far i've seen none.  

Since all the people having problems in linux with the athlon bug are
heavy graphics/game users ...I'd suspect overtuning as the problem
before anything else first and make sure they run memtest86,  even if
disabling pentium ops fixes things. 

On Tue, 2002-01-22 at 15:13, Florian Weimer wrote:
> Steve Brueggeman <brewgyman@mediaone.net> writes:
> 
> > Forgot to mention, I got the segfaults compiling kernels while running
> > linux-2.4.17, I was in console, and did not have Frame Buffer, or drm drivers
> > loaded.  I did have the SiS AGP compiled into the kernel though.
> 
> On my new system at home, I got similar segfaults.  Running memtest86
> revealed that one of the RAM modules had a problem--and if I swapped
> them, the BIOS startup code wouldn't even expand the actual BIOS code
> every other system boot.  After removing the offending RAM module (and
> later replacing it) the problems were completely gone and haven't
> returned yet...
> 
> Fortunately, I didn't know of the PSE/AGP bug back then.  This made
> debugging much, much easier. ;-)
> 
> -- 
> Florian Weimer 	                  Weimer@CERT.Uni-Stuttgart.DE
> University of Stuttgart           http://CERT.Uni-Stuttgart.DE/people/fw/
> RUS-CERT                          +49-711-685-5973/fax +49-711-685-5898
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/



  reply	other threads:[~2002-01-22 22:15 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-21 10:53 Athlon PSE/AGP Bug 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 22:14     ` David S. Miller
2002-01-21 16:54   ` Andrea Arcangeli
2002-01-21 17:57     ` Reid Hekman
2002-01-21 18:17     ` Andrew Morton
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  7:08               ` David S. Miller
2002-01-22  8:05                 ` Daniel Robbins
2002-01-22  0:26       ` Stuart Young
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:14             ` Ed Sweetman [this message]
2002-01-22 22:52               ` Steve Brueggeman
2002-01-22 23:49                 ` Rik van Riel
2002-01-23  0:36               ` Stuart Young
2002-01-23  1:20                 ` Rene Rebe
2002-01-23  2:01                   ` Gustavo Zacarias
2002-01-23  2:11                     ` Tom Hornyak
2002-01-22 22:32             ` Steve Brueggeman
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 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
  -- strict thread matches above, loose matches on Subject: below --
2002-01-22 14:12 Halpaap, Mark (CETA)
2002-01-22 14:51 ` Ed Sweetman
2002-01-22 23:21   ` Ian Molton
2002-01-22 14:51 ` João Seabra
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=1011737673.10474.12.camel@psuedomode \
    --to=ed.sweetman@wmich.edu \
    --cc=Weimer@CERT.Uni-Stuttgart.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