From: Dan Noe <dpn@isomerica.net>
To: "Michael Elsdörfer" <michael@elsdoerfer.info>
Cc: Andi Kleen <andi@firstfloor.org>, linux-kernel@vger.kernel.org
Subject: Re: Cannot boot any HIGHMEM kernel (kernel panic - not syncing)
Date: Thu, 08 May 2008 14:31:52 -0400 [thread overview]
Message-ID: <48234718.10604@isomerica.net> (raw)
In-Reply-To: <4822EAC2.5010502@elsdoerfer.info>
On 5/8/2008 07:57, Michael Elsdörfer wrote:
> So the problem would be defective RAM in the machine?
Especially with an MCE versus evidence of random bit flipping, I would
also check to verify that all your memory modules are seated correctly.
If you are only using one of the DIMMs with LOWMEM only then you may
be avoiding one which has a flakey connection.
I have solved at least one other mysterious MCE problem by reseating the
DIMMS.
Cheers,
Dan
--
/--------------- - - - - - -
| Daniel Noe
| http://isomerica.net/~dpn/
next prev parent reply other threads:[~2008-05-08 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 11:03 Cannot boot any HIGHMEM kernel (kernel panic - not syncing) Michael Elsdörfer
2008-05-08 11:43 ` Andi Kleen
2008-05-08 11:57 ` Michael Elsdörfer
2008-05-08 18:31 ` Dan Noe [this message]
2008-05-08 19:41 ` Andi Kleen
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=48234718.10604@isomerica.net \
--to=dpn@isomerica.net \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@elsdoerfer.info \
/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