From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Hubert Figuiere <hub-linux-ppc@trantor.staff.proxad.net>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: kernel panic in slab.c
Date: Thu, 25 Sep 2003 15:44:11 +0200 [thread overview]
Message-ID: <1064497450.702.12.camel@gaston> (raw)
In-Reply-To: <1064493093.17039.44.camel@trantor.staff.proxad.net>
On Thu, 2003-09-25 at 14:31, Hubert Figuiere wrote:
> Hi,
>
> I'm getting kernel panics (during boot up or 5 minutes after, it depends
> of the wind, the external temperature, or how old is the captain ;-) )
> when I activate CONFIG_SLAB_DEBUG.
>
> Here is the output:
> kernel BUG at slab.c:1263!
> Oops: Exception in kernel mode, sig: 4
>
> Anybody have had the same problem ?
> Disabling DEBUG is fine, but I was really wondering why I was getting
> this.
>
> kernel is linux-2.4-devel BK tree in version 2.4.23-pre5
Hi Hubert !
Nice to see you using Linux again :)
What machine is this ?
The bug shows that the poison checker found that a freed block got
overriden. It didn't display more infos about the kind of pattern
it found and/or a backtrace ? That would be helpful.
I've been trying to track down such kind of memory corruption for
some time now, so if you have a good handle on it, I'm interested,
as I suspect something wrong is going on in recent 2.4s
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-09-25 13:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-25 12:31 kernel panic in slab.c Hubert Figuiere
2003-09-25 13:44 ` Benjamin Herrenschmidt [this message]
2003-09-25 14:14 ` Hubert Figuiere
2003-09-25 14:30 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2005-05-23 21:33 Bill Rogers
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=1064497450.702.12.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=hub-linux-ppc@trantor.staff.proxad.net \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).