public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Micha Feigin <michf-+lLcF8/aw9x6auLlOhE+pQ@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Plea for help
Date: Sun, 21 Dec 2003 03:45:25 +0200	[thread overview]
Message-ID: <20031221014525.GB3587@luna.mooo.com> (raw)
In-Reply-To: <3FE28F79.601-Wuw85uim5zDR7s880joybQ@public.gmane.org>

On Thu, Dec 18, 2003 at 11:41:13PM -0600, Ian Pilcher wrote:
> 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?
> 

I had a brief look at what CONFIG_DEBUG_SLAB=y option does. It looks
that beside adding some debug output and sanity checks it also
initializes the memory to a non null pattern (poison something). You
could start with setting that pattern to 0x00 instead of what it is and
see if that returns your oopses (don't know where it points, but thats
probably won't do anything but could give you a null pointer access).
Otherwise I would follow the changes (it changes the DEBUG flag and
don't remember what else) and see if it changes anything (other then
the poison thing) or just read tests the results and prints error
messages. If that is the case than what you probably have is a race
condition causing some kind of timing problem.

> 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
> _______________________________________________
> Acpi-devel mailing list
> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/acpi-devel
> 


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

  parent reply	other threads:[~2003-12-21  1:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-19  5:41 Plea for help Ian Pilcher
     [not found] ` <3FE28F79.601-Wuw85uim5zDR7s880joybQ@public.gmane.org>
2003-12-19 14:28   ` Micha Feigin
2003-12-21  1:45   ` Micha Feigin [this message]
     [not found] ` <3FE33B69.1010606@netspace.org>
     [not found]   ` <3FE33B69.1010606-ooduxAEi7gVg9hUCZPvPmw@public.gmane.org>
2003-12-20  0:05     ` Ian Pilcher
     [not found]       ` <3FE39231.4040003-Wuw85uim5zDR7s880joybQ@public.gmane.org>
2003-12-20  0:09         ` Randy.Dunlap
     [not found]           ` <20031219160947.79c3fcdf.rddunlap-3NddpPZAyC0@public.gmane.org>
2003-12-20  1:09             ` Ian Pilcher
     [not found]               ` <3FE3A142.90407-Wuw85uim5zDR7s880joybQ@public.gmane.org>
2003-12-20  2:40                 ` Randy.Dunlap
     [not found]                   ` <20031219184043.3983572d.rddunlap-3NddpPZAyC0@public.gmane.org>
2003-12-20 19:47                     ` Ian Pilcher
     [not found]                       ` <3FE4A740.4080701-Wuw85uim5zDR7s880joybQ@public.gmane.org>
2003-12-21  2:08                         ` Randy.Dunlap
     [not found]                           ` <20031220180854.32e2f56d.rddunlap-3NddpPZAyC0@public.gmane.org>
2003-12-22  1:19                             ` Ian Pilcher
  -- strict thread matches above, loose matches on Subject: below --
2003-12-24  6:04 Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401720C53-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2003-12-29 23:17   ` Ian Pilcher
2003-12-31  9:58 Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401720C66-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-01 16:54   ` Ian Pilcher
2004-01-02  7:34 Yu, Luming

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20031221014525.GB3587@luna.mooo.com \
    --to=michf-+llcf8/aw9x6aullohe+pq@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox