All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tom Epperly" <tepperly@llnl.gov>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RH7.2 running 2.4.9-21-SMP (dual Xeon's) yields "Illegal instructions"
Date: Mon, 11 Mar 2002 08:07:05 -0800	[thread overview]
Message-ID: <3C8CD629.5090003@llnl.gov> (raw)
In-Reply-To: <E16dxoe-0007l6-00@the-village.bc.nu>

Alan Cox wrote:

>>Do you agree that this is likely to be a kernel problem?  Is upgrading
>>the kernel my best course of action?
>>
>
>Almost every other report I have ever seen that looked like that one has always
>turned out to be hardware related. The randomness in paticular tends to be 
>a pointer to thinks like cache faults.
>
>You do have ECC main memory which is good.
>
>What other hardware is in the machine ?
>
>
To recap from an earlier email, my nightly build & regression tests (a 
roughly 2 hour process involving Sun's JDK, GNU make, gcc, g++, g77 & 
Bourne shell scripts) has been failing intermittently on a dual-Xeon 
system usually with an "Illegal intruction" signal. I've tried removing 
the sound card and disabling the X11 server to avoid loading the nVidia 
kernel mod. The intermittent failures disappear when I run non-SMP. I've 
tried swapping the processors on the motherboard, and both processors 
appear to work fine individually. Most of the boxes I've run on have >= 
512MB ECC RAM. I've run Dell's hardware diagnostics (especially the 
memory ones) twice. The diagnostics don't seem to have SMP tests where 
both CPUs are being stressed.

FYI when I upgraded to the 2.4.18-1smp kernel, the failure rate went 
from 20% to 100%. I have tried running the nightly build & regression on 
roughly 6 different dual processors Pentium III or better machines 
(cylcing it over and over), and they all have intermittent failures of 
one kind or another. All these machines are made by Dell, but they 
provide some evidence that it is not a hardware problem.

Tom


  parent reply	other threads:[~2002-03-11 16:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-21 17:35 RH7.2 running 2.4.9-21-SMP (dual Xeon's) yields "Illegal instructions" during builds Tom Epperly
2002-02-21 18:19 ` RH7.2 running 2.4.9-21-SMP (dual Xeon's) yields "Illegal instructions" Alan Cox
2002-02-21 18:26   ` Tom Epperly
2002-02-21 18:33     ` RH7.2 running 2.4.9-21-SMP (dual Xeon's) yields "Illegal arjan
2002-02-21 19:23       ` Tom Epperly
2002-02-21 19:41         ` Alan Cox
2002-02-21 20:21         ` J Sloan
2002-02-21 19:05     ` RH7.2 running 2.4.9-21-SMP (dual Xeon's) yields "Illegal instructions" Richard B. Johnson
2002-02-21 19:36     ` RH7.2 running 2.4.9-21-SMP (dual Xeon's) yields "Illegal Alan Cox
2002-02-22 22:45       ` Tom Epperly
2002-03-11 16:07   ` Tom Epperly [this message]
2002-03-11 17:08     ` RH7.2 running 2.4.9-21-SMP (dual Xeon's) yields "Illegal instructions" Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2002-03-11 20:26 James Washer

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=3C8CD629.5090003@llnl.gov \
    --to=tepperly@llnl.gov \
    --cc=alan@lxorguk.ukuu.org.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.