Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751172AbVJ2Oy0 (ORCPT ); Sat, 29 Oct 2005 10:54:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751174AbVJ2Oy0 (ORCPT ); Sat, 29 Oct 2005 10:54:26 -0400 Received: from sender-01.it.helsinki.fi ([128.214.205.139]:33975 "EHLO sender-01.it.helsinki.fi") by vger.kernel.org with ESMTP id S1751172AbVJ2OyZ (ORCPT ); Sat, 29 Oct 2005 10:54:25 -0400 Date: Sat, 29 Oct 2005 17:54:21 +0300 (EEST) From: Janne M O Heikkinen X-X-Sender: jmoheikk@rock.it.helsinki.fi To: Andi Kleen cc: linux-kernel@vger.kernel.org Subject: Re: x86_64: 2.6.14 with NUMA panics at boot In-Reply-To: Message-ID: References: <200510291201.06613.ak@suse.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 669 Lines: 14 On Sat, 29 Oct 2005, Janne M O Heikkinen wrote: > No, I get same panics with numa=noacpi or even with numa=off. If I compile > 2.6.14 kernel without CONFIG_ACPI_NUMA it does boot. It wasn't removing of CONFIG_ACPI_NUMA that made it boot after all, I had also changed memory model from "Sparse" to "Discontiguous". And now when I recompiled with CONFIG_ACPI_NUMA=y and with "Discontiguous" memory model it booted just fine. - 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/