From: "Bharath Ramesh" <krosswindz@gmail.com>
To: "Robin Lee Powell" <rlpowell@digitalkingdom.org>
Cc: "Lee Revell" <rlrevell@joe-job.com>, linux-kernel@vger.kernel.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: Fri, 15 Sep 2006 01:42:49 -0400 [thread overview]
Message-ID: <c775eb9b0609142242r45d184d2h8d7edd7dd5bc2a26@mail.gmail.com> (raw)
In-Reply-To: <20060914191555.GJ4610@chain.digitalkingdom.org>
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.
Bharath
On 9/14/06, Robin Lee Powell <rlpowell@digitalkingdom.org> wrote:
> On Thu, Sep 14, 2006 at 03:14:08PM -0400, Lee Revell wrote:
> > On Thu, 2006-09-14 at 12:05 -0700, Robin Lee Powell wrote:
> > > This isn't just me. All the Debian kernels hang too. I've tried
> > > all of the following:
> > >
> > > Linux version 2.6.8-12-amd64-generic (buildd@bester) (gcc version
> > > 3.4.4 20050314 (prerelease) (Debian 3.4.3-13)) #1 Mon Jul 17 01:12:05
> > > UTC 2006
> > >
> > > Linux version 2.6.8-12-amd64-k8 (buildd@bester) (gcc version 3.4.4
> > > 20050314 (prerelease) (Debian 3.4.3-13)) #1 Mon Jul 17 01:39:03 UTC
> > > 2006
> > >
> > > Linux version 2.6.8-12-amd64-k8-smp (buildd@bester) (gcc version 3.4.4
> > > 20050314 (prerelease) (Debian 3.4.3-13)) #1 SMP Mon Jul 17 00:17:20
> > > UTC 2006
> >
> > Have you tried a *recent* 2.6 kernel like 2.6.17 or 2.6.18-rc*?
> >
> > 2.6.8 is way too old to debug.
>
> Yes; that's what my previous post was about. See
> http://lkml.org/lkml/2006/9/12/300
>
> I was doing 2.6.17.11, which was kernel.org's latest stable at the
> time I started all this.
>
> I tried the Debian kernels just to show that it wasn't just me
> screwing up my kernel configs.
>
> These machines will not boot an any kernel > 2.6.3 that I have
> tried, and I've tried about 8 different ones at this point.
>
> I noted in the release notes for 2.6.4 that the mce code was
> entirely replaced; I'm suspecting that's the problem, but I have no
> idea how to debug it. Whether the problem is the kernel or the
> motherboard is also certainly open to debate.
>
> -Robin
>
> --
> http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/
> Reason #237 To Learn Lojban: "Homonyms: Their Grate!"
> Proud Supporter of the Singularity Institute - http://singinst.org/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2006-09-15 5:42 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 [this message]
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
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=c775eb9b0609142242r45d184d2h8d7edd7dd5bc2a26@mail.gmail.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®