From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: tepperly@llnl.gov (Tom Epperly)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox), 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 17:08:14 +0000 (GMT) [thread overview]
Message-ID: <E16kTHS-00016E-00@the-village.bc.nu> (raw)
In-Reply-To: <3C8CD629.5090003@llnl.gov> from "Tom Epperly" at Mar 11, 2002 08:07:05 AM
> 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.
It does sound like either a bad compiler (eg gcc 3) which is unlikely but
possible or your workload triggers something important and unusual which is
buggy. Do you know which bit of the workload is the trigger - is it practical
to find out ?
Alan
next prev parent reply other threads:[~2002-03-11 16:53 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 ` RH7.2 running 2.4.9-21-SMP (dual Xeon's) yields "Illegal instructions" Tom Epperly
2002-03-11 17:08 ` Alan Cox [this message]
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=E16kTHS-00016E-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tepperly@llnl.gov \
/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
all inboxes | Powered by JetHome®