public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael Elsdörfer" <michael@elsdoerfer.info>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Cannot boot any HIGHMEM kernel (kernel panic - not syncing)
Date: Thu, 08 May 2008 13:57:54 +0200	[thread overview]
Message-ID: <4822EAC2.5010502@elsdoerfer.info> (raw)
In-Reply-To: <87od7h9g1s.fsf@basil.nowhere.org>

 >> Now, Machine Check Exception seems to point towards a hardware error,
 >
 > It not only seems to, it does.
 > The non highmem kernel will simply not use most of your memory, so if
 > the machine check happens accessing memory you will not see it.

Thanks Andi.

So the problem would be defective RAM in the machine?

I'm still wondering though while the previous kernel (a self-compiled 
2.6.17.11) worked then. Laxer checks?

Michael

  reply	other threads:[~2008-05-08 11:58 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 [this message]
2008-05-08 18:31     ` Dan Noe
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=4822EAC2.5010502@elsdoerfer.info \
    --to=michael@elsdoerfer.info \
    --cc=andi@firstfloor.org \
    --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