public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Gerst <bgerst@didntduck.org>
To: Christian Thalinger <e9625286@student.tuwien.ac.at>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: floating point exception
Date: Wed, 16 Jan 2002 08:52:14 -0500	[thread overview]
Message-ID: <3C45858E.39F31DBA@didntduck.org> (raw)
In-Reply-To: <1010925802.674.0.camel@sector17.home.at>  <3C44BB1B.E1F3318C@didntduck.org> <1011181530.513.0.camel@sector17.home.at>

Christian Thalinger wrote:
> 
> On Wed, 2002-01-16 at 00:28, Brian Gerst wrote:
> > What CPU do you have?  Do you have the FPU emulator compiled in?  Are
> > there any oops messages?
> >
> > --
> >                                               Brian Gerst
> >
> 
> I mentioned in my first mail the dual tyan, so athlon xp, no fpu
> emulator ;-) and no oops messages.

Last I checked, Athlon XP's weren't certified for SMP, only MP's. 
That's likely what the problem is.  And for the record, Tyan also makes
Intel boards too.

Processor manufacturing 101:  All processors of a given family come off
the same production line.  Due to variations in the process, some
processors have defects that only show up at higher clock speeds, SMP
mode, etc.  At the end of the line the processor is tested.  If it fails
at higher clock speeds it is marked at a lower speed.  If it fails SMP
it is marked as an XP.  Market demand can also cause a chip to be rated
lower than it really is, so you can sometimes get away with
overclocking, etc. but it's just random luck if it really works.

-- 

						Brian Gerst

  parent reply	other threads:[~2002-01-16 13:51 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-13 12:43 floating point exception Christian Thalinger
2002-01-15 23:28 ` Brian Gerst
2002-01-16 11:45   ` Christian Thalinger
2002-01-16 11:58     ` Dave Jones
2002-01-16 13:14       ` Bruce Harada
2002-01-16 20:06         ` Christian Thalinger
2002-01-17 19:26         ` bill davidsen
2002-01-16 13:52     ` Brian Gerst [this message]
2002-01-16 14:28       ` M. Edward (Ed) Borasky
  -- strict thread matches above, loose matches on Subject: below --
2002-01-14 10:56 Zwane Mwaikambo
2002-01-14 21:26 ` Christian Thalinger
2002-01-15 14:34   ` Zwane Mwaikambo
2002-01-15 14:46     ` Richard B. Johnson
2002-01-15 18:19     ` Christian Thalinger
2002-01-15 18:31       ` Richard B. Johnson
2002-01-15 18:49         ` Christian Thalinger
2002-01-16  5:45       ` Zwane Mwaikambo
2002-01-16 11:55         ` Christian Thalinger
2002-01-16 14:32           ` Zwane Mwaikambo
2002-01-16 20:26             ` Christian Thalinger
2002-01-16 21:23               ` Richard B. Johnson
2002-01-16 21:59                 ` Brian Gerst
2002-01-16 22:05                   ` Richard B. Johnson
2002-01-16 22:12                     ` Mark Zealey
2002-01-16 22:23                       ` Richard B. Johnson
2002-01-16 23:35                     ` Christian Thalinger
2002-12-27 14:18 Floating Point Exception Nandakumar  NarayanaSwamy

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=3C45858E.39F31DBA@didntduck.org \
    --to=bgerst@didntduck.org \
    --cc=e9625286@student.tuwien.ac.at \
    --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