public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hugh <hugh@nospam.com>
To: linux-kernel@vger.kernel.org, coles@vip.kos.netDear
Subject: Re: Dual Athlon 2000 XP MP nightmare
Date: Sun, 16 Jun 2002 09:54:04 +0900	[thread overview]
Message-ID: <3D0BE1AC.3080202@nospam.com> (raw)

Dear Steve, Richard, and others,

>I'm not sure that what I'm experiencing is a kernel problem, but I >thought
>I would stick my foot in the door nonetheless, since I have no real
>indication of what is going on.
>
>I have a dual Athlon 2000+ XP MP system. It's crashing very frequently >and
>looks to be getting worse. It seems to crash less with 2.4.19pre10-ac2
>which supports the 760 bus and 744x IDE controller, but with something
>that
>is as intermittent as this, who can tell?

I found three of us trying to use Athlon dual as a linux server so far.

>Machine specs:
>
> ASUS A7M266-D motherboard, 1006 BIOS rev.
> 2GB ECC registered memory
> 4 x 15K RPM Seagate UltraSCSI drives

So far the same.

> 2 x 2960 (AIC7892 rev 2) controllers
> 2 x 3C59x 3Com ethernet controllers
> !USB card to free up IRQs (removed later)
> 400W power supply

I also have a 400 watts.

> 240W power supply driving two of the hard drives + CD ROM
> Budget vid card
> 2 drives partitioned 30%/70%, 30% mirrored together for boot, 70%
>mirrored
>in RAID 0+1 with other drives

I got intemittent Memory-related errors while running Latex on a 1000
page book manuscript.
Without the error, the speed on this machine was the most impressive:

Athlon dual 1.6GHz : 16 sec
P4 Xeon dual 1.7GHz : 52 sec
P III single at 700 MHz : 35 sec

No error log in /var/log/message.  Very rarely but certainly the
Athlon dual crashed with the Reiserfs error (horrible!! I lost a file
of a chapter.  I recovered it only from a backup.)  Initially, I
thought that it is a kernel problem in the recent kernels.  In the
end, I realized that the kernel version really does not matter.  I
finally checked the memory one by one using memtest86 with the ECC
disabled in the CMOS setup.   No problem.  I then installed all four
memory modules and did memtest86.  Alas!!!!,  it found the memory error.
  Did the test three times.  All three times, it always stopped in the
middle with slightly different error messages, everytime reinstalled
the memory modules just to be sure about the contact.

That was when I returned the motherboard the second time.
The first time, the board gave me a CMOS error.   The third time, the
board even did not give me the first beep.  I now think that I should
have bought the Tyan board instead of the ASUS.

Regards,

G. Hugh Song






             reply	other threads:[~2002-06-16  0:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-16  0:54 Hugh [this message]
2002-06-16  6:35 ` Dual Athlon 2000 XP MP nightmare Austin Gonyou
  -- strict thread matches above, loose matches on Subject: below --
2002-06-18  9:19 Hugh
2002-06-15 22:21 Steve Cole
2002-06-15 22:58 ` Dr. David Alan Gilbert
2002-06-17  2:30   ` Shawn
2002-06-17  2:35     ` Shawn
2002-06-16  0:37 ` Austin Gonyou
2002-06-16  8:30 ` Mark Hounschell
2002-06-16 12:29   ` Allan Sandfeld Jensen
2002-06-19 12:00     ` Bill Davidsen
2002-06-16 21:06   ` Austin Gonyou

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=3D0BE1AC.3080202@nospam.com \
    --to=hugh@nospam.com \
    --cc=coles@vip.kos.netDear \
    --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