From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from test-iport-3.cisco.com (test-iport-3.cisco.com [171.71.176.78]) by ozlabs.org (Postfix) with ESMTP id 25BB167A6F for ; Mon, 10 Apr 2006 11:52:18 +1000 (EST) To: Andre Draszik Subject: Re: Slab errors on 4xx (STB04) References: <44398BD4.60904@andred.net> From: Roland Dreier Date: Sun, 09 Apr 2006 18:42:17 -0700 In-Reply-To: <44398BD4.60904@andred.net> (Andre Draszik's message of "Mon, 10 Apr 2006 00:33:56 +0200") Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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.