public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Hounschell <dmarkh@cfl.rr.com>
To: Steve Cole <coles@vip.kos.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dual Athlon 2000 XP MP nightmare
Date: Sun, 16 Jun 2002 04:30:39 -0400	[thread overview]
Message-ID: <3D0C4CAF.578D7CC1@cfl.rr.com> (raw)
In-Reply-To: <003101c214bb$0275a720$0a00000a@kos.net>

Steve Cole wrote:
> 
>  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?
> 
> Machine specs:
> 
>  ASUS A7M266-D motherboard, 1006 BIOS rev.
>  2GB ECC registered memory
>  4 x 15K RPM Seagate UltraSCSI drives
>  2 x 2960 (AIC7892 rev 2) controllers
>  2 x 3C59x 3Com ethernet controllers
>  !USB card to free up IRQs (removed later)
>  400W power supply
>  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 get EIP errors and Null pointer exception errors during full kernel
> panics.  I've had a lot of file system corruption in ReiserFS originally and
> now in EXT2, both fixable though Reiser seemed worse.  Uptime is measured in
> hours - usually 12 or more, sometimes two or three.
> 
> I can't come up with any reasons for this that point at the kernel, but on
> the other hand, nothing is ever logged regarding SCSI I/O problems (verbose
> logging turned on in kernel with extra queue checks).  I've replaced the
> > memory to no avail, and updated the BIOS' of both motherboard and Adaptec
> cards.  No memory errors are logged and one pass of memtest86 found no
> memory errors.
> 
> Yet, the machine crashes semi-randomly (load seems to play some part in
> this) and often crashes during the shutdown/reboot phase if it's run
> reliably for a few hours.
> 
> If it's hardware for sure, please just indicate that and I'll move on.  I'm
> getting semi-desperate. :(
> 

First make sure you have MP cpus NOT XP's. The XP's are not certified by amd to run
SMP. Second, try append="mem=nopentium" in your lilo.conf file. I have a dual 1900+ MP
box and without that I have random lockups also.

Mark

  parent reply	other threads:[~2002-06-16  8:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-15 22:21 Dual Athlon 2000 XP MP nightmare 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 [this message]
2002-06-16 12:29   ` Allan Sandfeld Jensen
2002-06-19 12:00     ` Bill Davidsen
2002-06-16 21:06   ` Austin Gonyou
  -- strict thread matches above, loose matches on Subject: below --
2002-06-16  0:54 Hugh
2002-06-16  6:35 ` Austin Gonyou
2002-06-18  9:19 Hugh

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=3D0C4CAF.578D7CC1@cfl.rr.com \
    --to=dmarkh@cfl.rr.com \
    --cc=coles@vip.kos.net \
    --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