From: Andi Kleen <ak@suse.de>
To: "Bharath Ramesh" <krosswindz@gmail.com>
Cc: "Lee Revell" <rlrevell@joe-job.com>,
linux-kernel@vger.kernel.org, rlpowell@digitalkingdom.org
Subject: Re: Same MCE on 4 working machines (was Re: Early boot hang on recent 2.6 kernels (> 2.6.3), on x86-64 with 16gb of RAM)
Date: 18 Sep 2006 09:52:18 +0200 [thread overview]
Message-ID: <p737j01628d.fsf@verdi.suse.de> (raw)
In-Reply-To: <c775eb9b0609142242r45d184d2h8d7edd7dd5bc2a26@mail.gmail.com>
"Bharath Ramesh" <krosswindz@gmail.com> writes:
> Have you tried booting newer kernel post 2.6.13 with the boot option
> mce=bootlog and see if it goes past the current failure. Try the same
> with with noacpi.
Did you mean mce=off? mce=bootlog will just log the leftover MCEs
from the previous boot, but that shouldn't change anything.
-Andi
next prev parent reply other threads:[~2006-09-18 7:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-12 22:32 Early boot hang on recent 2.6 kernels (> 2.6.3), on x86-64 with 16gb of RAM Robin Lee Powell
2006-09-14 19:05 ` Same MCE on 4 working machines (was Re: Early boot hang on recent 2.6 kernels (> 2.6.3), on x86-64 with 16gb of RAM) Robin Lee Powell
2006-09-14 19:14 ` Lee Revell
2006-09-14 19:15 ` Robin Lee Powell
2006-09-15 5:42 ` Bharath Ramesh
2006-09-15 17:47 ` Robin Lee Powell
2006-09-15 18:07 ` Robin Lee Powell
2006-09-15 18:22 ` Alan Cox
2006-09-15 18:12 ` Robin Lee Powell
2006-09-18 7:52 ` Andi Kleen [this message]
2006-09-18 18:59 ` Robin Lee Powell
2006-09-15 11:45 ` Alan Cox
2006-09-15 18:29 ` Robin Lee Powell
2006-09-15 20:50 ` Alan Cox
2006-09-15 20:31 ` Robin Lee Powell
2006-09-15 23:18 ` Robin Lee Powell
2006-09-18 7:50 ` Early boot hang on recent 2.6 kernels (> 2.6.3), on x86-64 with 16gb of RAM Andi Kleen
2006-09-18 19:06 ` Robin Lee Powell
2006-09-18 23:58 ` Robin Lee Powell
2006-09-19 6:04 ` Andi Kleen
2006-09-19 6:28 ` Robin Lee Powell
2006-09-19 6:39 ` Andi Kleen
2006-09-19 17:46 ` Robin Lee Powell
2006-09-19 21:07 ` Robin Lee Powell
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=p737j01628d.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=krosswindz@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlpowell@digitalkingdom.org \
--cc=rlrevell@joe-job.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.