From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Pilcher Subject: Re: Plea for help Date: Fri, 19 Dec 2003 18:05:05 -0600 Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: <3FE39231.4040003@comcast.net> References: <3FE28F79.601@comcast.net> <3FE33B69.1010606@netspace.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <3FE33B69.1010606-ooduxAEi7gVg9hUCZPvPmw@public.gmane.org> Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Brian Perkins Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: linux-acpi@vger.kernel.org Brian Perkins wrote: > First of all, what's the panic like? > Does it give a function? > You do have all of the kernel hacking options on, don't you? > You can see the panic at http://home.comcast.net/~i.pilcher/panics/1/panic.txt The config used to produce it is at http://home.comcast.net/~i.pilcher/panics/1/config Unfortunately, if I turn CONFIG_FRAME_POINTER on I don't get the panic, just the hang at http://home.comcast.net/~i.pilcher/panics/2/hang.txt Config at http://home.comcast.net/~i.pilcher/panics/2/config And as I previously mentioned, turning CONFIG_DEBUG_SLAB on prevents the panic entirely. -- ======================================================================== Ian Pilcher i.pilcher-Wuw85uim5zDR7s880joybQ@public.gmane.org ======================================================================== ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click