From: "Dr. David Alan Gilbert" <gilbertd@treblig.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Dual athlon XP 1800 problems
Date: Tue, 1 Jan 2002 15:21:56 +0000 [thread overview]
Message-ID: <20020101152156.GB12799@gallifrey> (raw)
On Mon, Dec 31, 2001 at 06:12:16PM -0800, ccroswhite@get2chip.com wrote:
> I am having problems with dual athlons and more than 512M RAM. I have
> compiled several kernels with either ATHLON, 1386, i686 support with the
> same affect, I get a kernel that will fail to boot properly. Sometimes
> I get a kernel panic that outs to kdb, sometimes I get a freeze, and
> sometimes I get failed to mount root partition, but never has this
> kernel successfully come up. I am quite certain it is not the memory or
> the system ( I can get windblows 2k to run successfully with upto 3.5G
> RAM).
>
> Here is the configuration:
>
> Tyan S2460
> Dual Athlon XP 1800
> 512M DDR DIMMS (also used 128, 256, and 1G)
> Western Digital 20G Drive
I have a similar system running fine. It has a Tyan S2460, a pair of
Athlon MP 1800s, 512M (2x256) and a pair of IBM 60G drives.
I haven't seen any signs of kernel instability. However:
1) When I first got it I had the BIOS do some very odd things; at one
point the CMOS got cleared and then everything worked from there on
in. So a good CMOS clean could be in order. I had to use the Debian
safe boot set prior to this.
2) Are you saying the problem only affects greater than 512M ? I only
have the 512M so don't know - but it is probably worth booting with
mem=512M as an option with more RAM in and see if it is stable.
3) The guys who put the machine together had lots of problems getting
it stable; the type of RAM they used was critical; it was stable
enough for them to boot NT and get it through a lot of tests before
they hit problems.
4) COOL IT - these things generate tons of heat (mine run at 75degC
normal operation). I have it in a big Supermicro 760 case with damn
big fans on.
5) I bought Athlon MPs because I didn't want the hastle of knowing
whether XPs would work or not. Now sure, it could be AMD just trying
to squeeze some more money out of us; but it is entirely possible that
a) the chips could be different, b) that the critical timing path in
the device could be in the cache snooping/consistency stuff (that
stuff is probably pretty hairy!). I mean there must be a reason why
it took them a month and a half longer to release the Athlon MP 1.9GHz
than the XP 1.9GHz.
6) I'm currently on 2.4.17 and have used most of the later 2.4.1x's on
it.
Dave
---------------- Have a happy GNU millennium! ----------------------
/ Dr. David Alan Gilbert | Running GNU/Linux on Alpha,68K| Happy \
\ gro.gilbert @ treblig.org | MIPS,x86,ARM, SPARC and HP-PA | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next reply other threads:[~2002-01-01 15:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-01 15:21 Dr. David Alan Gilbert [this message]
2002-01-03 17:08 ` Dual athlon XP 1800 problems Andreas Bombe
-- strict thread matches above, loose matches on Subject: below --
2002-11-16 15:11 Kevin Brosius
2002-11-16 15:14 ` Kevin Brosius
2002-11-15 10:31 David Crooke
2002-11-15 11:55 ` Alastair MacGregor
2002-11-15 14:54 ` Alan Cox
2002-11-15 14:40 ` Dave Jones
2002-11-15 17:19 ` Willy Tarreau
2002-11-15 18:38 ` erich
2002-11-15 17:26 ` Ken Witherow
2002-11-15 17:40 ` steve roemen
2002-11-15 18:21 ` Ken Witherow
2002-11-15 18:51 ` Alastair MacGregor
2002-11-16 3:04 ` Alan Cox
2002-01-01 2:12 ccroswhite
2002-01-01 3:23 ` Dave Jones
2002-01-01 3:40 ` Jeffrey H. Ingber
2002-01-01 4:46 ` Adam Schrotenboer
2002-01-01 6:58 ` Shaya Potter
2002-01-03 16:53 ` Andreas Bombe
2002-01-03 17:07 ` Dave Jones
2002-01-03 19:07 ` Shaya Potter
2002-01-03 17:48 ` H. Peter Anvin
2002-01-03 18:02 ` Dave Jones
2002-01-04 0:36 ` H. Peter Anvin
2002-01-04 2:15 ` Andreas Bombe
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=20020101152156.GB12799@gallifrey \
--to=gilbertd@treblig.org \
--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