From: Chris Gianelloni <wolf31o2@gentoo.org>
To: Kevin <gentoo-dev@gnosys.biz>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] SOLVED: Major MCE problem with SMP on Gentoo kernels
Date: Fri, 21 May 2004 09:05:51 -0400 [thread overview]
Message-ID: <1085144751.25042.31.camel@localhost> (raw)
In-Reply-To: <200405201716.27770.gentoo-dev@gnosys.biz>
[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]
On Thu, 2004-05-20 at 17:16, Kevin wrote:
> But the bizarre thing is that I couldn't reproduce this MCE at all using
> another distribution on the same (pre-replacement) hardware. Does Gentoo
> push the hardware much harder than other distros? Perhaps because I'm
> compiling the code for my particular hardware vice running code that was
> built to run on many different sets of hardware (less aggressive CFLAGS
> et. al.)? I'm at a loss to explain this.
Simply... Yes. You are using, even at -march=pentium3, the MMX and SSE
portions of the chip, which may not be used at all on another
distribution (compiled -march=i586) at all.
CFLAGS, as both the Gnome and KDE teams can attest, can make a world of
difference on how things come out in the end.
As for the memtest86 problem, who knows... ask the memtest86 guys.
They'd probably be really interested in your findings.
--
Chris Gianelloni
Developer
Games/LiveCD Teams
Gentoo Linux
Is your power animal a penguin?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-21 12:58 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
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 [this message]
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=1085144751.25042.31.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