From: Roland Dreier <rdreier@cisco.com>
To: Andre Draszik <kernel@andred.net>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Slab errors on 4xx (STB04)
Date: Sun, 09 Apr 2006 18:42:17 -0700 [thread overview]
Message-ID: <adairpi5hqe.fsf@cisco.com> (raw)
In-Reply-To: <44398BD4.60904@andred.net> (Andre Draszik's message of "Mon, 10 Apr 2006 00:33:56 +0200")
Andre> Since it _seems_ to work nevertheless - is
Andre> CONFIG_DEBUG_SLAB known to be broken on this platform?
Andre> (Although such stack traces are only printed when doing sth
Andre> with the USB). Or is this caused by some other (memory
Andre> initialization?) error?
Last time I looked, I think CONFIG_DEBUG_SLAB was broken on
non-cache-coherent architectures (such as PPC 4xx). The reason is
that the slab poisoning breaks the cacheline alignment of slabs, and
then invalidating the cache can trash stuff that slab debugging ends
up thinking is overwritten.
- R.
next prev parent reply other threads:[~2006-04-10 1:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-09 22:33 Slab errors on 4xx (STB04) Andre Draszik
2006-04-10 1:42 ` Roland Dreier [this message]
2006-04-10 7:14 ` Eugene Surovegin
2006-04-10 19:48 ` Andre Draszik
2006-04-16 1:32 ` Andre Draszik
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=adairpi5hqe.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=kernel@andred.net \
--cc=linuxppc-embedded@ozlabs.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).