mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shane Nay <shane@minirl.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Nicolas.Turro@sophia.inria.fr (Nicolas Turro)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
	Nicolas.Turro@sophia.inria.fr (Nicolas Turro),
	linux-kernel@vger.kernel.org
Subject: Re: amd nvidia and mem=nopentium
Date: Tue, 19 Mar 2002 07:11:22 -0800	[thread overview]
Message-ID: <20020319150920Z311378-889+124219@vger.kernel.org> (raw)
In-Reply-To: <E16nL60-0007uF-00@the-village.bc.nu>

> I'd go Athlon
>
> >  Do you have pointers  showing stability problems when using
> > XP processor in a multiprocessor context ?
>
> Remember the XP's haven't been tested in MP configurations (or
> tested and failed). The same was true of celerons and as most
> people found the fail rate was pretty low 8)

You have to bridge L5-4 on the newest XP CPUs though.  My Tyan Tiger 
boards' BIOS was giving me something like-
00Error
  Failed

Turned out it needed those guys bridged up.  It's not that difficult 
though, I had a circuit pen lying about and just drew in a trace :).  
(You don't have to fill the cracks like the overclock bridges)

Anyway, it was pretty easy, but I wouldn't suggest it for the faint 
of heart.  Running 2.4.18 happily now in dual config with no 
stability problems.  I have compiled the kernel a few times, compiled 
Qt, all of KDE, xemacs, glibc, gcc, and a couple billion other things 
that I can't remember right now.  So, no stability problems with the 
newest XPs and a hand closed L5-4 bridge.  (So far anyway :) )

Thanks,
Shane Nay.

      reply	other threads:[~2002-03-19 15:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-15 18:41 Nicolas Turro
2002-03-15 19:05 ` Alan Cox
2002-03-19 14:19   ` Nicolas Turro
2002-03-19 15:00     ` Alan Cox
2002-03-19 15:11       ` Shane Nay [this message]

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=20020319150920Z311378-889+124219@vger.kernel.org \
    --to=shane@minirl.com \
    --cc=Nicolas.Turro@sophia.inria.fr \
    --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 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®