From: Chris Gianelloni <wolf31o2@gentoo.org>
To: Kevin <gentoo-dev@gnosys.biz>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Major MCE problem with SMP on Gentoo kernels
Date: Tue, 11 May 2004 16:54:36 -0400 [thread overview]
Message-ID: <1084308876.1920.3.camel@localhost> (raw)
In-Reply-To: <200405111538.35551.gentoo-dev@gnosys.biz>
On Tue, 2004-05-11 at 15:38, Kevin wrote:
> Ok. Thanks for the suggestion. But what about this: Dell has a utility
> partition and some programs for doing exhaustive testing of all the
> hardware in the server. If I run the most thorough set of tests
> available in this utility partition and I get a clean bill of health,
> is that a reliable indication that there are no hardware problems? Or
> does memtest86 do testing that's more exhaustive than most such utility
> suites?
I think the Dell suite would be more extensive.
> If the utility partition testing says all is well (I've done it several
> times in the last month or so, though maybe not the most extensive
> tests), what's the next place to look for an explanation of why this
> MCE is happening in Gentoo but not in SuSE?
Are you sure that it isn't MCE *causing* these problems? Have you tried
turning it off and seeing if you still have the same kinds of problems?
--
Chris Gianelloni
Developer, Gentoo Linux
Games Team
Is your power animal a penguin?
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-05-11 20:57 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 [this message]
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
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=1084308876.1920.3.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