All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Pilcher <i.pilcher-Wuw85uim5zDR7s880joybQ@public.gmane.org>
To: Alan Cox <alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: CONFIG_DEBUG_SLAB=y prevents kernel panic
Date: Sat, 06 Dec 2003 03:05:51 -0600	[thread overview]
Message-ID: <3FD19BEF.2060807@comcast.net> (raw)
In-Reply-To: <1070673944.30487.17.camel-Z+iYsftfazAXoXS6vNje7nviChZXdy279dF7HbQ/qKg@public.gmane.org>

Alan Cox wrote:
> On Gwe, 2003-12-05 at 20:55, Ian Pilcher wrote:
> 
>>The question is, where do I go from here?  The help for
>>CONFIG_DEBUG_SLAB makes it seem unlikely that this is the root cause,
>>but I don't have any idea how I can debug this further.
> 
> 
> If that is really what makes the difference then 99 times out of 100 you
> are looking for code that kmallocs memory and then relies on its content
> without clearing it.
> 
> 

Setting CONFIG_DEBUG_SLAB is definitely the deciding factor.  (I editted
the i686-smp config file and rebuilt the SRPM; voila!, it boots with
ACPI turned on.)

Any suggestions on how I can find the offending code?

-- 
========================================================================
Ian Pilcher                                        i.pilcher-Wuw85uim5zDR7s880joybQ@public.gmane.org
========================================================================




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/

      parent reply	other threads:[~2003-12-06  9:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-05 20:55 CONFIG_DEBUG_SLAB=y prevents kernel panic Ian Pilcher
     [not found] ` <3FD0F0DE.4050708-Wuw85uim5zDR7s880joybQ@public.gmane.org>
2003-12-05 22:35   ` Janek Kozicki
2003-12-06  1:25   ` Alan Cox
     [not found]     ` <1070673944.30487.17.camel-Z+iYsftfazAXoXS6vNje7nviChZXdy279dF7HbQ/qKg@public.gmane.org>
2003-12-06  9:05       ` Ian Pilcher [this message]

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=3FD19BEF.2060807@comcast.net \
    --to=i.pilcher-wuw85uim5zdr7s880joybq@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.