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: Fri, 19 Dec 2003 16:28:59 +0200	[thread overview]
Message-ID: <20031219142858.GC7009@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?
> 

If you say that CONFIG_DEBUG_SLAB=y solves the problem, you could start
by grepping in the kernel for CONFIG_DEBUG_SLAB and see what its doing.
This sounds like one of two things.
Either CONFIG_DEBUG_SLAB=y clears some memory which isn't cleared
properly somewhere else (there are quite a few kernel structures that
are allocated as slabs iirc), or its a timing problem that
CONFIG_DEBUG_SLAB solves by adding a printk somewhere that causes a
short delay (the second one will probably be a lot harder to solve).
I'll see if I have some time to look at it later.

> 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-19 14:28 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] ` <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
     [not found] ` <3FE28F79.601-Wuw85uim5zDR7s880joybQ@public.gmane.org>
2003-12-19 14:28   ` Micha Feigin [this message]
2003-12-21  1:45   ` Micha Feigin
  -- 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=20031219142858.GC7009@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