lkml.org 
[lkml]   [2002]   [Jan]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Athlon PSE/AGP Bug
Date
OK, now my dander's beginning to get up.

I have been in the computer industry for 20+ years.

I don't particularily like graphic interfaces.

My original post said that I was running the kernel compile in console
mode, but I guess I didn't expressly state that there was "NO X
running".

I did state that there were no Frame Buffer modules, nor DRM modules
loaded, but I did have the AGPGART driver for the SiS AGP hardware
compiled into the kernel.

I am not overclocking my system in "ANY WAY SHAP OR FORM". I do not
believe one bit in overclocking, as I appreciate stability much more
than the 2% to 5% overclocking gets you.

I have PC2100 DDR SDRAM, which should be able to run with a 133 Mhz
bus.

I have an Athelon 1800+ (1500 or so real clock) which should run with
1 133Mhz bus.

While I cannot rule out a poor power supply, experience has shown me
that a minor tweek, such as running the kernel with mem=nopentium, is
not enough of a load change to expose a bad power supply.

Again, I reiterate, I consistently got 3-4 Segmentation faults when
compiling a kernel without the mem=nopentium, with 5 attempts done.

I was unable to get any segfaults when compiling kernels WITH the
mem=nopentium option, with 10 attempts done.

I AM NOT stating that this is necessarily the Athelon bug exposed by
gentoo, but it appears that there are enough people complaining about
unstable systems, becoming stable by running with the mem=nopentium.
It also appears that a significant number of them are also running
Nvidia AGP graphics adapters.

For all I know, this may be due to Nvidia imposing some border-spec
timming on the AGP bus when doing dma, or maybe it could be Athelon
related, or maybe it could in fact be a kernel bug that's been blown
off by kernel developers, just because they're using Nvidia, and don't
bother to ask whether or not they were running X or not.

And of course, since this is a new, and untested system, purchased
from a computer fair, it could indeed be bad hardware, it's just that
my current indications say it's not.

I would like to see some indication that someone is collecting data
related to "running stable with mem=nopentium on Athelon
architecture", and maybe we can see a pattern here. Heck maybe we see
2 or 3 different patterns here.

OK, I'm done.

Steve Brueggeman



On 22 Jan 2002 17:14:27 -0500, you wrote:

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


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

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

\
 
 \ /
  Last update: 2005-03-22 13:18    [W:0.094 / U:0.264 seconds]
©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site