Plea for help

[Ian Pilcher <i.pilcher-Wuw85uim5zDR7s880joybQ@public.gmane.org>]

I posted a couple of weeks ago about a kernel panic that shows up when I
boot my Abit VP6 (dual-PIII) with ACPI turned on.  It turns out that the
kernel boots just fine with ACPI on when I build it with
CONFIG_DEBUG_SLAB=y.

Alan Cox suggested that this is probably due to code that kmallocs
memory and then relies on its content without clearing it, but I never
received any response to my request for suggestions on how to identify
the offending code.

I've just spent several hours adding printk statements to the ACPI code,
and I've reached a point where the oops message is overwriting portions
of my printk messages.  I have the sinking feeling that this indicates
that the process executing the ACPI code is not the one that's oops'ing.

I'm stuck.  How can a relative newbie debug a problem like this, or at
least gather enough information to enable someone with more expertise to
do so?

TIA.
-- 
========================================================================
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