From: Eugene Surovegin <ebs@ebshome.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: bart.vanassche@gmail.com, netdev@vger.kernel.org,
"bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>,
linuxppc-embedded@ozlabs.org
Subject: Re: [Bugme-new] [Bug 8778] New: Ocotea board: kernel reports access of bad area during boot with DEBUG_SLAB=y
Date: Wed, 18 Jul 2007 01:34:25 -0700 [thread overview]
Message-ID: <20070718083425.GA29722@gate.ebshome.net> (raw)
In-Reply-To: <20070718005253.942f0464.akpm@linux-foundation.org>
On Wed, Jul 18, 2007 at 12:52:53AM -0700, Andrew Morton wrote:
> On Wed, 18 Jul 2007 00:07:50 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:
>
> > http://bugzilla.kernel.org/show_bug.cgi?id=8778
> >
> > Summary: Ocotea board: kernel reports access of bad area during
> > boot with DEBUG_SLAB=y
Slab debugging is probably the culprit here. I had similar problem
couple of years ago, not sure something has changed since then,
haven't checked.
When slab debugging was enabled it made memory allocations non L1
cache line aligned. This is very bad for DMA on non-coherent cache
arches (PPC440 is one of those archs).
I have a hack for EMAC which tries to "workaround" this problem:
http://kernel.ebshome.net/emac_slab_debug.diff
which might help.
--
Eugene
next prev parent reply other threads:[~2007-07-18 8:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-8778-10286@http.bugzilla.kernel.org/>
2007-07-18 7:52 ` [Bugme-new] [Bug 8778] New: Ocotea board: kernel reports access of bad area during boot with DEBUG_SLAB=y Andrew Morton
2007-07-18 8:34 ` Eugene Surovegin [this message]
2007-07-18 13:41 ` Josh Boyer
2007-07-18 15:59 ` Eugene Surovegin
2007-07-18 16:28 ` Josh Boyer
2007-07-18 16:55 ` Andrew Morton
2007-07-18 17:04 ` Eugene Surovegin
2007-07-18 18:43 ` Bart Van Assche
2007-07-23 20:34 ` Christoph Lameter
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=20070718083425.GA29722@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=akpm@linux-foundation.org \
--cc=bart.vanassche@gmail.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=netdev@vger.kernel.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).