Date: Fri, 15 Sep 2006 13:31:59 -0700
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: 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)
Message-ID: <20060915203159.GS4610@chain.digitalkingdom.org>
References: <20060912223258.GM4612@chain.digitalkingdom.org> <20060914190548.GI4610@chain.digitalkingdom.org> <1158320742.29932.20.camel@localhost.localdomain> <20060915182915.GR4610@chain.digitalkingdom.org> <1158353439.29932.146.camel@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1158353439.29932.146.camel@localhost.localdomain>
User-Agent: Mutt/1.5.12-2006-07-14
From: Robin Lee Powell <rlpowell@digitalkingdom.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1005
Lines: 27

On Fri, Sep 15, 2006 at 09:50:39PM +0100, Alan Cox wrote:
> Ar Gwe, 2006-09-15 am 11:29 -0700, ysgrifennodd Robin Lee Powell:
> > > 	pci=conf2
> > 
> > No effect without acpi=off.
> > 
> > With acpi=off, it gets rather farther before apparently failing to
> > talk the 3-ware card:
> 
> Thats helpful. The conf2 cycles are the wrong type for the board
> so with acpi=off pci=conf2 it doesn't see any PCI devices and
> doesn't explode. I see nothing odd in the lspci data at all
> however.
> 
> You also have a lot of RAM, that shouldn't matter but it means you
> hit code paths most users don't. If you boot with mem limited to
> 1GB I assume it still blows up ?

I've tried mem=1023M, yes, and it still blows up.  Just did acpi=off
mem=1023M to check.

-Robin
-
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/