Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261463AbUCEXNK (ORCPT ); Fri, 5 Mar 2004 18:13:10 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261465AbUCEXNK (ORCPT ); Fri, 5 Mar 2004 18:13:10 -0500 Received: from ns.suse.de ([195.135.220.2]:14747 "EHLO Cantor.suse.de") by vger.kernel.org with ESMTP id S261463AbUCEXNI (ORCPT ); Fri, 5 Mar 2004 18:13:08 -0500 To: Stuart_Hayes@Dell.com Cc: linux-kernel@vger.kernel.org Subject: Re: ACPI stack overflow References: From: Andi Kleen Date: 06 Mar 2004 00:13:06 +0100 In-Reply-To: Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1024 Lines: 14 Stuart_Hayes@Dell.com writes: > Hello... > > I think I am getting a stack overflow when Linux is parsing the ACPI tables (initializing all the devices and running all the _STA methods). I am using the x86_64 architecture. I would like to try increasing the kernel stack size, but I'm not sure how to go about doing this. Could someone tell me how to increase the kernel stack size? (And, has anyone else seen a problem with stack overflows with ACPI?) Increasing THREAD_ORDER to 2 in include/asm-x86_64/page.h should do the trick in theory (not tested). There is also an old 2.4 exact stack overflow checking patch at ftp://ftp.x86-64.org/pub/linux/debug/stackcheck-1 that could be probably ported to newer kernels. I haven't heard of ACPI stack overflows before. -Andi - 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/