From: David Balazic <david.balazic@uni-mb.si>
To: aia21@cus.cam.ac.uk,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Athlon problems fixed tweaking BIOS memory settings
Date: Fri, 14 Sep 2001 15:12:14 +0200 [thread overview]
Message-ID: <3BA2022E.F33FA9B6@uni-mb.si> (raw)
Anton Altaparmakov (aia21@cus.cam.ac.uk) wrote :
> Hi all,
>
> I had a few random crashes on my Athlon EPOX 8KTA3 mobo Athlon 1.33GHz
> (BIOS from 06/14/2001) and Alan Cox suggested to run memtest as the oops
> apparently looked like memory corruption. Sure enough memtest showed
> problems above 256MiB but swapping the chips around still showed problems
> above 256MiB which meant it couldn't be the chips at fault (failing tests
> were 5 and 8 in memtest86 supplied with SuSE 7.2).
To eliminate any doubt about the chips, I suggest testing each of them separately.
>
> Playing with the memory settings I found that using the "DRAM
> Timing by SPD" option was unstable but setting it to manual and using the
> settings: 133MHz, CL2, Bank interleave disabled as well as Pre charge to
> active 3T, active to precharge 6T, active to cmd 3T. Makes it fully
> stable even with Page-Mode enabled.
>
> Changing the precharge/act/cmd value to faster caused increasing amounts
> of errors in memtest to appear and enabling Timing by SPD did the same.
> Memory now running at 23.1 MiB/sec according to memtest86 compared to 26
> MiB/sec at previous, faster but unstable settings.
>
> It seems there is some kind of problem with the "Timing by SPD" option.
SPD EEPROMs on many ( especially no-name ) RAM modules are programmed incorrectly
( according to C'T magazine - http://www.heise.de/ct/ ) so "Timing by SPD" does
not work at all, or sets a wrong timing.
> Also no matter what the settings are the system is always error free below
> 256MiB, which means that might explain why some people are having problems
> and some are not... Until I upgraded the 256 to 768MiB I didn't have any
> problems.
>
> Just a datapoint...
>
> Best regards,
>
> Anton
--
David Balazic
--------------
"Be excellent to each other." - Bill S. Preston, Esq., & "Ted" Theodore Logan
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
next reply other threads:[~2001-09-14 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-14 13:12 David Balazic [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-14 0:38 Athlon problems fixed tweaking BIOS memory settings Anton Altaparmakov
2001-09-14 5:58 ` Janne Pänkälä
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=3BA2022E.F33FA9B6@uni-mb.si \
--to=david.balazic@uni-mb.si \
--cc=aia21@cus.cam.ac.uk \
--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