[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060915174701.GN4610@chain.digitalkingdom.org>
Date: Fri, 15 Sep 2006 10:47:01 -0700
From: Robin Lee Powell <rlpowell@...italkingdom.org>
To: Bharath Ramesh <krosswindz@...il.com>
Cc: Lee Revell <rlrevell@...-job.com>, linux-kernel@...r.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)
I didn't know about mce=bootlog. Neat. It doesn't change anything,
though. I've tried noacpi and many variants thereon; no change.
The most severe set of options I have record of trying is:
nosmp noapic mem=512M ide=nodma apm=off acpi=off desktop showopts
but there were lots of others.
mce=nobootlog doesn't help either, for the record.
If mce=bootlog actually sticks logs somewhere I should retrieve and
show to you, please tell me; ./Documentation/x86_64/boot-options.txt
doesn't say anything about it.
-Robin
On Fri, Sep 15, 2006 at 01:42:49AM -0400, Bharath Ramesh wrote:
> 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@...italkingdom.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@...ter) (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@...ter) (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@...ter) (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@...r.kernel.org
> >More majordomo info at http://vger.kernel.org/majordomo-info.html
> >Please read the FAQ at http://www.tux.org/lkml/
> >
--
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists