public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: Kevin <gentoo-dev@gnosys.biz>
Cc: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Major MCE problem with SMP on Gentoo kernels
Date: Wed, 12 May 2004 10:44:29 -0400	[thread overview]
Message-ID: <1084373069.7729.55.camel@localhost> (raw)
In-Reply-To: <200405120958.45686.gentoo-dev@gnosys.biz>

[-- Attachment #1: Type: text/plain, Size: 1325 bytes --]

On Wed, 2004-05-12 at 09:58, Kevin wrote:
> Oh....  Well, that seems like an important difference between yours and my 
> arrangements.  Are you running Gentoo on a box with more than one 
> physical CPU?  I had no problems running Gentoo on this box until after 
> installing a second CPU.  That's when the weirdness started.
> 
> Is anyone here running Gentoo on a dual-physical CPU machine?  What 
> compiler flags are you using?

I am running Gentoo on several dual-CPU machines, and even one quad-CPU
machine with no troubles at all.

CFLAGS="-march=pentium4 -O2 -pipe -fomit-frame-pointer"

> > > FEATURES="autoaddcvs ccache distcc sandbox"
> 
> Huh.  That's odd.  When I installed distcc, I changed the FEATURES as 
> indicated in the docs to list distcc, but I didn't add any of those 
> others.  Wonder where they came from...

They came from the defaults.  Unless you set -autoaddcvs, etc in your
FEATURES.  There's no need to try to remove autoaddcvs, since it just
won't work.

> I was thinking "number of physical CPUs + 1" here, but ok.

You would probably get a speed boost going with -j5 rather than -j3, but
I would bench it myself before trusting anything from an external
source.

-- 
Chris Gianelloni
Developer, Gentoo Linux
Games Team

Is your power animal a penguin?

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-05-12 14:43 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-11 18:07 [gentoo-dev] Major MCE problem with SMP on Gentoo kernels Kevin
2004-05-11 18:46 ` Greg KH
2004-05-11 18:55   ` Kevin
2004-05-11 19:04     ` Greg KH
2004-05-11 19:38       ` Kevin
2004-05-11 20:54         ` Chris Gianelloni
2004-05-11 21:31           ` Kevin
2004-05-11 19:38     ` Paul de Vrieze
2004-05-11 21:37       ` Kevin
2004-05-12  1:02         ` Georgi Georgiev
2004-05-12 10:23           ` [gentoo-dev] [OT] SuSE kernel on gentoo system (Was: Re: Major MCE problem with SMP on Gentoo kernels) sf
2004-05-12  2:42 ` [gentoo-dev] Major MCE problem with SMP on Gentoo kernels Josh Glover
2004-05-12  9:31   ` Dan Podeanu
2004-05-12 11:26     ` Kevin
2004-05-12 11:24   ` Kevin
2004-05-12 11:48     ` Josh Glover
2004-05-12 12:14       ` Ciaran McCreesh
2004-05-12 13:58       ` Kevin
2004-05-12 14:44         ` Chris Gianelloni [this message]
2004-05-12 15:17         ` tom_gall
2004-05-13 11:06           ` Kevin
2004-05-13 11:12             ` Senor Rodgman
2004-05-13 13:04             ` Chris Gianelloni
2004-05-13 15:04             ` Daniel Drake
2004-05-13 15:54             ` Greg KH
2004-05-18  8:29               ` Kevin
2004-05-18 10:59                 ` Alexander Futasz
2004-05-18 12:02                 ` Josh Glover
2004-05-19 17:48                   ` Kevin
2004-05-20 12:19                     ` [gentoo-dev] SOLVED: " Kevin
2004-05-20 21:16                     ` Kevin
2004-05-20 21:32                       ` Greg KH
2004-05-20 23:08                       ` Robin H. Johnson
2004-05-20 23:16                         ` Hasse Hagen Johansen
2004-05-21  2:46                           ` Kevin
2004-05-21 13:05                       ` Chris Gianelloni
2004-05-18 12:46                 ` [gentoo-dev] " Daniel Drake
     [not found]         ` <40A23987.9080104@gentoo.org>
2004-05-12 16:22           ` [gentoo-dev] memtest86 fails? (was Re: [gentoo-dev] Major MCE problem with SMP on Gentoo kernels) Kevin
2004-05-12 16:59             ` Greg KH
2004-05-12 17:18               ` Scott Myron
2004-05-12 17:15             ` Sven Vermeulen

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=1084373069.7729.55.camel@localhost \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-dev@gnosys.biz \
    --cc=gentoo-dev@lists.gentoo.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